Hitachi Vantara Pentaho Community Wiki
Skip to end of metadata
Go to start of metadata



As we continue to push thin-client interfaces and capabilites, the amount of Javascript we're writing and maintaining has increased substantially. Unfortunately, for most of this expansion we have lacked clear guidelines for Javascript development. This has in part contributed to the fragmentation of our thin-clients into the current collection of various different Javascript frameworks and methodologies. This document is an effort to consolidate best practices and serve as a reference to inform future development.

Framework Guidelines


Early thin-client works at Pentaho were primarily plain javascript with the exception of WAQR (Ad-hoc reporting) which was written partially with the Dojo 0.4 framework. We introduced GWT as a way of allowing our Java developers to contribute to thin-client development. Later efforts have been a mixture of JQuery and modern Dojo.

Looking forward

Going forward we're trying to consolidate as much new development as possible around a JQuery stack. Dojo will continue to be used for Analyzer and Interactive Reporting, major thin-client applications where Dojo is already in use and excels. GWT usage will be limited to shared code situations leveraging XUL such as the Pentaho Modeler.

jQuery Stack

jQuery alone is not a full development suite in and of itself. As such we've chosen the most popular technologies to augment jQuery with. Backbone for MVC, Handlebars for templating, and jQuery.UI for widgets

Javascript Doc

All Javascript should be documented using JSDoc notation Generation of doc will be added to a future update to Subfloor-JS

JSDoc notation guide

AMD and RequireJS

Scripts need to be written as AMD modules. Plenty of documentation exists out on the web. The details of our RequireJS AMD system are described in the link below
AMD Javascript Modules (RequireJS)

Unit Testing

Notes: Seems like RequireJS guys have worked around the issues with the major test suites out there, JSTestDriver, Jasmine.

Source maps

Source Maps allow the debugging on compressed and obfuscated javascript by mapping the compressed version to it's original source GWT, Dojo and RequireJS all support this. Future releases should be constructing source maps for all of the compressed javascript portions of our product.

CSS Considerations

CSS is quickly becoming as much of an issue as the scripts have been. Nothing has been committed to but below are some recommendations to consider going forward.

Pre-processing (compiled CSS)

There's broad interest in moving to a CSS pre-processor to generate consolidated CSS. SASS is the leading candidate to provide this. Much work needs to be done to migrate to a pre-processor but we should be able to start the transition soon.

Image Bundles (Sprites)

SASS and it's associated tool, Compass, provide this capability.

Standardize the DOCTYPE

We need to get to HTML4 strict as fast as possible. In addition, we should consider adopting one of the templates out there, HTML5-Shim or Boilerplate.

  • No labels