Christian, just to clarify things: You refer to a bug that relates to a deep technical topic, event handling across windows. But what is not clear to me from your description, which (application) problem are you trying to solve? You mention you want to open multiple windows and the viewport gets cluttered. But what is the problem then? Closing the windows? Working in multiple windows? Removing them entirely from view and getting them back again? I'm not getting it.
T. On 06/09/2010 10:35 AM, panyasan wrote: > > Hello, > > I assume that bug 3086 [1] is probably still very low in priority, so I want > to do some advertising and hope for support from the community - or get > convinced that I am the only one who think that this is important. > > qooxdoo windows (qx.ui.window.Window) are pretty and work very well. > However, there are use cases in which they are not as useful as having > native browser (popup) windows: if you need to work with data that is shown > in your main application AND an additional widget in wich other data is > displayed. The qooxdoo windows, which cannot be moved out of the browser, > get in the way of working. > > An example. I work on an application which manages bibliographic data. I > select a reference and get a list of potential duplicates of the reference > in the database. Now I need to open each of the potential duplicates and > compare them to the original record. If I do this with qooxdoo windows, > unless I have a REALLY large screen, the available viewport is quickly > cluttered and I can no longer see the main record. > > I could, of course, simply fire up a new browser window and load an > additional instance of the app, and then search for the duplicate record. > Bad. Takes a long time and defies the idea of being able to quickly scan the > duplicate records. > > Instead, I would like to use a native browser window which simply extends > the qooxdoo object tree, i.e. the qooxdoo application uses it as an > additional viewport. Support for this has already been added long ago. But > there is a bug in the event registration system (Seee [1]) that prevents > this from working. > > We seem to be very close to get this working and I think it would really add > to the usefulness of the framework. So I would be very happy if the devs > could devote some time looking into it - if more people voiced their > support. > > Thanks, > > Christian > > > > > > > > > > [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=3086 ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
