UNG Docs

UNG Docs is an extensible component framework for user interfaces based on:

  • pure javascript
  • document orientation
  • serverless interaction
  • data access abstraction
  • content collaboration

Quick Links

Why UNG Docs?

Most enterprise Javascript applications do the same thing: create documents, search documents, list documents, view documents, edit documents and save documents. The logic to edit document content is often mixed with the logic to access document data. Since there is no Web standard to search documents stored in different enterprise applications, most Javascript components are thus not interoperable with different enterprise applications.

What is UNG Docs?

UNG Docs provides a set of standards to facilitate reuse and interoperability of Javascript user interface components used in enterprise applications. UNG Docs wraps existing Javascript user interface components created by communities so that they share a common API and can be used in combination with different enterprise applications.

How does UNG Docs look like?

The default configuration of UNG Docs is a Web Office suite which can be used to create and modify text, spreadsheets and illustrations.

UNG Docs can be configured with different user interface. It can then look like an accounting software or a content management backend.

What is UNG Docs 1.0, 2.0, 3.0?

UNG Docs is still an ongoing effort. The long term goal of UNG Docs will be achieved step by step by 2013.

UNG Docs 1.0 (2010) is the current stable version of UNG Docs. It uses a server based architecture based on ERP5 document management module. It provides: text, spreadsheet, illustration, email and calendar. It can be extended using ERP5 business templates. It supports office document formats such as ODF and MS Office.

UNG Docs 2.0 (2011) is a proof of concept and testbed. It uses a serverless architecture, provides an early implementation of JIO data access abstraction standard, offline mode and supports Unhosted.org protocol for user registration and preference management. UNG Docs 2.1 will include support for extensible gadgets and component registry based on the OpenAjax Alliance standards. UNG Docs 2.2 (2012) will include a form engine component capable of accessing and modifying ERP5 structured data. UNG Docs 2.3 will include support for content collaboration.

UNG Docs 3.0 (2013) will be a clean rewrite of UNG Docs. Subsequent UNG Docs 3.x will include support for more storage backends and enterprise applications.

UNG Docs Components

UNG Docs software components consist of: JIO data abstraction layer, cloudooo conversion server and UNG Shell.

JIO is a javascript library which provides a unified API to create, search, load and save documents. Thanks to JIO, accessing documents in local storage, in a remote CMS or on an S3 key-value store uses the same method calls. In addition to abstraction data access, JIO is capable of splitting data or encrypting transparently. JIO was first implemented as part of UNG 2.0. JIO can be used standalone or with other UNG Docs components.

Cloudooo conversion server provides a unified API to convert any document in more than 200 file formats. It supports office documents (ODF, MS Office, PDF, HTML, etc.), images (PNG, JPEG, TIFF, etc.) and videos (MPEG, ASF, etc). Cloudooo was first implemented as part of UNG 1.0. Cloudooo can be used standalone or with other UNG Docs components.

UNG Shell is the root application container of an UNG Docs application. It provides persistent for the arrangement of gadgets which define an UNG Docs configuration. UNG Shell will be implemented first in UNG 2.1. UNG Shell requires JIO.

UNG Docs Standards

UNG Docs is based on widely adopted or very promising standards:

  • HTML5
  • JQuery
  • OpenAjax Alliance (Metadata Specification, Hub and Registry)
  • Unhosted.org

Bottom Gadget
Right Gadget