[Interest] [OT] Re: how to develop the HTML5 application(web application) by using Qt?

[Jason H]

It is a very interesting project. I have fiddled with it. Someone suggested that the fork of Qt be called Cutie, or something like that, but that's what I called my efforts to unify Qt and Wt. I ended up creating a  version of UIC that would take a UI and put out a Wt-classed and #included version of Qt screens, so that you essentially had a form builder. The goal was to have one code base, with minor changes depending if you wanted local (Qt) or web (Wt). I got pretty far with it, but eventually because Wt uses boost, I was not able to keep things uniform enough for it to be advantageous. 


My current effort is now, once Qt5 is released to implement a HTML5 canvas interface using QPA. I already have a a traditional QPainter interface working. That's Vaudeville. I named it that because the GNOME effort is called Broadway. I downloaded braoadway the other day and I'm going to see how closely I can keep Vaudeville to Broadway. One significant change is I want to avoid the use of SPDY.





________________________________
 From: Till Oliver Knoll <till.oliver.knoll at gmail.com>
To: Qt Interest <interest at qt-project.org> 
Sent: Wednesday, June 20, 2012 9:17 AM
Subject: Re: [Interest] [OT] Re: how to develop the HTML5 application(web application) by using Qt?
 
2012/6/20 Konstantin Tokarev <annulen at yandex.ru>:
> You can also try Wt [1] - it allows you to write web applications in C++ (you may even use non-GUI Qt stuff!)

That looks interesting! In fact, when browsing the documentation it
seems to closely resemble the Qt API ;)

My first understanding after browsing the description is that the Wt
framework is a Server/Client framework, not a toolkit which
transmogrifies your existing C++ into JavaScript/HTML5 which could run
on its own.

So whereas a "HTML5 app" in theory can run on its own (once you have
downloaded and installed it, using platform/browser-specific
functionality), the browser does all computation alone. With Wt you
always need a server connection, because all the logic resides on the
Server (as C++ code). That's something to keep in mind.

>From what I understand you develop your logic as Server component,
which calls the appropriate Wt API, which then renders the
corresponding HTML output which is presented to the Client (browser).

Cheers, Oliver

p.s. There still seems to be a bug in that framework: every n-th
minute it tries to redirect my Firefox to another URL, but even when
pressing Cancel I am thrown back to the previous page ;)
_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20120620/961a3a37/attachment.html>