Renaming Aspose.Cells for JavaScript via Java to Aspose.Cells for Node.js via Java

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose, a file formats API provider, has decided to rename Aspose.Cells for JavaScript via Java to Aspose.Cells for Node.js via Java. Aspose.Cells for Node.js via Java is a subset component that includes all the important and useful features present in its native Aspose.Cells for Java. Aspose.Cells for Node.js via Java presents all the useful features of Aspose.Cells for Java using Node.js. It is a class library that enables you to perform a great range of spreadsheet processing tasks. Aspose.Cells for JavaScript via Java is a scalable and feature rich API that offers spreadsheet format conversion, styling of worksheets at every level, chart management & rendering, and our reliable Formula Calculation Engine. Aspose.Cells for Node.js via Java supports XLS, XLSX, ODS, SpreadsheetML, CSV, Tab Delimited, HTML/MHTML, PDF, XPS and other formats. With Aspose.Cells for Node.js via Java you can generate, modify, convert and render Excel documents. You will have full programmatic access through a rich APIs set to all MS Excel document objects and formatting that allows to create, modify, extract, copy, merge, and replace spreadsheet content. With Aspose.Cells for Node.js via Java, developers can export data, format spreadsheets to the most granular level, create, manipulate and render charts, apply and calculate complex formulas efficiently and much more.

Important to Know

Please note, The APIs structure still remains the same, so it won’t disturb our existing clients who can still use the APIs without any changes in the code. We will soon revamp the Wiki Conf. Docs accordingly. We will also change Aspose.Cells for JavaScript via Java node to Aspose.Cells for Node.js via Java in Downloads section. Moreover, the Aspose.Cells for JavaScript via Java product pages will be soon updated. Similarly API Reference section for the product and other important areas will be accommodated accordingly.

The post Renaming Aspose.Cells for JavaScript via Java to Aspose.Cells for Node.js via Java appeared first on File Format APIs Blog – aspose.com.

Posted in Conholdate.Total Product Family, Aspose.Cells Product Family | Tagged | Leave a comment

Join Images using GroupDocs.Merger for Java

Share on FacebookTweet about this on TwitterShare on LinkedIn

With the new release of GroupDocs.Merger for Java 19.8 you can take your document joining experience to the next level.
What is special about this release?
We are pleased to announce that you can now do image joining. And following are the supported image formats:

  • BMP
  • PNG
  • TIFF

How easy is that?
Let’s understand this with a use-case. We’ll join a BMP and TIFF file.
https://gist.github.com/d03aba45762a74c410ee10e0e4fa1a05

New Format Support
API now fully supports HTML format.


We’d recommend you to download the latest release and integrate it in your application. In case you find any issue, feel free to post on forum.



The post Join Images using GroupDocs.Merger for Java appeared first on Document Manipulation APIs Blog – groupdocs.com.

Posted in Conholdate.Total Product Family, GroupDocs.Merger Product Family, GroupDocs.Merger for Java | Tagged , | Leave a comment

It’s Time to Upgrade to GroupDocs.Viewer for .NET 19.8

Share on FacebookTweet about this on TwitterShare on LinkedIn

GroupDocs.Viewer for .NET has been serving the developers in creating the document viewer applications for many years. With the efforts of our hard-working team and the support of our valuable customers, we are able to make the API stand among the top-ranked document viewer APIs. Since the Sky is the only limit, we always kept trying to enrich the API with more features, improve its performance, and make its usage easier for the developers. And today, I am excited to announce that we have introduced a new public API for GroupDocs.Viewer for .NET with major improvements.

In the latest version of the API (v19.8), we’ve improved the architecture of the API to simplify its usage and make it even easier to build applications. With the major product optimization, the API now consumes fewer resources as compared to the previous versions. Whereas, the document rendering speed has been improved significantly.

