Sebastian, I don't see qx.bom.Flash, but I do see qx.ui.embed.Flash. I'm guessing qx.bom.Flash is now qx.ui.embed.Flash, right?
I can try to create a modified version of qx.ui.embed.Flash that includes whatever seems to be missing that caused it not to work for the demo. As far as building a full-fledged set of code that's worthy of the contrib, I fear I may be in over my head. Migrating the FABridge.js code into the Qooxdoo framework is my concern...I'm not sure where to start in order to make this a qooxdoo class. If you guys (or anyone else) can help me with this piece, I can probably handle the other parts (modifying qx.ui.embed.Flash). Perhaps there needs to be a qooxdoo class that handles the embedding of the flash and the setup of the "bridge"...Maybe qx.ui.embed.Flash should stay as it is, and we should add a contrib.ui.embed.FlashBridge that has all the heavy bridge things, so as to not weigh down the basic class for simple flash inclusion. -Mike -- View this message in context: http://www.nabble.com/Qooxdoo---Flex%3A-two-way-communication-demo-tp15198071p15205451.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
