Completion Release

Since Tangram reached more than the originally intended features it should now be a 1.0 release. The name Tangram points out that the main objective was to create applications from a fixed set of modules and options which can form nearly any shape you would need. You can start quickly with a limited set of functionality and let the application grow. For many extensions you will not even need a deployment but a change in the data repository forming small and stable cores where the application as whole can be modified to changing requirements quicky, easily and securely.

We provide object oriented templating for objects from JPA, JDO, EBean, and CoreMedia repositories. The core system emphasises dynamic web programming through CSS, JavaScript, Velocity Templates, and Groovy Codes in the repository together with basic CDN support, code minification, and caching support.

The implementation of authentication and authorization now uses the pac4j set of libraries to provide a seamless and easy integration of plain user lists in files or the repository, OAuth providers, OpenID providers, Google App Engine user service and others for the web application and the base system itself.

Except for CoreMedia we provide a generic web editor which is now responsive (there is now separate mobile editor anymore) which can be loaded from the respective cloud locations of the used components (CKEditor, CodeMirror). Also it can be extended with our dynamc web programming facilities.

Appart from the about 40 minor improvements and clean ups following the 0.9 path, this release adds Google Guice support through a module called guicy. It uses Google Guice and Groovy code to reach the same level of dependency injection for the configuration of the applications as provided through the spring module for the springframework and the dinistiq module for the dinistiq minimal DI library.

One real limitation is the older set of JSP/Servlet APIs which need to stay in place to support the Google App Engine. So this is the final release to support the App Engine to be able to move ahead to newer APIs for several areas. This will not be achieved in the 1.0 branch.

The 1.0.1 Patchlevel fixes a few glitches mostly related with the packaging of the artifacts which made some dependent projects fail during build