We are thinking about the possibility of implementing a view on top of the iink view where the user could perform operations that are not available with the SDK. If the data from our view could not be imported into iink, we would like to be able to merge ourselves both sets of data to save as a single document (for example a PDF file). I think we could retrieve the data from iink using its export functionality, but would we also be able to retrieve formatting and layout data? For example, the positions of various text elements, the font, color, etc.
If metadata doesn't answer your use-case, the more complete information you can have is exporting as JIIX, as the latter contains Shapes information, position and content of text blocks...
If metadata doesn't answer your use-case, the more complete information you can have is exporting as JIIX, as the latter contains Shapes information, position and content of text blocks...
Nicolas Morin
We are thinking about the possibility of implementing a view on top of the iink view where the user could perform operations that are not available with the SDK. If the data from our view could not be imported into iink, we would like to be able to merge ourselves both sets of data to save as a single document (for example a PDF file). I think we could retrieve the data from iink using its export functionality, but would we also be able to retrieve formatting and layout data? For example, the positions of various text elements, the font, color, etc.
Thanks!
Dear Nicolas,
without knowing your exact use-case, it is difficult to provide with an accurate answer, but I want to point out that you can add metadata to your contentParts and contentPackages to add custom data: https://developer.myscript.com/docs/interactive-ink/1.4/android/fundamentals/storage/#metadata
An explanation about using metadata is given in the following post: https://developer-support.myscript.com/support/discussions/topics/16000027762
If metadata doesn't answer your use-case, the more complete information you can have is exporting as JIIX, as the latter contains Shapes information, position and content of text blocks...
Best regards,
Olivier
Olivier @MyScript
Dear Nicolas,
without knowing your exact use-case, it is difficult to provide with an accurate answer, but I want to point out that you can add metadata to your contentParts and contentPackages to add custom data: https://developer.myscript.com/docs/interactive-ink/1.4/android/fundamentals/storage/#metadata
An explanation about using metadata is given in the following post: https://developer-support.myscript.com/support/discussions/topics/16000027762
If metadata doesn't answer your use-case, the more complete information you can have is exporting as JIIX, as the latter contains Shapes information, position and content of text blocks...
Best regards,
Olivier