It's definitely USE_REMOTE_UI=true to get the SWING UI, which semantically makes sense anyway.. (yeah REMOVE was a type, fingers faster than brain).
As for the rest, I'm sure I could fiddle with the devmode to fix some of the navigation annoyances, but with my workflow the window works much better for me in any case. I should just post issues, but it would be nice to have the swing ui change to the new browser tab when a new browser connects, and for scrolling to stay at the bottom of the content.. Thanks jk On Apr 16, 9:16 am, Rajeev Dayal <[email protected]> wrote: > On Fri, Apr 16, 2010 at 11:03 AM, kozura <[email protected]> wrote: > > Ah thanks Rajeev, been looking for that, it works except you have to > > set USE_REMOVE_UI=true. > > Really? I'm glad it's working, but I think the right way to set it is to > define an environment variable of "USE_REMOTE_UI" and set its value to > "false". That should cause the Swing UI to pop up. Does that not work for > you? > > And since you asked... Maybe it's a little "I'm used to it", but I > > > find the Swing UI much more convenient than the Development mode view: > > > - Clear tabs for Jetty and each browser window that comes up, > > navigation is tricky in the Eclipse DMV tab > > Ah, are you saying that you'd prefer a different tab for each Jetty instance > and browser window, instead of having nodes in a Breadcrumb view? Note that > you can switch the layout of the DMV - look at the view settings, and switch > the layout to "Tree" > > > - Handy dandy "Launch in Browser" and "Restart Server" buttons > > The DMV also has the "Restart Server" button. We're working on making the > URLs that pop up in the DMV launchable. > > > - Separate window and process makes it easy to see that I have it > > running, close it to end the process, etc. In dev mode I have to > > notice the tab, switch to it, and stop it from there to end to > > process, not nearly as convenient. In this mode I often rerun app > > only to find conflicting port because I didn't see and close the old > > process. > > - Separate window also doesn't compete with my code for space, makes > > it easy to have a large log and still browse my code in my setup. > > Personal preference, but hey. > > Understood. > > > > > The first two could just be improvements in the Eclipse DMV tab, but > > don't assume everyone's workflow is improved through the "convenience" > > of everything being built into eclipse! > > Thanks for the feedback - it is definitely useful! > > > > > > > jk > > > On Apr 16, 8:41 am, Rajeev Dayal <[email protected]> wrote: > > > To clarify, GWT 2.0+ no longer uses the Hosted Browser - it makes use of > > > Out-Of-Process-Hosted-Mode. See > > > code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.htmlfor > > > more information. > > > > When using GWT 2.0+ with the Google Plugin for Eclipse, you'll see the > > > "Development Mode View" pop up whenever you launch a GWT 2.0+ > > application. > > > From this view, you can see the module-based logs, and restart the Jetty > > > server. Server logs are show in the console view. > > > > If you prefer the Swing UI that GWT 2.0+ has (as opposed to the > > "Development > > > Mode View"), set the following environment variable in your launch > > > configuration: > > > > USE_REMOTE_UI=false > > > > However, we'd be curious to know why you actually prefer the Swing UI to > > the > > > Development Mode view :). > > > > Thanks, > > > Rajeev > > > > On Fri, Apr 16, 2010 at 7:40 AM, Christian Schuhegger < > > > > [email protected]> wrote: > > > > I just wanted to mention that I have the same problem after I updated > > > > the google eclipse plugin to its newest version. I was using gwt 2.0.1 > > > > and gae 1.3.1 before. Now I ahve gwt 2.0.3 and gae 1.3.2. > > > > > -- > > > > 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%[email protected]> > > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > > 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%[email protected]> > > . > > > For more options, visit this group athttp:// > > groups.google.com/group/google-web-toolkit?hl=en. > > > -- > > 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%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > 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 > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
