Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-12-15 Thread Ralf Nieuwenhuijsen
Ah, silly me, i typed the wrong bug number! And this one already has some nice example code attached. Oh, well, thanks for the quick response! For now, i'll just go the MDI way and I'll just make sure that in the future I can easily switch to HTA style mode. (not that i'm using internet explorer,

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-12-15 Thread Alexander Back
Hi Ralf, Ralf Nieuwenhuijsen wrote: > It seems that that bug is fixed in svn (according to the bug page). > Does this mean, this now works? The bug is still in the status "NEW", so this issue is still open to fix. As you can see at http://bugzilla.qooxdoo.org/show_bug.cgi?id=1529 we are

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-12-14 Thread Ralf Nieuwenhuijsen
It seems that that bug is fixed in svn (according to the bug page). Does this mean, this now works? Ifso, does anyone (perhaps you Heiko) have an up-to-date implementation of QxNativeWindow. If i'm not mistaking it should be possible to do something like var nw = new QxNativeWindow(); nw.getRo

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-11-03 Thread Heiko Stübner
Am Montag 03 November 2008 schrieb Fabian Jakobs: > thank you for this investigation. Could you open a bug report for this. > This is something we want to support and from what your report we are > not far from doing so. It would be great if you could attach a small > test program to the bug report

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-11-03 Thread Fabian Jakobs
Heiko Stübner schrieb: > Am Mittwoch 29 Oktober 2008 schrieb Heiko Stübner: > >> _findHandler() builds the cache key as DOM_div_mouse* and finds a cached >> handler for it. But this is the handler for the main window, where instead >> it should build a new mouse-handler instance for the target-w

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-10-30 Thread Heiko Stübner
Am Mittwoch 29 Oktober 2008 schrieb Heiko Stübner: > _findHandler() builds the cache key as DOM_div_mouse* and finds a cached > handler for it. But this is the handler for the main window, where instead > it should build a new mouse-handler instance for the target-window. > > The mousehandler itsel

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-10-29 Thread Heiko Stübner
Am Dienstag 28 Oktober 2008 schrieb Heiko Stübner: replying to myself with results for now: > Am Dienstag 28 Oktober 2008 schrieb Fabian Jakobs: > > This is the way I would try to do it. Just load an empty HTML file into > > the window and once it is loaded attach a qx.ui.root.Application to the >

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-10-28 Thread Heiko Stübner
Am Dienstag 28 Oktober 2008 schrieb Fabian Jakobs: > Hello Heiko, > > you are pretty much a pioneer in this area. We have designed 0.8 with > multi-document support in mind be we have never tried to actually do it. Great, I can conquer a little part of the world myself :-) > > My second idea was o

Re: [qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-10-28 Thread Fabian Jakobs
Hello Heiko, you are pretty much a pioneer in this area. We have designed 0.8 with multi-document support in mind be we have never tried to actually do it. > Hi again, > > my objective is to put parts of an application in a native javascript window, > so it can be moved next to the original wind

[qooxdoo-devel] Using qooxdoo in native Javascript-Window

2008-10-28 Thread Heiko Stübner
Hi again, my objective is to put parts of an application in a native javascript window, so it can be moved next to the original window on a second screen. Additionally I need qooxdoos functionality in this window. Creating a second application in the window does seem to be a bit much overhead,