Major JPedal Java PDF Library SDK update in April

The April release (29th of April) of JPedal will be a little bit special, so we would like to give you a sneak preview…

Over the last few months, we have been planning how we continue to develop our products and what improvements we would like to see. We can now reveal our plans for the next 12 months (well some of them). Some of these changes will be immediate, some will be phased in and some we are announcing now so that you know what we are doing.

From April, we will move to JPedal release 7 (which is our way of signaling big changes).

1

Changes

In the April 2016 Release….

1. XFA support as standard in a single JPedal release

The XFA and non-XFA releases will combine together. This allows us to better support more types of PDF files with just a single jar. Many customers do not even know if they are working with XFA files or not, so this will make life much simpler.

Existing customers will be grandfathered into the new version. This will also mean that the price of JPedal will rise slightly – the first price increase since 2004 (any existing quotes will be honoured at the old price).

2. API tidy up

We started the code base in 1999 and it is time for some old stuff to go. Under the hood, we have been working on a big code tidy with long deprecated methods now removed and a clean-up to remove old, unused methods and to tidy up meaning that JPedal is easier to work on, more efficient and is a better code base for you to use.

3. Improved appearance for the Java Viewer

The JPedal Java PDF Viewer as been around a long time and we felt it was due for a reskin of the GUI. In later releases, we will also be giving you some new features…

4. Goodbye AppletViewer.

Applets are dead and buried!

…and in the next few releases

1. Forms saving

Until now, JPedal has been unable to edit files. This will be changing with JPedal 7 so that we can write back forms data into PDF files. We will add additional features and enhancements to this over the year. This will allow us to provide a single, complete solution for our clients with Forms.

2. Support for new image formats and better image support in Viewer

For JPedal and the Viewer. We will continue to add additional image features and also improve the Viewer as a Java image viewing solution.

3. Java8 will be required from April 2017

We want to move to Java 8 eventually as the other versions of Java are already EOL (End of Life) and Java 8 will be approaching EOL in 2017. At the moment, we support Java6 level and moving to Java8 will allow us to make JPedal better by using streams, lambda and more to improve performance. Our aim is to have a modern, actively developed product for our customers, and we feel 2017 is the time to move onto Java8.

So we are giving 12 months notice of the change…

4. More editing features.

You will have to wait and see…

We hope that you like the changes and look forward to your feedback now or over the next 12 months. Let us know what you think, or what you would like to see…

If you’re a first-time reader, or simply want to be notified when we post new articles and updates, you can keep up to date by social media (TwitterFacebook and Google+) or the  Blog RSS.

Related Posts:

The following two tabs change content below.

Mark Stephens

System Architect and Lead Developer at IDRSolutions
Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX. He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.
Markee174

About Mark Stephens

Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX. He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>