[Interest] HTML5 canvas support?

[Jason H]

To answer your questions,
1. No, You'll have to use CSS and such to style them, and come up with specific POST handlers for every possible input. If that's what you want then use Wt. The advantage here is that there is only ever one POST handler, which handles browser events like KEY UP/DOWN, and MOUSE MOVE, BUTTON UP/DOWN. Another advantage is you can style it using Qt Style Sheets. Really I made this so I could put a legacy Qt application "on the web". No [Adobe] plugins required!
2. UI Files, as made by Qt Designer or Creator. 

3. Don't worry about the license. My thing is that I want something for my resume. And I didn't want people "finishing" it before I had a better effort in place. With GTK's Broadway already complete, I will be creating Vaudeville, the Qt version, as soon as I get time and 5.0 is out (QPA interfaces will be 'finalized').




________________________________
 From: Jonathan Greig <redteam316 at gmail.com>
To: Jason H <scorp1us at yahoo.com> 
Cc: Interests Qt <interest at qt-project.org> 
Sent: Sunday, June 24, 2012 8:09 AM
Subject: Re: [Interest] HTML5 canvas support?
 

Jason,
I think it's cool. I would have been nice if you had at least included the private files needed, but I hunted them down and got it working;) I'm trying to build Qt remotely on a web server so I can try to use it for CGI scripts so maybe your concept will come in handy.

I'm not very familiar with some of Qt's web capabilities but wouldn't it make more sense to generate actual html checkboxes and radiobuttons for some of that? I can see some interesting uses for the canvas but was wondering if there is anything else that does say an entire html page layout? Is this uncharted territory or can Qt already do this?

Your license is a little odd. Why don't you just include your email in the files and state that your releasing the code into the public domain or just use the zlib license: http://www.gzip.org/zlib/zlib_license.html

Sorry for such a delayed response on this. I have been busy but knew I would come back to this to check it out. Luckily my memory served me well and found your post. Good job nonetheless, I will study and play around with it some more later this week.


On Thu, Mar 29, 2012 at 2:50 PM, Jason H <scorp1us at yahoo.com> wrote:

No one else thought this was cool?
>
>
>
>________________________________
> From: Jason H <scorp1us at yahoo.com>
>To: Interests Qt <interest at qt-project.org> 
>Sent: Wednesday, March 28, 2012 2:24 PM
>Subject: [Interest] HTML5 canvas support?
> 
>
>
>
>I think we should be able to paint to a HTML5 canvas.
>
>I created the attached PoC, modeled after QPicture. See main.cpp for an example.
>
>
>The code is released with the following license: 
>
>USE: Use at your own risk. Use it as you wish with no warranties or fitness expressed or implied. 
>COPYING/DISTRIBUTION: Don't claim the original code is yours, that would  be wrong. Please attribute the original code to me. (It's a resume thing) It is your responsibility to put my email address in the file headers. You may use the code in Open and Closed Source projects, and assign what ever license and copyright as you wish. I don't assert any copyright, just credit.
>
>Details:
>The rendering is "pretty good" I've noticed fonts are not pixel-perfect but pretty close. The HTML5 canvas system (at least in FireFox) needs a 0.5px offset to generate a line properly, so things may be a tad off.
>
>If you browser supports HTML
 I'm attaching sample output. (123.html)
>
>I'd love to see how you use this. Feel free to show me.
>
>_______________________________________________
>Interest mailing list
>Interest at qt-project.org
>http://lists.qt-project.org/mailman/listinfo/interest
>
>
>
>_______________________________________________
>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/20120625/f214a4f0/attachment.html>