Oh - one question I had is if there's a way to set the browser path? On Fri, Mar 13, 2009 at 7:22 AM, Vitali Lovich <[email protected]> wrote:
> I'm getting the plugins from the gwt-oophm branch. The current install.rdf > says 3.0.*. I manually set it to 3.1.*. > > Installs fine now in 3.1. > > I just built the thing from trunk, applied the previous patch for > HostedMode, and now have my gwt 1.6 project running successfully on 64-bit > Ubuntu 8.10. I might try, just for the hell of it to reboot & see if it'll > work in Windows. > > One comment is that even after the patch, I still need to include the > platform specific dev (gwt-dev-linux) or there are unresolved class > references (i.e. HostedModeBase). I think the ant build script needs to be > updated to pull in the appropriate files from core/. > > Otherwise, thanks & keep up the amazing work. > > > On Mon, Mar 9, 2009 at 8:27 AM, Vitali Lovich <[email protected]> wrote: > >> *S*orry meant to put this in my previous e-mail. >> GWT OOPHM Plugin File name: npOOPHM.dll GWT OOPHM Plugin MIME Type >> Description Suffixes Enabled application/x-gwt-hosted-mode Plugin to >> allow debugging of GWT applications in hosted mode. >> Yes >> >> >> On Mon, Mar 9, 2009 at 8:26 AM, Vitali Lovich <[email protected]> wrote: >> >>> The OOPHM is registered in Firefox 3.0. Firefox 3.1 doesn't have it >>> registered (which used the XPCOM plugin instead of the Firefox one). >>> >>> >>> On Mon, Mar 9, 2009 at 1:03 AM, Vitali Lovich <[email protected]> wrote: >>> >>>> OK - I'll check as soon as I get the chance to work on my GWT project. >>>> >>>> >>>> On Sun, Mar 8, 2009 at 4:21 PM, John Tamplin <[email protected]> wrote: >>>> >>>>> On Sun, Mar 8, 2009 at 1:41 PM, Vitali Lovich <[email protected]>wrote: >>>>>> >>>>>> >>>>>> It said that the (firefox) plugin is incompatible with this version of >>>>>> firefox. It's probably just the version number - you need to bump it up >>>>>> to >>>>>> 3.1. Even if the ABI remains the same, AFAIK, plugins still have to have >>>>>> their versions bumped if they specify a maximum. The XPCOM plugin >>>>>> installs >>>>>> on both. Registering the dll does nothing for IE (I made sure to launch >>>>>> the >>>>>> 32-bit version). >>>>>> >>>>> >>>>> I believe the version was set to 3.*, so that should be compatible, >>>>> though I need to check the version actually checked into the branch. >>>>> >>>>> >>>>>> I didn't look in the about:plugins - just the add-ons menu. Would >>>>>> there be a difference? The machine with my project is in Linux for the >>>>>> time >>>>>> being (until some-time Monday), so if there is a difference, I can only >>>>>> check after then. >>>>>> >>>>> >>>>> The add-ons simply shows the XPI is installed. The install registers a >>>>> plugin for a specific MIME type used to access it from the hosted.html, >>>>> and >>>>> that should show up in about:plugins. if not, then it was unable to >>>>> actually load the plugin, which in the past has tended to be library >>>>> version >>>>> issues. >>>>> >>>>> -- >>>>> John A. Tamplin >>>>> Software Engineer (GWT), Google >>>>> >>>>> >>>>> >>>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
