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.
When creating a GradientStop, an alpha channel of the color could be applied. However, this setting is not respected it the result document and the gradient is with full opacity. Steps to reproduce: 1. Create a gradient with an alpha channel: RadFixedDocument document = new RadFixedDocument(); RadFixedPage page = document.Pages.AddPage(); FixedContentEditor containerEditor = new FixedContentEditor(page); LinearGradient linearGradient = new LinearGradient(new Point(0, 0), new Point(30, 30)); linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 207, 0), 0)); linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 102, 204), 1)); containerEditor.GraphicProperties.FillColor = linearGradient; containerEditor.DrawRectangle(new Rect(10, 10, 48, 29)); 2. Export the document to PDF Observed: The alpha channel is not respected and the gradient is with full opacity
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.
When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts.
The CropBox is currently not supported by RadFixedPage class and is not preserved on an Import-Export scenario with PdfFormatProvider. CropBox is also not supported by PdfPageSource class and it is not preserved by using PdfStreamWriter as well. This property should be implemented in both scenarios.
When merging, only the widgets are copied but not their fields. This can lead to ArgumentNullException when exporting the document. Implement copying the fields and consider cases which include collision of names of the fields. Workaround: Repair the generated document using the following code: Provide a way to rename FormFields.In case of Name collision, you can use the attached project or the attached project to the following feedback item to rename the duplicate fields:
To bring RadPDFProcessing to the next level you should support XMP metadata. This would extremely help to use pdf files from RadPDFProcessing in digital workflows. Reference: http://www.adobe.com/devnet/xmp.html