Hi, Cutelyst ain't about writing websites like desktop applications, QtCore and QtNetwork are great modules which don't require any GUI code, Qt is mainly used due to it's very convenient classes, and your HTML can be written with a templating system.
Originally Posted by gufide
I've written a small FAQ https://gitorious.org/cutelyst/pages/Home
since some of you are confused, I wrote this small FAQ to help out sorting out WTF is this project about :P
I think what gufide means is that this is a Component based framework, which implies an approach to developing web applications similar to desktop applications (UI object trees). A common problem with Component based frameworks is that styling and theming is very hard to keep separated from code (see for instance the addStylingClass calls in the examples). Another is that the definition and structure of the UI elements are defined in code. In Desktop UI frameworks this is often externalized (e.g. think QML for Qt) after years of maturation. A third issue is that in order to process event callbacks on UI objects, the whole object tree needs to be reconstructed on every request, which leads to relatively much overhead.
Originally Posted by dantti
Sure that's what I'm telling Cutelyst is not. One of the reasons I don't like wt and other frameworks is that I don't like the idea of generating HTML from code, I'd rather use a template system. However Cutelyst doesn't even enforce a templating system, you can think of Cutelyst as a nice API for dealing with HTTP protocol, with helper plugins to deal with session cookies (that can be stored anywhere), authentication, authorization and so on, so if you want to use wt to render HTML and Cutelyst to have the processing requests logic that's something possible.
Originally Posted by accumulator
So far I use Grantlee (Django) templating for my websites, the logic to connect to DB and what to pass for the template is done in the C++ code using the nice Qt classes (QtDatabase, QtCore, QtNetwork...).