The first problem you face is that each browser window represents a separate GWT application. The second one you face is that, to the best of my knowledge, there are only two ways those applications can communicate with each other: via the server, and via cookies. A third problem you face is that you're going to run into a fair number of users like me, who hate it when web sites try to take over their machines and create new windows, and have their preferences set so that you can't do that.
You can deal with the third problem by making sure that all your window creation is done with actual HTTP links (so the user can right- click on the link, and then tell it to open in a new window / tab). This pretty much requires you to implement History (which is a good thing in and of itself). The only way I can see to deal with the first two problems is to have a session cookie on the users machine that can be shared among multiple running applications, and then have REALLY "chatty" apps that are constantly sending updates to the server, and (by way of a Timer task set to go off every second or so) constantly checking with the server to see if anything has changed. If you have few users and a server with a good network connection, that might work. But it's not a solution that will scale very well. Greg On Feb 1, 9: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]> > > > . > > > 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.
