Thank you both for your input. Let me take a sec to try and iterate what I'm looking for more clearly.
The only thing I'm focusing on is user interaction with the form. Greg, you're correct in that I'm looking for the form to lack a save button. When the user changes data in the form, that change is made asynchronously in the record in the database that the form represents. It doesn't matter how that change gets initiated (maybe form widgets triggering an "onblur" event, whatever). I don't necessarily need a persistent connection or socket or anything fancy like that; just a simple way to truck data from the form to the database, initiated by user interaction with individual form widgets. I'm not sure if anyone's had this requirement yet. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Require-a-live-form-what-are-my-options-tp5032609p5038181.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
