After some more consideration I have dropped my way of doing it. In theory it would be possible by sharing an EventBus between the different windows. By using JSNI I could do "window.eventbus = [email protected]" and then do "window.open(someotherwindow)". In this other window I could do "[email protected] = window.opener.eventbus". If this would work in practice I do not know as I never got the point where I tested it, but I am writing it down in case someone else stumbles over this thread.
The most influential reason for not doing it is that I have no idea if it would work in the end. Further, I think it would heavily complicate things if the user closes the opener window. Also it requires every view to be in the same domain, and failing to do that would break the whole app. And I do agree with Greg when he says that most users probably would not like it. Thanks for the input guys. On 1 Feb, 17:36, Jeff Schwartz <[email protected]> wrote: > If I were dealing with as dense an amount of data as you seem to be dealing > with I'd look to use 1 physical window with possibly multiple view ports to > present it all. Just MHO and YMMV. > > On Tue, Feb 1, 2011 at 10:20 AM, Terje Andre Johansen < > > > > > > [email protected]> wrote: > > As far as I can see this would force me to re-render each view on > > change and also make it harder for a user to compare the different > > views. Further if the user has multiple screens, I think using several > > Windows is better than using only one. Your idea is good, however its > > not what I want to do if it is possible to do it the way I described. > > > If am not mistaken, if the user is using Chrome I would actually be > > able to use several cores in the CPU for rendering if the application > > is split between different Windows? Correct me if I am mistaken. > > > On 1 Feb, 15:17, Jeff Schwartz <[email protected]> wrote: > > > Have you considered using GWT tabs or some other ui feature (roll your > > own > > > if you have to) that would provide multiple views other than opening > > > multiple browser windows or tabs? I really don't like it when > > applications > > > open multiple browser windows or tabs and consider that a UI faux pas :). > > > > On Tue, Feb 1, 2011 at 8:44 AM, Terje Andre Johansen < > > > > [email protected]> wrote: > > > > I am working on a project where I am using GWT to visualize biological > > > > data in several ways. This is done by searching for a gene by name, > > > > and what I want to happen is for each visualization to get its own > > > > window to display its data. The reason for this is that there is huge > > > > amounts of data, and trying to fit more than one visualization in one > > > > page is not a ideal way to do it. > > > > > One of the goals for the project is to enable interaction between > > > > these visualization. In short this means that if a user clicks on a > > > > gene in one view, a similar event/method should be invoked in the > > > > other views as well. The newly opened windows will have the same > > > > parent and be in the same domain. > > > > > I have looked at the GWT API, and so far only found the static void > > > > method Window.open(url, name, features). As far as I understand this > > > > means that I cannot get hold of the new window as an object to invoke > > > > methods on. Neither did I find the equivalent to the JS method > > > > window.opener() to get hold of the parent object in the newly opened > > > > window. > > > > > I am wondering if anyone has worked with a similar problem and got > > > > some an idea of how to enable Window interaction using GWT. > > > > > Help is appreciated. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Google Web Toolkit" group. > > > > To post to this group, send email to > > [email protected]. > > > > To unsubscribe from this group, send email to > > > > [email protected]<google-web-toolkit%2Bunsubs[email protected]> > > <google-web-toolkit%2Bunsubs[email protected]> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > > *Jeff Schwartz* > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%2Bunsubs[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > *Jeff Schwartz* -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
