Implement support for pictures with references represented with the r:link attribute in the schema.
Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields. Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.
The non-breaking hyphen element is currently not supported in the model and is stripped when importing the document.
I'm working on a project that has a service component that will be generating Excel xlsx documents for distribution. While there is a UI for administrative tasks, the service itself will run without an interface. I'm using the Documents.Core, and several other associated libraries to accomplish this. Two issues I've encountered, one is setting up the project with the appropriate libraries and keeping the version in sync with the Admin application, second is protecting those libraries once they are packaged for release. I had a support ticket open to determine how to accomplish the latter, but the first is still a manual issue.
So the feature request is to include the ability in the project templates and/or Convert to Telerik WPF Application to support a headless document solution. It would ideally include (only) the required libraries and maintain their linkage to the appropriate library version with the rest of the solution which occurs with a full Telerik WPF UI app. It would also include the necessary boilerplate code and references to properly protect the libraries. I was referred to another feedback request on improving the overall library protection build process, but while related, what I'm asking for here is not exactly the same.
When exporting, an option of how to create the PDF bookmarks should be provided:
- Using the RadFlowDocument bookmarks
- Using document Headings
Add support for preserving and exporting the macros in a macro-enabled workbook. Macros are pieces of code written in Visual Basic for Applications (VBA) which are used to automate repetitive tasks in excel. The macros are part of the excel file. When a file contains a macro its extension becomes xlsm. SpreadProcessing should be able to import and export xlsm files and edit the macros in them.
Add support for setting and exporting document metadata, like Title, Author and similar.