Improved Rendering of Visio Drawings to PDF using Aspose.Diagram for Java 2.2.0

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose.Diagram for Java logoToday, we’re pleased to announce the release of Aspose.Diagram for Java 2.2.0 as well as the goal of increasing consistency and simplicity for developers. The Aspose.Diagram API has improved export of Visio drawings to PDF format so that it exports just like Microsoft Visio does. Our development team has also worked to port the latest features from Aspose.Diagram .NET to Java and is pleased to make them available in the public API.

Rendering Improvements

We have provided improved rendering support in this latest release. Normally, Microsoft Visio users prepare complex drawings in a beautiful layout. Chances are they’d like to maintain its appearance when exporting to PDF or any other supported formats. We have improved the API in this area. It’s all based on the customer Visio drawing samples. This release includes a number of key fixes that help us improve Visio to PDF rendering:

  • The spaces between the text lines were messed up.
  • The computer symbol shape disappeared.
  • The text and image items were jumbled up.
  • Dotted lines were replaced with solid lines.
  • The page number sequence was incorrect.
  • The arrow thickness is preserved in the output PDF format. Previously, it was ignored.
  • Numbered items from the shape’s text were missing.
  • A portion of the source PDF file was cut off.
  • The date was missing from the label shape.
  • The Microsoft Outlook icon was replaced by a Microsoft Word icon.
  • All the smiley faces were changed.
  • Hyperlinks were not preserved properly in the output PDF.
  • Some map shapes were missing.

Error Message Fixes

This version brings fixes to reported error messages and include various other enhancements.

  • Fixed: the array index out of bound error message occurred while saving VSD to the PDF Format by calling the Diagram.Save method.
  • Fixed: the unknown source message occurred while converting VSD to PDF format.

Auto-Ported Features from the .NET Version

Aspose.Diagram for Java is fully ported from the Aspose.Diagram for .NET API. The porting process has added a few more features that are already available in the latest version of Aspose.Diagram for .NET. Below is a of new features.

  • Glue Shapes in Container using Connection Names – There are many ways to glue shapes in the container, we’ve covered the basics of handling glue. Developers can now glue shapes in the container by passing connection name parameters. Previously, it was only possible by connection IDs. The new release of the Aspose.Diagram API has now made it very easy: just pass the exact connection name.  Developers can use either the connection IDs or name by using either the Page.glueShapesInContainer or Page.glueShapesInContainerByID methods. You can find the details of this feature in the following help topic: Glue Shapes Inside the Container
  • Add Master to Diagram from Source Diagram – This feature is useful primarily if we have added the new shapes and saved them to a source Microsoft Visio diagram. It helps developers to add a master to diagram from source diagram.  We have added a new overloaded Diagram.AddShape method. It takes a master name and a Diagram class object (the object that represents a Visio drawing). Please find details of this feature in the following help topic: Add Master from the Stencil of Shapes

Public API Changes

The following API changes in the new version are also worth noting:

  • The Page.glueShapesInContainer and Page.glueShapesInContainerByID methods have been added. These methods take connection IDs or Name/NameU as parameters to glue shapes in the container.
  • The overloaded Diagram.addMaster method has been added. It takes a master name and the source diagram object as parameters.
  • The Page.addShape method has been added. It’s used to import a bitmap image as a Visio shape.

Aspose.Diagram for Java Resources

The following resources will help you work with Aspose.Diagram for Java:

We hope you’ll enjoy this new release that save time and efforts. The API is quite simple and developers can use it in application easily.