Dear GroupDocs customers,
To ensure that our Cloud services continue to run smoothly, we are going to have some scheduled maintenance on Sunday, the 2nd of August, 2015. This maintenance is going to be held between 07:00am – 07:30am GMT.
Please note that the GroupDocs for Cloud API and GroupDocs for Cloud Apps services will be unavailable during this period. We are expecting that downtime will be no more than 30 minutes.
We tried to schedule the downtime during this period to minimize disruption to our customers as much as possible. We apologize for any inconvenience caused by the downtime.
The GroupDocs Team
Added support for new formats in GroupDocs.Conversion for Java library – PDF to HTML, Word to HTML and more
We’re pleased to announce the release of a new version of GroupDocs.Conversion for Java library – 1.2.0. In this release we’ve implemented three major updates. Probably the most interesting among them - is the ability to convert all supported file formats to HTML (including PDF to HTML, Microsoft Word to HTML and many more). We also added support for Microsoft Word bookmarks and the ability to convert and merge several documents into one PDF file.
Convert PDF and Microsoft Office Documents to HTML
With this feature, you can now convert files of any format supported by GroupDocs.Conversion for Java to HTML. To name just a few, the library allows you to convert:
- PDF to HTML
- Microsoft Word (DOC, DOCX) to HTML
- Microsoft Excel (XLS, XLSX) to HTML
- Microsoft PowerPoint (PPT, PPTX) to HTML
- Microsoft Outlook (MSG, EML) to HTML
- Microsoft Project (MPP, MPT) to HTML
- Microsoft Visio (VSD, VSDX) to HTML
- OpenDocument (ODT, ODS, OTT) to HTML
Source documents can be obtained either from files or from streams. And in the output you can also get either a complete web-page saved in a file (HTML + CSS + images) or send converted data (texts, images, fonts and other document elements) to streams.
Documents can be converted one-by-one on-demand or in batch. You can configure the library to convert one specific page within a document to HTML, all document pages to equivalent number of individual HTMLs (page-by-page), or all document pages to one single HTML file.
For more details on these and other GroupDocs.Conversion for Java features and supported file formats, please visit its homepage. If you have any question about the library, please see documentation, or make a request in our support forum.
GroupDocs.Viewer is a multi-format HTML5-based document viewer designed as a middleware to let developers on different platforms seamlessly integrate it into their own web-based applications, websites, or 3rd party services. GroupDocs.Viewer enables end users to view literally all common business document and image types using only a web-browser. To name just a few, supported file types include: PDF, Microsoft Word, Excel, PowerPoint, Outlook, Project, Visio, OpenDocument, Visio, CAD, multi-page TIFF and many more.
Thanks to add-ons developed by the GroupDocs Marketplace team, Concrete5 developers and website administrators can now seamlessly integrate GroupDocs.Viewer into their websites. Depending on your deployment preferences, you can choose between three different GroupDocs.Viewer versions: a downloadable .NET or Java library and a cloud-based REST API. The first two versions allow on-premises deployment, while the third one is an on-demand cloud service.
Regardless of the deployment option you choose, GroupDocs’ HTML5 document viewer provides you with the following benefits:
- Support for 50+ document and image types, including PDF and Microsoft Office.
- Cross-platform and cross-browser compatibility. End user can view documents from any web-enabled device using any HTML5-compliant web-browser.
- No need to install any software or web-browser plugins on end users’ machines.
- Convenient web-based UI that can be easily customized and embedded into any web-page as a document viewer widget. The UI allows end users to easily navigate large documents directly on your website.
- Ability to display documents in a read-only mode. GroupDocs.Viewer allows you to disable the print, download and text selection options to prevent users from unauthorized copying of your documents.
For more details on the add-ons and installation instructions, please refer to:
GroupDocs.Viewer for .NET version 2.13.0 – caching PDF copies of original documents & using multiple root storage paths
Last week we’ve announced a release of the GroupDocs.Viewer for .NET library version 2.13.0 and its two new features – an option for caching PDF copies of original files and the ability to use the viewer with an unlimited number of different independent root storage paths. Today we’d like to write about these features in more detail to help you quickly set up and get the most out of them.
Let’s start with the caching enhancement. As you may already know, GroupDocs .Viewer for .NET allows you to configure caching for displayed documents. When enabled, the viewer doesn’t have to convert original documents stored on the server to HTML-compatible content each time the documents are requested. Instead, documents are converted only during the first view request and then added to the cache. For all subsequent requests of the same documents, they are loaded from the cache, which significantly reduces load time.
This caching feature, however, was unavailable for PDF copies of original documents. So, when using features like .UsePdfPrinting(true) and .DownloadPdfFileIfPossible(true), the viewer had to convert original documents to the PDF format repeatedly for each new request. This was the case until the version 2.13.0. In the latest release of the GroupDocs.Viewer for .NET, you can now configure caching for PDF copies as well. What is important, the viewer is able to identify whether any changes to the displayed documents has been made (e.g. added watermarks, rotated or re-ordered pages, etc.) and if yes, refreshes the cache with the updated PDF copies, so that you can be sure that end users always get access only to the latest versions of the documents.
This new caching feature can also be used ahead-of-time. In other words, you can configure GroupDocs.Viewer to add PDF copies of original files to cache even before they were actually requested by end users. For doing so, just use a new method – GeneratePdfVersion – within the DocumentCache class.
The GeneratePdfVersion method obtains only one mandatory parameter – document’s name, then converts the document to the PDF format and saves it inside the cache folder. The method also has optional parameters which allow you to burn watermarks into PDF copies of original files. Please be cautious when configuring watermarks for different versions of a document. If you pre-generate a PDF copy of a document with watermarks and then specify the same document in the widget without the watermarks (or with some other watermarks), a discrepancy will occur, since watermarks specified for the "standard" document will vary from those specified for the PDF-version of the document.
Using Multiple Independent Root Storage Paths
Another remarkable improvement we’ve implemented in this version is the ability to use the viewer with an unlimited number of different independent root storage paths. Here is how this works. The default root storage path, which is configured via the Viewer.SetRootStoragePath method, remains obligatory. However, you can now set up additional paths using the InstanceID identifier. For example:
Groupdocs.Web.UI.Viewer.SetRootStoragePath(Server.MapPath("~/App_Data/"));- the default mandatory initialization.
Groupdocs.Web.UI.Viewer.SetRootStoragePath(Server.MapPath("~/OtherFiles/"), null, "myInstanceIdN1");- an additional root storage path (the OtherFiles folder), linked to the myInstanceIdN1 identifier.
Now, to load documents from the second root storage path (the OtherFiles folder), simply set the .ViewerInstanceId("myInstanceIdN1") method in the ClientHelper. This way you can configure as many independent root storage paths, as you need.
That’s it! If you have any questions about these or other GroupDocs.Viewer for .NET features, please feel free to ask for help on our Support Forum.
Get up and running quickly with GroupDocs.Total for Cloud API using the latest SDK version for your programming language
GroupDocs.Total for Cloud API is a suite of RESTful APIs that allows developers to seamlessly add powerful document collaboration functionality to their web-based and mobile applications, sites or 3rd party cloud services. The suite currently includes the following APIs:
GroupDocs.Viewer for Cloud API
GroupDocs.Viewer for Cloud is an online document viewer API that enables end users to view and securely share common document types on the web, without having to install any office software. Supported document formats include: PDF, Microsoft Word, Excel, PowerPoint, Outlook, Project, Visio, CAD, multi-page TIFF and many more. GroupDocs.Viewer for Cloud API comes with a web-based GUI that can be easily customized with your own CSS and embedded into your app or site as a document viewing widget. For more details on the document viewer API, please see this page.
GroupDocs.Annotation for Cloud API
GroupDocs.Viewer for Cloud is a document annotation API that allows end users to review and collaboratively annotate PDF, Microsoft Office and other common document types on the web. The API allows multiple users to annotate the same document simultaneously. Users can see each other’s annotations and comments and reply to them in real time. For more details on the document annotation API, please see this page.
GroupDocs.Assembly for Cloud API
GroupDocs.Assembly allows you to generate essential business documents on-the-fly by automatically merging your PDF or Microsoft Word templates with data obtained via online forms. GroupDocs.Assembly for Cloud provides API for designing and publishing online forms associated with your templates, collecting data via the forms and incorporating it into the templates. For more details on the document assembly API, please see this page.
GroupDocs.Signature for Cloud API
GroupDocs.Signature for Cloud is a secure electronic signature API that allows you to easily add e-signature functionality to your web-based application, site or business process. The API allows you to build custom electronic signature workflows of any complexity, or embed an out-of-the box GUI as is to let end users sign documents online without leaving your application or site. For more details on the electronic signature API, please see this page.
GroupDocs.Comparison for Cloud API
GroupDocs.Comparison for Cloud is a document comparison API that enables end users to compare two versions of PDF, Microsoft Word, Excel, PowerPoint, ODT, plain text or HTML documents online, without having to install the original software used to create the documents. This API comes with a web-based diff view GUI that displays differences found between compared documents and can be easily embedded to your web application or site. For more details on the document comparison API, please see this page.
GroupDocs.Conversion for Cloud API
GroupDocs.Conversion for Cloud is a universal document conversion API that allows you to convert back and forth between over 50 common document and image types. To name just a few, it allows you to convert DOC to PDF, DOCX to TIFF, PDF to DOC, PDF to HTML, XLS to CSV, RTF to DOC, HTML to JPEG, PDF to TIFF, PPT to JPEG, XLSX to HTML, MSG to PDF and many more. For more details on the document conversion API and supported file formats, please see this page.
GroupDocs Cloud SDK for Your Programming Language
Recently we’ve released an update to GroupDocs.Total for Cloud API with over 20 minor improvements and bug fixes. In particular, we’ve improved handling of Google Picker file uploads, added the ability of requesting user account removal from the profile page, improved handling of DOC to DOCX conversion operations, streamlined the process of integrating GroupDocs with the Box cloud storage provider, implemented a number of GUI style fixes, etc. In conjunction with updated APIs, we’ve also released new SDK versions with the updated UploadGoogle method (added parameters: url, description, accessToken; removed parameters: path, field), StorageInfoResult class (added a new property - used_documents) and a new method – SetCreditCard.
The latest versions of GroupDocs Cloud SDKs can be downloaded from:
- GroupDocs Cloud SDK for .NET – NuGet | GitHub
- GroupDocs Cloud SDK for Java – MVN | GitHub
- GroupDocs Cloud SDK for Python – PyPI | GitHub
- GroupDocs Cloud SDK for Ruby – Gems | GitHub
- GroupDocs Cloud SDK for PHP – Packagist | GitHub
For more details on GroupDocs.Total for Cloud API and to start a free trial, please go to:
Here at GroupDocs, we constantly develop new integrations that help developers on different platforms seamlessly add comprehensive document collaboration functionality to 3rd party applications, cloud services and content management systems. Today we have good news for ExpressionEngine developers and site owners. Recently we’ve released a new plugin that makes it easy to integrate GroupDocs.Annotation for Java into ExpressionEngine sites. The plugin has been approved by ExpressionEngine admins and is now available for download on the official ExpressionEngine marketplace.
When deployed, GroupDocs.Annotation for Java allows you to embed a convenient annotation widget on any page within your website. End users can then review and annotate essential business documents and image files online, directly on your website. Supported file formats include: PDF, Microsoft Word, Excel, PowerPoint, Outlook, Visio, OpenDocument, CAD, TIFF, PNG, JPEG and many more.
GroupDocs.Annotation for Java is platform and browser independent. It allows end users to annotate documents using any standard web-browser. There is no need to install any office suites or browser plugins. And thanks to the real-time annotation mode, several users located in different places can collaboratively annotate the same document simultaneously. During such multi-user annotation sessions, reviewers can place annotations, see each other’s comments and reply to them instantly. There is no more need of emailing back and forth documents between involved parties until they are finally approved. Getting documents reviewed has never been easier before!
This new Java plugin is the third in a series we’ve released for GroupDocs.Annotation. Earlier we’ve already published plugins that allow you to integrate GroupDocs.Annotation for .NET and GroupDocs.Annotation for Cloud. Now you have a choice to integrate any of the available GroupDocs.Annotation versions, depending on your deployment preferences. For more details on the plugins and installation instructions, please visit the ExpressionEngine marketplace at:
One of the most requested and hence actively developed features in GroupDocs.Viewer for .NET is watermarking. Watermarking allows you to protect documents that you display on the web from screen-grabbing. In GroupDocs.Viewer for .NET watermarks are implemented as customizable text that can be added over a displayed document, overlapping its content.
For the first time the ability to add watermarks was implemented in GroupDocs.Viewer for .NET version 2.0. In its first implementation, the feature had a number of restrictions. In particular, watermarks could be used only in the image-based rendering mode and the only customization option was the ability to specify a text color. Since that time, a lot of new parameters have been added and, importantly, the watermarking feature is now available in the HTML-based rendering mode too. In this article I’d like to discover all new parameters of the watermarking feature we’ve added since its first implementation.
But before we proceed with the parameters, I’d like to clarify several basic principles about how watermarks are rendered in GroupDocs.Viewer for .NET:
1. When adding watermarks, GroupDocs.Viewer doesn’t modify your original documents on the server. Instead, watermarks are rendered only on the client-side (over the document displayed in the GroupDocs.Viewer widget). So, be sure to disable the print and download options of your original files, or otherwise, end users will be able to get your documents without any watermarks. Alternatively, you can let users download and print PDF versions of the original files with watermarks burned in. More details about this option later in this article.
2. Watermarks are added to every page across the document. So far, you can’t add watermarks to specific pages only, or place different watermarks on different pages.
3. Watermarks, along with page rotation and reordering, are treated as one of the document modification features - they change representation of the document. But, unlike the page rotation and reordering options, watermark settings are not accessible from the client-side (GroupDocs.Viewer widget) and can’t be disabled or modified by viewers via the toolbar.
We’re now ready to explore all parameters of the watermarking feature available to date. Let’s start with the method signature:
public ClientHelper Watermark(
Color? watermarkColor = new Color?(),
WatermarkPosition watermarkPosition = 0,
float watermarkWidthInPercents = 0f,
bool printWithWatermark = false
As you can see, the only mandatory parameter is watermarkText (you can’t add a textual watermark without actually specifying a text to display). All other parameters are optional, have default values and can be omitted. Now, let’s take a closer look at them:
The watermarkColor parameter allows you to specify the color of the watermark text. The default color is red. You need to add a reference to the System.Drawing.dll assembly for your project in order to be able to use the System.Drawing.Color class.
The watermarkPosition parameter in an enumeration which specifies a start position of the watermark. It allows you to specify the following values: Diagonal, TopLeft, TopCenter, TopRight, BottomLeft, BottomCenter and BottomRight. The default value - Diagonal – places text across the page starting from the bottom left corner to the top right corner.
The watermarkWidthInPercents parameter requires a bit more clarification. By default, when this parameter is omitted, GroupDocs.Viewer tries to stretch the watermark text, making it as large as possible to match the page size. This default maximum size is treated as a 100% size. With this parameter you can decrease the watermark size, making the text smaller. The default value is "0" which equals 100%. A range from 1 to 99 (with support for fractional numbers) allows you to adjust the text size quite precisely.
The printWithWatermark is the most interesting in this series. As you may already know, GroupDocs.Viewer can generate a PDF-version of the original document when users try to print (.UsePdfPrinting(true)) or download (.DownloadPdfFileIfPossible(true)) the displayed document. With the printWithWatermark parameter set to true, watermarks will be burned into the PDF copies of the original documents that end users print or download. This allows you to share any document in the PDF format, protected with your custom watermarks.
That’s it. Hope the article answers all the questions you had about watermarking in GroupDocs.Viewer for .NET. If you still have any questions or experience issues when configuring watermarks, please feel free to ask for help on the GroupDocs Support Forum.
Back to top