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.
This request is to ask that the development team review the code inside the Documents for refactoring to see if certain things can be reduced (like Generics).
When using the Telerik UI for Xamarin and referencing the UI.for.Xamarin NuGet package, the assembly reference for the Telerik.Documents.Fixed.dll is added to the project. This increases the amount of code that is compiled when the Linker is only set to SDK only, thus breaking AOT compilation with LLVM enabled.
A few addition insights:
- When the project cannot set the Linker to SDK and User Assemblies
- When individually referencing DLLs for only what the project uses is an insufficient solution
- When installing sub-packages like Telerik.UI.for.Xamarin.DataGrid is an insufficient solution.
These file formats are very similar to DOCX, and can be easily imported with loss of some information (e.g. macros).
When this type of section break is used, the next section should start on the same page instead on the next one.
Implement functionality allowing to specify that when a table is split on multiple pages, a specific row should be shown on each page. Workaround: in the attached demo projects.
Currently, similar scenario may be achieved by converting Tiff images to BitmapSource and inserting them to RadFixedPage as images by using FixedContentEditor.
Add support for INCLUDEPICTURE fields. Such fields should work with nested MERGEFIELD, as this is common scenario. Workaround: Manually insert images over specific placeholder
Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document: - Rich Text - Plain Text - Check Box - Combo Box - Drop-down list - Date picker Do not confuse this feature with form fields support (see https://feedback.telerik.com/Project/184/Feedback/Details/219850 ).