Let me give you a few reasons why you should switch to the v19.8 of GroupDocs.Viewer for .NET.

  • Memory usage – Significantly improved and optimized API’s memory usage (from 10% to 400% approx. depending on the document type ).
  • Improved rendering speed – The overall rendering speed has been improved remarkably. 
  • Code optimization – Optimized public API to make it even more intuitive and simple (with only a few lines of code you will be able to perform any action which required 20+ lines of code in the previous version).
  • Single entry point – A single class to manage the document rendering process for any supported file format.
  • Easy to use – API now gives more options to the developer in terms of usage and creativity.

With the major updates, the public API of GroupDocs.Viewer for .NET has undergone significant changes. As a result, the usage of the classes and their properties and functions has also been changed. Let’s now check the difference between the coding styles of the new and old version of the API.

This is how we used to get the HTML representation of the document with embedded resources using the old version:

Now, have a look at how we can perform the same operation using the new API.

Have you noticed that the code has been shrunk significantly to fewer lines of code in the coding style of the new API? Also, you don’t have to create separate handlers for HTML and image representation. Instead, just create a Viewer class and control its behavior using the classes that extend ViewOptions i.e. HtmlViewOptions, PngViewOptions and so on.

Now, as a developer, it is obvious that you would think about how would you deal with breaking changes in code after upgrading to the version which contains the major updates. So let me make it easier for you. In the latest version, the legacy API has been moved into the Legacy namespace. Therefore, after you upgrade to version 19.8, it is required to make project-wide replacement of namespaces only. This means that the namespaces will be changed from GroupDocs.Viewer.* to GroupDocs.Viewer.Legacy.* to resolve build issues. And that’s it!

Alright! So now, its time to switch to the latest version. I would recommend you to first explore the documentation of the new API with the help of the source code examples. Once you try it yourself, you will get a better idea of how useful it’ll be for you to switch to the latest version. You can also consult the release notes as well as the migration notes.

In case you would find the migration process difficult for you, feel free to post on our forum.

The post It’s Time to Upgrade to GroupDocs.Viewer for .NET 19.8 appeared first on Document Manipulation APIs Blog – groupdocs.com.

Posted in Conholdate.Total Product Family, .NET document rendering API, CAD viewer, Document viewer API, GroupDocs.Viewer Product Family, GroupDocs.Viewer for .NET Releases, Office Viewer, PDF viewer, document viewer, document viewer API for asp.net, online document viewer, render as PDF, word to pdf | Tagged , , , , , , , , , , , | Leave a comment

Manipulate XPS and EPS Documents using Aspose.Page

Share on FacebookTweet about this on TwitterShare on LinkedIn

The world admires Batman and Superman. They both have billions of fans together. They both have a different character, different powers, different qualities, and features. Even the fan base quarrel with each other about which superhero is better than the other one. One can always hear rants about Batman vs Superman. What if there was nothing like Batman vs Superman and they both worked together – serving humanity and saving the world? The world would definitely be a better place to live in!

Well, not for the whole world, but we can make life easier for .NET and Java developers working with XPS and EPS documents. We had Aspose.XPS and Aspose.EPS for manipulating XPS and EPS documents. Now, there is nothing like Aspose.XPS vs Aspose.EPS – They both are working together serving the developers – we call the new product Aspose.Page.

If you were a fan of Aspose.XPS or EPS there is nothing to worry. You can access all the features of both products with your existing license. Now combined together – we can have an even bigger fan base. Now let’s jump inside the code to get highlights of the product.

Convert XPS to PDF

Aspose.Page allows document conversion. For instance, you can convert XPS to PDF. Let’s try out the examples for conversion.

.NET

Java

This is the overview how the product words. The API offers other handful features for manipulate XPS and EPS documents. For more details, please feel free to visit documentation. To explore more examples you can access our open source examples and in case you would have any query, please feel to contact us using our forum.

The post Manipulate XPS and EPS Documents using Aspose.Page appeared first on File Format APIs Blog – aspose.com.

Posted in Conholdate.Total Product Family, Aspose.Page, Aspose.Page Product Family, EPS, XPS, conversion | Tagged , , , , | Leave a comment