Some news on the Wt and JWt development front: we have just released 3.1.0 versions. These releases contain many new features, including the features that we announced in a previous post.
Edit: The c++ package was missing the test/ directory
The highlights of this release are:
We have added an Object-Relational-Mapping (ORM) layer to Wt, of which we provided a preview in a previous post, and if that has wettened your appetite, there is a tutorial with more detail. Since its conception, it has already been exposed (unexpectedly, through this very blog) to the famous slashdot effect, without a single hick-up!
There is currently only a SQLite3 backend, but a contributed MySQL backend is already sitting in my mailbox and is surely to make it for the next release.
This is a C++ only addition. For JWt, we recommend using Hibernate/JPA as an ORM layer.
Many users have complained that the default look of Wt’s widgets is boring, and we must confess, we have always given priority to functionality rather than looks. We intend to change this with the advent of theme support. All CSS that was previously provided within the inline stylesheet by each widget class, has been pushed out to external style sheets, and a small API to select a particular theme was added.
It finally occurred to us that many things related to CSS-based layout could be simplified if we admitted to support XHTML templates. Unlike traditional frameworks, Wt templates describe the XHTML for a single widget. Within a template, variable references may resolve to widget instantiations or string contents. This simplifies those situations where you would like to express the layout using XHTML/CSS, rather than using a nested hierarchy of WContainerWidgets.