January 22nd, 2010| 
After the feedback received from my previous posts, I continued where I left of integrating all other events into qcubed.
For now, the following are done:
- Mouse Events: all with exception of toggle() and hover(): those events require 2 actions to be performed instead of 1. QCubed currently cannot handle this
- Keyboard Events: All integrated and removed some code for browser specific behaviour
- Form events: Form Events: all integrated, except onsubmit()
- Browser Events: error(), resize(), scroll(): not integrated
- Document Loading: load(), ready(), unload(): not integrated
- Event Object: not integrated
Q/A:
- toggle and hover can accept 2 parameters: should we support that through QCubed?
- How about integrating error(), resize() and scroll() ? Do we want/need this? Suggested approach?
- Should we initialize QCubed through ready() event instead of normal at the end of the page?
- Event object: I would love to be able to access the data on the server side! Can we somehow serialize (or json) this object and pass it in the form, so we can access the data on the server?
Kristof
1) Initializing through document.ready instead of at the end of the HTML: absolutely yes.
2) Toggle and hover accepting 2 parameters: seems low priority, I'd open a ticket to track this later.
What's the difficulty of toggle and hover? Yeah, please open a ticket describing this. Looking at the existing QCodo js, it should be very simple to replicate using jQuery, so I'm confused.
If someone wants to use jQuery's toggle and hover functions, there will be nothing stopping them from using the extra parameters, I think most things exposed through QCubed is mostly going to be for backwards compatibility.