4 ms·

I find it irritating that even after reading their front-page and the "How you can use WT" I still have no clue what it is supposed to be. Is this an embedded b

I find it irritating that even after reading their front-page and the "How you can use WT" I still have no clue what it is supposed to be. Is this an embedded browser? Is it a C++ app GUI that allows you to use HTML like construction? Is it an emscripten application? How can it work without JS enabled? Is it compiled into pure WebASM? What the heck do they mean by connection? What connection? What does have PDF and DB to do with all that? Etc. Very poor marketing imo. After reading all this I have even less clue what it is supposed to do.

roywiggins 6y ago
It works without JavaScript because it can render everything server-side. If the user has JavaScript it uses websockets or Ajax to fetch updates from the server, but if it doesn't have those it can just reload the whole page like you would with a CGI application. "Qt, but for web applications" would be a short and basically accurate descriptor. You slot together widgets in C++ and it works out how to lay them out and connect actions taken by the user to your event-handling code, which lives on the server. The PDF thing is for rendering reports to PDF, instead of HTML. Not useful unless you're in a corporate sort of space, but when you want a PDF report you do want something like that. The DB thing is an ORM that makes basic CRUD operations on your database easier.
- hellofunk 6y ago
  Oh strange, I completely assumed from the start that it was referring to front end C++ using Webassembly, similar to how some rust libraries do it. Never occurred to me this is server side.
  - chrismorgan 6y ago
    Wt comes from many years before WebAssembly.
- marta_morena_25 6y ago
  Yeah it dawned on me the moment I hit sent... That this is probably something like ASP.NET for C++. Probably some people still need that :). Legit use case, just I think they need to work a lot on their messaging.

roywiggins 6y ago

It works without JavaScript because it can render everything server-side. If the user has JavaScript it uses websockets or Ajax to fetch updates from the server, but if it doesn't have those it can just reload the whole page like you would with a CGI application. "Qt, but for web applications" would be a short and basically accurate descriptor. You slot together widgets in C++ and it works out how to lay them out and connect actions taken by the user to your event-handling code, which lives on the server. The PDF thing is for rendering reports to PDF, instead of HTML. Not useful unless you're in a corporate sort of space, but when you want a PDF report you do want something like that. The DB thing is an ORM that makes basic CRUD operations on your database easier.

hellofunk 6y ago
Oh strange, I completely assumed from the start that it was referring to front end C++ using Webassembly, similar to how some rust libraries do it. Never occurred to me this is server side.
- chrismorgan 6y ago
  Wt comes from many years before WebAssembly.
marta_morena_25 6y ago
Yeah it dawned on me the moment I hit sent... That this is probably something like ASP.NET for C++. Probably some people still need that :). Legit use case, just I think they need to work a lot on their messaging.