Since long, Wt embedded snippets of JavaScript code (e.g. used for implementing the layout managers) directly in the C++ source code as string literals. This was not very developer friendly, and it also did not allow for using a minifier to compress the JavaScript.

We have just released 3.1.1 versions of Wt and JWt. These releases are maintenance releases and provide mostly bug fixes and feature polishing.

Update 22/2 An MSVC build problem has bene fixed in the C++ package, the new package version is now wt-3.1.1b

We were invited to speak on Wt::Dbo and JWt at FOSDEM 2010. For all of you who could not come to Belgium, we have put the slides online.

FOSDEM 2010:

FOSDEM 2009:

Last years presentation on Wt for embedded systems is still a nice introduction to C++ Wt.

Hey all,

I will be presenting two talks at Fosdem 2010 (6-7 February, Brussels, Belgium):

It would be nice to take the opportunity to meet with old and new Wt/JWt enthousiasts and meet up for beers on Saturday? Let me know if you are up for it (in comments or by email) and we will arrange for a nice pub in our capital.

Update Let’s meet up at the beer event on Friday!

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

Recently, Facebook provided us some information on their server park. They use about 30000 servers, and not surprisingly, most of them are running the PHP code to generate pages full of social info for their users.

We do not yet know what the outcome (if any!) of Kopenhagen will be, but what do these 30000 servers mean in terms of CO2? And what would be the impact of a more sane language instead of PHP?

When we developed Wt we followed the Qt model since we had experience while programming several desktop applications. Because those were mainly for engineering, we didn’t really need a database. Therefore, we never considered a database layer a must-have for Wt but mostly as a SEP.

Today however, many Wt applications talk to databases, and recommendations on the Wt mailing list for existing solutions were confined only to low level database API layers.

Finally, we bit the bullet and released Wt and JWt 3.

We wanted to have the JWt Reference Documentation clean and clutter-free before having the first solid release of the Java version of our web library.

We moved to a new major version number mainly because we needed to break the API for signals and slots. Some ideas for performance improvements required such a fundamental API change. We took the opportunity to also break the API in some other places, such as for a reworked WResource API.

But other than huge performance improvements and code clean-ups, also many other improvements happened over the last 9 months, and even more exciting features are sitting in unstable branches.