Final packages for version 3.2.1 have been uploaded:

We’ve uploaded new release candidate packages. These contain only a number of fixes for corner cases, and thus nothing out of the ordinary.

It thus looks like these will be renamed to the final 3.2.1 packages later on, so now is the time to give them a spin!

With 3.2.1 out of the way, we are starting work on 3.2.2 which will included a long needed (and already half staged) overhaul of the layout managers which is becoming a dominant attractor of bug/annoyance reports.

Totally unrelated, but interesting in its own right, Gabor Vitez wrote on his experience of using JWt from JRuby within an embedded Tomcat server, using Servlet API 3 (and thus scalable server push).

A new version of the library, with a typical mix of bug fixes and new features.

Here are the main links:

We’re trying a new release scheme, with release candidates first to enjoy wider testing, in an attempt to avoid release glitches that happened all too often in the past.

Not sure whether it’s just a gimmick or something useful, but recently we saw some online examples (e.g. by Google) of authentication by delegating the authentication to your smart-phone using a QR code (the odd thing which your mother in law just recently asked you what it was, since it started appearing in all kinds of magazines).

In any case, it sounded like a good test (to us and to you) for the extensibility of the authentication framework we added to Wt in 3.2.0.

A new version of the library packed, with a fair share of new features.

We bumped the mid-version number, not only because this release brings a lot of new functionality to the plate, but, we also did some changes that may require existing users to be modified — read the release notes carefully.

A large patch landed in our git repository last week. This was the result of the merge of a development branch that has kept us busy over the last months.

In a series of posts, we will give an overview of the new modules that were added to Wt, starting here with Wt::Auth, an authentication module.

In future posts, I will discuss other novel modules such as Wt::Http (Http client), Wt::Json (JSON library), and Wt::Mail (SMTP client), which were developed under the impulse of the authentication module.

A new version of the library packed with lots of bug fixes and a fair share of new features.

A new version of the library packed with lots of bug fixes and a fair share of new features.

A new version of the library packed with lots of bug fixes and a fair share of new features.

I’ve come to learn that Wt (and JWt) are opiniated frameworks. I like the word: Wt is not just different from other traditional web frameworks, but it is deliberately so.

Yes, Wt is a C++ library but focusing on this particular oddity is missing the point. It could have been implemented in any language, including your favorite. It just happens that we like C++, don’t believe that it is that complex (at least not compared to web application security) and wouldn’t trust anyone to implement a (secure!) web application who cannot manage a pointer deallocation.

Anyway, one of the unique things in Wt is how it handles URLs (traditionally called URL routing). Wt has an internal path API (implemented as three methods in WApplication) which allow you to:

In short, you can create a modern Ajax application with perfect graceful degradation (or progressive enhancement) and search engine accessibility.