Wt & JWt 4.5.1 released!

  • Posted by Roel
  • Thursday, October 7, 2021 @ 20:18

Don’t worry guys, we didn’t forget about Wt. Wt 4.6.0 will be coming soon, but it’s about time we get 4.5.1 out the door, with all its bug fixes.

In the meantime, we’ve started to make better use of the roadmap feature of Redmine, so going forward we intend to include all changes on the roadmap.

More information in the release notes.

Here are the links:

Binary builds for Windows are available on the GitHub releases page.

Tags:
10 comments
  • Posted by anonymous
  • one month ago
Is Wt a html over the wire (hotwire) framework?
https://hotwired.dev/
  • Posted by Roel
  • one month ago
I had a brief look at it, and no, Wt isn't quite like that. Wt uses widgets that are rendered out to JavaScript code that updates the DOM.
The hotwire concept seems to be that a server renders HTML and a client side framework figures out how to update the page.
  • Posted by anonymous
  • one month ago
JavaScript over the wire
  • Posted by anonymous
  • one month ago
Thanks. Which approach is better?
  • Posted by Roel
  • one month ago
It appears to me that hotwire is designed for developers that use more classic '00s style web frameworks. Basecamp is a classic Ruby on Rails company, so the HTML over the wire concept probably makes a lot of sense for them.
Wt on the other hand is built around widgets and the signal-slot concept known from desktop frameworks like Qt. Wt turns JavaScript events into server side signals, and renders updates to widgets back to the browser.
While Wt is a complete web development framework with client side and web server side parts, hotwire is only one part of the puzzle, to be supplemented by some server side web framework.
I think it just depends on the style of application development that fits best for you or your team.
I'd say that Wt's widget based development concept does have some automatic security benefits, since the only way that the client can interact with the application is by sending events that belong to some widget that is currently in the widget tree. The client can't simply send a request out of the blue.
  • Posted by anonymous
  • one month ago
I think that WTemplate is similar to html-over-the-wire. Widget is javascript-over-the-wire with dom diffing done one server side. Correct me if i'm wrong.
  • Posted by anonymous
  • one month ago
Thanks. I just was surprised that there are an incompatible change to version 4.5.0 (maybe more?)
The QueryModel::setHeaderData wasn't usable with three parameters any longer.
  • Posted by anonymous
  • one month ago
If there is an incompatible change there's a bug. I don't see why it wouldn't be usable with three parameters?
  • Posted by Roel
  • one month ago
I tested it and indeed, the three argument version is not exposed in QueryModel anymore. That'll have to be fixed.
  • Posted by anonymous
  • one month ago
Thanks.

Contact us for more information
or a personalised quotation