Do you have any experience with QML? Do I understand it correctly that by this idea, we would emit QML + JavaScript from Wt (instead of HTML + JavaScript) and target a custom viewer rather than a web browser or perhaps a combination of both ?

I think we should definitely add this to the Ideas page, but also discuss better what it means, and especially, how feasible it is ?

I am not sure WSqlQuery is needed, as it seems to overlap with Wt::Dbo::Query, but I do agree MVC integration of Wt::Dbo is needed. I’ve added this to the wiki Ideas page.

Now the HTML-based Wt Designer is a fantastic idea indeed. But it also has a number of
non-trivial challenges: how do we connect signals with slots? Wt does not have a moc and
does not use string-based signal/slot connections. how do we let the Wt Designer learn about new widgets ?

I do agree that you have the same issues with the Qt Designer approach to a large extent, so it makes sense to go by a HTML-based approach
rather that Qt…

I think this is all pretty difficult (I think it will definitely be the heardest Idea on the list), unless I am missing an obvious solution ?