> Good idea, but QxIframeTransport was never thought to be used directly. > This is part of the new transport implementation. You can take a look at > these "Transport_*.html" demos files.
Despite their name, all the Transport_* only uses the classes in the QxRequest hierarchy. I haven't figured out which, if any, relation QxRequest have with QxTransport. > Currently qooxdoo doesn't feature any special form handling. You must do > it your own. But I think it's a bad idea to directly use > QxIframeTransport. Better is to try to integrate this using the real > transport API and handle it somewhere in QxRequest. It is not so easy because, as you probably already know, inputs of type "file" has to be handled specially. You need to have a form that you submit() and that form needs to contain the file input and the file input need to have been attached to the document. QxIframeTransport is the only suitable class I have found because it has a private _form attribute to which the file input can be appended. If there is a better way, I'd really like to know because relying on the _form attribute of QxIframeTransport is damn hackish. :) -- mvh Björn ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
