Free Support Forum - groupdocs.com

GroupDocs.Viewer - Looking for answers to these questions

This is for GroupDocs.Viewer.
  • Client-only document rendering (JS/HTML5) / Document rendering using backend server + Client viewer?
  • Is Backend Rest API available?
  • What is the Backend programming language (language in which the backend is developed)
  • Is Backend as library available (Can document viewer backend be integrated in our software as a library or does it need to be started as a separate service?)
  • Backend supported systems (Windows, Linux (which distributions))
  • Is the Viewer UI customizable?

  • Native rendering (using MS Office) available?

  • Underlying renderer (which renderer is used (Libreoffice, Microsoft Office, custom)?)

  • Integrations for AngularJS available?

  • Frontend (viewer) programming language (language in which the viewer is developed)

Answers to even a couple of questions will help. Thank you.

Hi there,

Thanks for taking interest in GroupDocs.Viewer.

Here are the answers of your questions.

Client-only document rendering (JS/HTML5) / Document rendering using backend server + Client viewer?

The API is available as GroupDocs.Viewer for .NET, GroupDocs.Viewer for Java and GroupDocs.Viewer for Cloud. GroupDocs.Viewer for .NET and GroupDocs.Viewer for Java are the standalone back-end APIs that provides the set of methods to render the source document into either HTML pages or images as per user’s choice. You will have to create your own front end UI to view/display these rendered HTML pages or images. Whereas, GroupDocs.Viewer for Cloud is a cross-platform compatible REST API and works for any desktop, web, mobile or tablet devices. For details, please visit this link.


Is Backend Rest API available?


GroupDocs.Viewer for Cloud is available as REST API for your apps & websites.


What is the Backend programming language (language in which the backend is developed)?

In case of back-end APIs, the programming languages are C#, VB.NET and Java.


Is Backend as library available (Can document viewer backend be
integrated in our software as a library or does it need to be started as
a separate service?)


Yes, GroupDocs.Viewer for .NET and GroupDocs.Viewer for Java are available as back-end APIs that can be integrated in your software/application.


Backend supported systems (Windows, Linux (which distributions))?

GroupDocs.Viewer for .NET supports MS Windows desktop and server operating systems, Windows Azure, and Linux (Ubuntu, OpenSUSE, CentOS and others). Whereas, GroupDocs.Viewer for Java supports MS Windows desktop and serves, Linux, and Mac OS.


Is the Viewer UI customizable?

GroupDocs.Viewer for .NET and Java are the back-end APIs and UI is not a part of these. However, we have created some open source document viewer application using these APIs. You can customize these applications according to your requirements. Please mentioned your suitable API so that we can guide you how to access and use these open source applications.


Native rendering (using MS Office) available?

Yes, native document rendering is supported by GroupDocs.Viewer API. In this case, stream returned by the API must be included/written in the header of HttpContext’s response. After the client app receives this response, it depends on the browser whether it supports to display that file format or not. In case, the browser does not support any MS Office format, the file will be downloaded automatically. For this, you will have to maintain your MSO Server.


Underlying renderer (which renderer is used (Libreoffice, Microsoft Office, custom)?)

The API uses its own methods to render the supported documents into HTML or image form without using any other rendered like MS Office or Libreoffice.


Integrations for AngularJS available?

As the APIs are independent of the front end frameworks therefore they can be integrated/used with AngularJS or any other front end framework.


Frontend (viewer) programming language (language in which the viewer is developed)?

You can use any of the front end programming languages as per your choice.


Please mention the API which is the most suitable in your scenario so that we can guide you for that particular case.

Warm Regards