Wt & JWt 3.3.8 RC1, and Wt 4.0.0 RC1!

  • Posted by Roel
  • Tuesday, July 4, 2017 @ 19:05

We’re simultaneously releasing a first release candidate for Wt and JWt 3.3.8, and we’re proud to announce the first Wt 4.0.0 release candidate!

Get Wt 4.0.0 RC1 here: wt-4.0.0-rc1.tar.gz

All changes between Wt 3.3.7 and 3.3.8 RC1 also apply to Wt 4.0.0 RC1. For changes specific to Wt 4, see the release notes.

Here are the main links for Wt 3.3.8 RC1:

This release fixes several bugs, and introduces a few small features, like OpenID Connnect support.

Users of JWt need not worry. While there’s no JWt 4 yet, this does not mean we’re abandoning JWt. Most changes in Wt 4 are very specific to C++. We will work on updating our Wt to JWt porting toolchain after the release of Wt 4 so that JWt can stay in sync with Wt.

Tags:
9 comments
  • Posted by anonymous
  • 2 months ago
anyone have tutorial to install wt 4.0.0?
  • Posted by anonymous
  • 5 months ago
Great. Thanks for your efforts.
Do you have any information when the final version will be available?
How can we use 4.x, if we have licensed 3.x?
  • Posted by wim
  • 5 months ago
While things are usually ready when they are ready, I think it's safe to expect the final 4.0 before the end of the summer.
The license does not make a distinction between Wt 3 or Wt 4, so you can use all Wt releases released during the Maintenance Period of your license, or any extensions thereof.
  • Posted by anonymous
  • 5 months ago
Any chance we see a .NET version, based on a source-to-source translator similar to that of JWt?
  • Posted by wim
  • 5 months ago
We have discussed this regularly here at emweb. I came to the conclusion that .NET web developers are more likely to stick to the MS frameworks rather than to use a 3rd party framework for their web developments, and that as such it would be very hard to get some popularity. Would you agree?
We use JWt intensively for projects here at emweb.
Technically I think it's feasible. Any chance you'd sponsor such a development? ;-)
  • Posted by anonymous
  • 5 months ago
.NET + Angular is becoming the most popular way to develop webapps. .NET is used for the backend, Angular for the front-end. In my experience as a project manager, the Angular part ends up being slow and expensive to develop. If Wt.NET is as easy as regular Wt, then you have a market.
Unfortunately, my company does not invest in such research projects unless we do it internally. The fact that the C++-to-Java source-to-source translator is not available does not help either :-(
  • Posted by wim
  • 5 months ago
Your request is noted. If we see this request a lot, Wt.NET may happen... Please understand that this must be economically senisble for us, since creating, documenting and maintaining such a port is not a small task.
  • Posted by anonymous
  • 5 months ago
Version 4 release on 4th. Like a clockwork!
  • Posted by anonymous
  • 5 months ago
The new features and updates you've included with this release are outstanding. Congratulations on reaching this significant milestone!

Contact us for more information
or a personalised quotation