We would like to greatly simplify the JPDF2HTML5 converter by changing the way that our view modes and navigation modes work. The plan is to provide two simple options:
Option 1: Content Mode
Option 2: IDRViewer
This mode is designed for users who wish to use our converted content inside their own content management system or to wrap the converted content in their own viewer.
What it gives you is each PDF file converted into one HTML file per page. Additionally, we would like to provide a properties.json file which provides information about the document that can be used to build your own viewer. In the April release, we have added a system property experimentalProperties=true that when set, will output a properties JSON file that contains the pagecount, the page bounds, as well as any bookmarks the PDF file contains.
This is the information that we currently use within our own IDRViewer. We do have some other ideas for what we can put in this file, but we would really love your feedback so that we know whether this is useful or not.
This mode is designed for users who want a more complete viewer solution and do not want to do lots of post processing to the converted content.
What it gives you is a viewer with several different display modes (MultiFile, SplitSpreads, SingleFile, Mobile Swipe Mode) with a small number of configuration options and the ability to make some minor changes such as to reskin the viewer and control which display modes are available. In the April release, we have added a system property experimentalViewer=true that when set, will output our current progress of the new version of the IDRViewer for you to test.
Additionally, we have also added support for pure SVG content in the experimental IDRViewer, as the plan is for this change to affect both the HTML and the SVG conversion.
What else will be removed/changed?
When this change goes live, our plan is to remove the current navigation mode options. For example, no longer will it be possible to output the current version of the singlefile mode that does not use the IDRViewer. Instead, if you need that, we recommend that you programmatically use the properties JSON file, and to post-process the content produced by our content mode to use the converter in the way that you need.
Why do we want to make this change?
We feel that this change has many positives and very few negatives (except for potentially the need for some customers to update their post-processing to reflect these changes when they update to the new version).
– Isolate viewer from content
– Simplified usage model
– Improved viewer, better mobile support
– Higher chance future updates will not affect customer post-processing
– Easier to build a custom viewer around converted content with the new properties JSON file
What do the changes look like?
If you would like an easy way to see how these changes look, we highly recommend that you watch the April release update video as we provide additional information and show what these changes entail.
Your feedback is important to us. Think this is a brilliant/terrible idea or want to discuss these changes with us further? Let us know! We would love to get your feedback so that we can make sure that these changes are the best for everyone.
Latest posts by Leon Atherton (see all)
- Making a Simple Basecamp Chatbot with NodeJS - November 29, 2017
- My Business of Software Conference Experience – BoS Europe 2017 - June 7, 2017
- Do you still need IE8 support in JPDF2HTML5? - February 8, 2017
- JPDF2HTML5 2016 Roundup and looking ahead to 2017 - December 20, 2016
- What Chrome 45 dropping NPAPI Plug-in support means - September 10, 2015