Hey all,
I've got a lot of work done into the 2.0 experimental branch. The base of jquery has been integrated and the basic effects and events have all been integrated (probably small bugs here and there).
Currently in 1.0 and 1.1 the javascript is rendered inline with the control which is the old way of doing things. Now what happens is that the QForm renders all of the actions inside the document ready.
Also, each control now renders through a template file. You can customize the way buttons, inputs and basically any control is rendered.
if you want an example checkout the experimental branch of 2.0 (experimental/qcubed2jquery) and run the sample.php for a quick example of what is going on.
If you have an ideas about performance improvements let me know or share your thoughts in the forum.
Jon Kirkpatrick / Bas

Hey Baselius,
I'm trying to pick up the code to start integrating jQuery 1.4
First, great job so far! Integration of jQuery seems mostly complete. I'm now looking into adding some stuff from jQuery 1.4
Question: it seems you also started templating for the controls. I would like to find out more about this. Is there any post you refer to on how to handle this? I noticed that only a limited set of controls have this integrated, the other controls seem simply return nothing (no templates exist for them). Should we start creating templates for each of these controls?
Greetings,
Kristof
To answer my own question:
http://qcu.be/content/proposal-improving-generation-control-html
http://trac.qcu.be/projects/qcubed/wiki/ImprovingGenerationofControlHTML
Has any of the other core contribs had a look at the architecture? Is this basic proof of concept the way to go forward? If so, I'll start creating templates for the remaining controls as well.
K.
Thanks, you rock!
this is really exciting stuff. A QCubed built on JQuery! I would pay money for that :)
Shh! Don't tell him that!
...thanks basileus