GroupDocs.Viewer 2.0 – New Features & Improvements to the Java Version of the Document Viewer

GroupDocs.Viewer for Java library

Last week, we released an update to the GroupDocs.Viewer library for the .NET platform. Now it is time to share what version 2.0 of GroupDocs.Viewer has to offer to the Java world. You can find a full list of new features, improvements and fixes on the GroupDocs.Viewer download page. The most notable improvements, I’m going to discover in this article.

Native HTML5-Based Document Rendering

The brightest gem presented in this version is the HTML-based rendering mode – an addition to the image-based one that was the only choice in previous versions of the document viewer. Under the new mode, all text is placed on the page using pure HTML and CSS, while graphics are drawn using SVG format. This feature makes pages more “lightweight” and allows end-users to search for text within the document using the native browser search functionality.

Please note: by default, the rendering mode is image-based, so you have to switch it explicitly. This can be done via the useHtmlBasedEngine parameter in the JavaScript plugin – just specify true to enable HTML mode. Also, when you turn on the HTML-based mode, make sure to set the com.groupdocs.viewer.config.ServiceConfiguration constructor’s useCache argument to true.

Enhanced Thumbnails Panel Usability

GroupDocs.Viewer for Java 2.0 has a new layout option for the thumbnails panel. The panel can now either slide over the document pages, or you can place it on the same level as the pages, so that it doesn’t overlap the document’s content. The layout options can be switched with the useInnerThumbnails Boolean parameter, where the true value places thumbnails to the left side of the viewport.

Improved Text Search Engine

Previous versions of the viewer could only search on exact phrases. That is also the default in the new version. A newly added option allows users to search for every separate word entered to the search form. To activate this, just specify true for the searchForSeparateWords parameter.

Enhancements for the Upload API

Token ID – a New Unique and Secure File Identifier

This is a Java-specific feature of the new version of the document viewer. Before this update, the upload API was quite primitive – it only provided an ID of the uploaded file on the output side. The identification functionality was encapsulated into the TokenId class. Now, the ViewerHandler method:

public Object uploadFile(InputStream inputStream, String fileName, Integer timeToLive)

returns the file token ID, which, as before, can be used to view the uploaded file. But with its new ID, the viewing process got few important improvements:

Uploaded File Time Usage Restriction

The first improvement is the ability to restrict access to uploaded files using the TokenId time limit. Each uploaded file’s ID now has the timeToLive parameter, which can be checked with the

public boolean isExpired()

method of the TokenId class. For example, before displaying a document, you can check:

TokenId tki = new TokenId(tokenId);
if(tki.isExpired()) {
    // access denied
}

Token ID Renewal API

The redundancy of file upload and space usage issue was resolved with the token ID renewal API. Now, the old token can be refreshed using the

public Object renewTokenId(String tokenId)

method of the ViewerHandler class.

Other Improvements

In addition to the above, the new version of the Java document viewer library features the following:

  • Faster page rendering on first load – due to additional cache.
  • Lower memory usage – due to tuned-up algorithms.
  • Improved integration – the API is now better structured.

For a complete list of new features, improvements and bug fixes, as well as to download the new version of the GroupDocs.Viewer for Java library, please visit this page. Also, here are a couple of samples that might help you discover all the new features faster:

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

To keep up with our news, you can follow us on Twitter or follow our Facebook page.

Leave a Reply