cboulanger schrieb: > Fabian Jakobs schrieb: > >> Leander Hanwald schrieb: >> >> >>> Hi all, >>> >>> only in theory (didn't tested it): >>> >>> Shouldn't it be possible to add and remove qooxdoo widgets inside of a >>> native window and control them from inside of the main window? >>> >>> Like: >>> >>> 1. Create native window >>> 2. Add class XYZ to it (the divs and co., the code is running inside of >>> the main window). >>> 3. add events to class xyz >>> 4. events fired, main window do xyz >>> >>> Since you can manipulate html in js of an child native popup window (I >>> think I did it in the past ;) ), this should be possible, right? >>> [I don't know if the layout manager can do this] >>> >>> Greetings, >>> Leander >>> >>> >>> >> Hi Leander, >> >> I think this is not possible with qooxdoo 0.7. First there must be a >> ClientDocument instance for the IFrame but ClientDocument is currently a >> Singleton. Second the event manager only listens for events in the main >> document. Maybe with a bit of hacking qooxdoo internals you could get it >> to work. >> >> We plan to remove these limitations for 0.8 >> >> Best Fabian >> >> > It is most certainly not possible. The context of all the objects in the > parent window is the DOM and the execution object of the parent window. > All DOM and other action will be executed in the parent window. At this > point, you need a complete additional object tree in the opened window. > If this can be changed for 0.8, that would be a real achievement! Go for > it, qooxdoo team!!! >
I think I have to clarify this a bit. There are two ways to add qooxdoo widgets to add widgets to an Iframe: 1. Run all the code in the parent application and create the widgets from the context of the parent application into the IFrame. This requires access the the IFrame DOM and is of cause protected by the same origin policy. The new event layer already supports attaching events to DOM elements inside of other documents. 2. Write a separate qooxdoo application for the IFrame but instead of packaging all qooxdoo classes, use the qooxdoo classes from the parent frame. Again only possible if both applications come from the same domain. We plan to support the first solution. The second one seems to me much harder to implement but maybe it is possible as well. Best Fabian > Christian > > ------------------------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas Gauger, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
