Here’s an opportunity for our American Bay Area users to meet us: we’ll be on a trip in Silicon Valley in the week from June 25 to June 29 2012. Our purpose is to meet existing and new customers, to discuss business opportunities, trends, and the roadmap of Wt and JWt.

Are you in that area and would you like to schedule a meeting with us? Please mail me (wim@emweb.be) and we’ll give you a spot in our agenda!

Over the weekend, emweb moved to new offices. We’re now in a classy historical barn just next to Leuven, yet in the middle of Flemish pastures. The new offices are larger and more quiet than the previous one, so we’re sure they will give a continuous boost of inspiration to our projects :-)

You may have noticed that our fora and bug tracking system were down over the weekend. Whereas we first anticipated to be down only for an hour or so, the brand new modem at our new location decided to break down. We had to wait until today for a fix.

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.

We developed the hangman example in 2006 to demonstrate Wt’s principles to first-time users. The tutorial used this examples to walk through the libraries basic functions. Over the years Wt evolved and many new features were introduced, but the hangman example did not always follow these new developments.

We are pleased to announce to that we have updated both the hangman example source code and the tutorial text to the current state of Wt.

The hangman example now also talks about:

In the same effort, we also restyled the Wt::Dbo tutorial, but the contents remained largely the same.

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.