-
Notifications
You must be signed in to change notification settings - Fork 79
PDFViewer Annotations Documentation #2429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
a57edc2
1ab1c24
4d18f5f
6f854ed
d2fbe94
cbdd9c5
1ecb19d
9e839b4
07e16e6
bcb7fff
0141549
13df49c
1cb1ec0
b7bfc5b
e48317c
0fff161
aab8a63
93c3948
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| --- | ||
| title: Annotations | ||
| page_title: PdfViewer - Annotations | ||
| description: Annotations in the PdfViewer for Blazor. How to add and configure annotations in the PdfViewer for Blazor | ||
| slug: pdfviewer-annotations | ||
| tags: telerik,blazor,pdf,pdfviewer,annotations | ||
| published: True | ||
| position: 15 | ||
| --- | ||
|
|
||
| # PdfViewer Annotations | ||
|
|
||
| The PdfViewer supports a set of annotation types to enhance PDF documents. For example, users can highlight important text areas or add notes as free text. | ||
|
|
||
| The PdfViewer creates a dedicated layer for the annotations and includes them when downloading or printing the file. If the user opens a file with annotations, they can edit only the annotations that were added using the PdfViewer `Annotations` tool. The PdfViewer does not support editing annotations added in a different PDF editor. | ||
|
|
||
| To add and manage the annotations, the user can click on the dedicated button in the [PdfViewer Toolbar]({%slug pdfviewer-toolbar%}). It opens an annotations bar with the available annotation types. | ||
|
|
||
| ## Supported Annotations | ||
|
|
||
| The PdfViewer provides the following annotation types: | ||
|
|
||
| @[template](/_contentTemplates/common/parameters-table-styles.md#table-layout) | ||
|
|
||
| | Annotation Type | Description | | ||
| | --- | --- | | ||
| | **Text Highlight** | Allows highlighting the selected text in the document. Users can choose the desired highlight color. | | ||
| | **Free Text** | Allows creating an element with free text anywhere in the document. Provides option to select the desired text color and font size. | | ||
ntacheva marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ## Working with Annotations | ||
|
|
||
| **To manage the annotations the user should:** | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not entirely opposed to the bold formatting here, but do we need it?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I want to visually distinguish these parts but we've agreed not to use cations for that purpose. |
||
|
|
||
| 1. Click on the `Annotations` tool in the [Toolbar]({%slug pdfviewer-toolbar%}) to open the Annotations bar with the available annotation types. | ||
| 1. Click the desired annotation type to toggle it. You need to first "turn on" the annotation tool to add or edit annotations of the corresponding type. If none of the annotation tools are enabled, the PdfViewer will not allow interacting with the document to create or edit annotations. | ||
|
|
||
| **From this point the user can:** | ||
|
|
||
| 1. **Create an annotation**—The user can select a non-annotated text to highlight it or they can click an area that does not have free text element to create an annotation. Once they create the annotation, a popup with the available customization options will appear. | ||
| 1. **Edit an existing annotation**—The user can edit one or multiple annotations at a time but they all must be of the same type. To select multiple annotations, the user can hold `Ctrl` and click on all annotations they want to edit. | ||
| * To edit color and font size the user can click the annotation they want to edit to open the customization popup. | ||
| * To edit the text in the `Free Text` annotation element, the user can double-click the element to open the textbox for editing. | ||
| * To move the `Free Text` annotation element the user can click it to enable the drag tool and start dragging. | ||
| 1. **Delete an existing annotation**—The user can click the annotation they want to delete to open the customization popup. Pressing the delete button in the customization popup will open a delete confirmation dialog where the user can confirm or cancel the annotation deletion. | ||
|
|
||
| ## Disabling Annotations | ||
|
|
||
| The Annotations tool is included in the [Toolbar]({%slug pdfviewer-toolbar%}) by default. To prevent users from creating annotations, you can [configure the Toolbar and not include the `PdfViewerToolBarAnnotationsTool`]({%slug pdfviewer-toolbar%}#toolbar-configuration). | ||
|
|
||
| ## See Also | ||
|
|
||
| * [PdfViewer Live Demo](https://demos.telerik.com/blazor-ui/pdfviewer/overview) | ||
| * [PdfViewer Toolbar]({%slug pdfviewer-toolbar%}) | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,64 @@ | ||
| --- | ||
| title: 6.3.0 | ||
ntacheva marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| description: Handle the rendering changes in the 6.3.0 release of the Telerik UI for Blazor components. | ||
| page_title: Rendering Changes in the 6.3.0 Release | ||
| slug: changes-in-6-3-0 | ||
| position: 970 | ||
| --- | ||
|
|
||
| # Rendering Changes in 6.3.0 | ||
ntacheva marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| * [AIPrompt](#aiprompt) | ||
| * [Gantt](#gantt) | ||
| * [Menu](#menu) | ||
| * [PDFViewer](#pdfviewer) | ||
| * [Signature](#signature) | ||
| * [TabStrip](#tabstrip) | ||
| * [TreeList](#treelist) | ||
|
|
||
| ## AIPrompt | ||
|
|
||
| 1. The view buttons in the toolbar are now fully rounded (`k-rounded-md` class is replaced with `k-rounded-full`). The same applies to the `Generate` button. | ||
| 2. The output view, which contains the `<div class="k-card-list">` element, is now wrapped in a `<div>` element with class `k-prompt-view`. | ||
| 3. The copy button in the output view is now styled as primary. | ||
|
|
||
| ## Gantt | ||
|
|
||
| 1. The `k-gantt-content` class is now applied to a `<div>` wrapper element that encloses the Gantt Splitter. | ||
| 2. The Splitter component class (`k-splitter` element) is now changed from `k-grid-content` to `k-grid-splitter`. | ||
| 3. The `<div class="k-gantt-tables">` element no longer includes the `k-user-select-none` class. | ||
| 4. The `<table class="k-gantt-rows">` element now also has a `k-grid-table` class. | ||
| 5. The `<span class="k-spacer">` element in the toolbar no longer has the `k-toolbar-spacer` class. | ||
| 6. The `<div class="k-gantt-views">` button group / select element is now wrapped in a `<div>` with class `k-gantt-views-wrapper`. | ||
|
|
||
| ## Menu | ||
|
|
||
| 1. The menu item elements (`<span class="k-link">`) no longer include the `k-in` class. | ||
| 2. The `<ul class="k-menu-group">` element no longer includes the `k-reset` and `k-group` classes. | ||
|
|
||
| ## PDFViewer | ||
|
|
||
| The `Open`, `Download` and `Print` tools have been moved to a submenu toggled on click of a hamburger menu on the leftmost side of the Toolbar. | ||
|
|
||
| ## Signature | ||
|
|
||
| 1. When maximized, the Signature now renders a `k-signature-maximized` class. | ||
| 2. The fill mode class is now applied based on the `FillMode` parameter (appearance settings). | ||
|
|
||
| ## TabStrip | ||
|
|
||
| 1. The active (currently selected) tabs now render only the `k-active` class. The `k-tab-on-top` class is no longer applied. | ||
| 2. The inactive tabs no longer include the `k-state-default` class. | ||
| 3. The scroll buttons (prev & next) now render the `k-tabstrip-prev` and `k-tabstrip-next` classes, respectively. | ||
| 4. The `k-pos-relative` class is no longer applied to the `<div class="k-tabstrip">` element. The component now receives an inline `position: relative` style instead. | ||
|
|
||
| ## TreeList | ||
|
|
||
| 1. The `k-cursor-pointer` class is removed from the `<span class="k-treelist-toggle">` element (toggle row icon). | ||
| 2. The `<table class="k-table">` element rendered in the `<div class="k-grid-header-wrap">` element now also has the `k-grid-header-table` class. | ||
| 3. The `<table class="k-table">` element rendered in the `<div class="k-grid-content">` element now also includes a size class (appearance settings). | ||
| 4. The `k-filterable` class in the table header cells is now rendered only when the column is filterable and has either a filter menu or column menu. | ||
|
|
||
| ## See Also | ||
|
|
||
| * [Use best practices when overriding theme styles]({%slug themes-override%}#best-practices) | ||
Uh oh!
There was an error while loading. Please reload this page.