On Wed, Oct 7, 2009 at 2:34 PM, jastram <[email protected]> wrote: > > Hello Jason, > > > Sounds like a neat idea, kudos to getting the Hello World to work! I'm > > curious how it's set up--I assume the Eclipse view showing the GWT app a > > browser-backed view? > > Yes, that was actually fairly easy. Here is the central code from the > ViewPart: > > public void createPartControl(Composite parent) { > browser = new Browser(parent, SWT.FLAT); > int port = JettyRunner.getServerPort(); > String url = "http://localhost:"; + port + "/document"; > browser.setUrl(url); > } > > JettyRunner resides in another plugin for launching Jetty. The call > to getServerPort() triggers the loading of that plugin. So if the > view isn't shown, Jetty isn't started. JettyRunner then looks for a > free port, that's why I have to query for it. > > > Are the plugins you depend on separate projects in your workspace? If > so, > > you can add them as linked source folders to your main GWT+Plugin > project. > > If not, it'll be a bit more tricky. You'll need the source of those > > plugins, and then you may be able to add that as source directories. > > I don't think it is that easy, unfortunately. I wrote some plugins > that reside in the workspace, but these in turn rely on others that do > not. For instance, I am using EMF to create and manage the value- > objects. These in turn rely on EMF-classes (e.g. EList, etc.) that > reside in the EMF-plugins. >
> I could do what you suggested - but that would be messy. Ideally, I > would like to take advantage of Eclipse to resolve all dependencies, > but I fear that this will be quite difficult. In fact, I did some > work with PDE-building, and it was not pretty. But I am afraid that > this is exactly what's required: A PDE environment for compiling > GWT. :-( And even if I manage that, I would loose the ability to > debug - unless I build a PDE environment for running in hosted mode in > addition to that! > > Anyway, thank you for your response. Any other ideas...? > > Gotcha, thanks for the explanation. I worry that even if we can resolve all the dependencies, you'll probably run into one of your dependencies relying on some classes that GWT does not provide (for example, some of java.io). I can't think of an easy way to avoid this except make your GWT code not rely on Eclipse-provided plugins (only the server-side stuff depending on Eclipse-provided plugins.) jason > Best, > > - Michael > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
