Dev plugin for firefox 3.7

[Alan Chaney]

When I try to install the dev plugin on my Ubuntu 10.04 x64 system I get:

"No suitable plugins were found"

Seems to me that's because the 'latest' version in the plugin descriptor
is set to 3.6.

Does anyone know if there is a dev plugin build for 3.7? If not, can I
build/modify one myself?

TIA

Alan

[Jim Douglas]

Firefox 3.7 is the nightly ("Minefield") build; is it possible to
switch back to the current released version (3.6.3)?

[Alan Chaney]

I'm developing a large WebGL application which is currently only
supported by the nightly builds, so the answer to your question is,
sadly, no :-) .

I really, really want to be able to debug GWT in Firefox, so if
necessary I'd be prepared to help with testing/building.

Alan

[Chris Conroy]

Preliminary support for Firefox 3.7 just went in to trunk thanks to
the hard work by John Tamplin. You'll need to build the extension
yourself. It's currently working on Linux and Mac, and Windows support
for VS will be coming later.

The plugins live at trunk/plugins/ and you should invoke the makefile
from that directory. You'll want to set your environment with
BROWSER=ff40 (e.g. export BROWSER=ff40 with bash) to tell the makefile
that you want to build for Minefield. Also note you will need to
checkout the plugin-sdks parallel to your trunk/ checkout of gwt:

in same folder as GWT trunk, do
svn co https://google-web-toolkit.googlecode.com/svn/plugin-sdks

If you don't want to mess with getting libidl on your box, you can
comment out the lines199-203 in xpcom/Makefile which call out to
xpidl. The generated file is up in svn so you don't need to run this
portion if libidl gives you trouble.

After a successful build, you'll find the extension packaged at
xpcom/prebuilt/gwt-dev-plugin.xpi

--
Chris Conroy
Software Engineer
Google, Atlanta

[01fetischist]

Doesn't work with Firefox 4.0 beta1 and Firefox 4.0 beta2pre
(nightlybuild).
Tested with gecko1.9.3 plugin-sdk from google and with self build
gecko2.0b2pre sdk.
I still get the "Development Mode requires the Google Web Toolkit
Developer Plugin" page.

Any hints?

[andreas]

I'm having the same problem ... just built development plugin from
trunk but FF 4.0 still displays its "Plugin required..." stuff.

Working on Ubuntu with actually only newest versions of browsers
(Chrome dev channel and FF 3.6 & 4.0). At least for FF 3.6 a working
development plugin exists. Hope this will change soon...

Does anyone have a working setup for this combination?:
- Ubuntu
- GWT Development Mode
- Browser supporting Websockets

What about other OS?

I had it running with FF 4.0 and development plugin build from trunk
like two weeks ago but apparently it does not work anymore.

Regards,

Andreas

On 7 Jul., 23:15, 01fetischist <01fetisch...@googlemail.com> wrote:
> Doesn't work withFirefox4.0 beta1 andFirefox4.0 beta2pre

[al...@mechnicality.com]

Hi Chris,

I've found that FF 4 beta on Linux x86_64 (Ubuntu 10.04) doesn't seem to
work with the BROWSER=ff40 version of the plugin. I've updated to 8516
and tried to repeat the steps in your last email but I can't seem to get
the make to work. It worked fine with 3.7 but I urgently need to move to
4 beta. There's also a thread on the gwt-dev list on this, where John
gave me help to get the plugin going on 3.7.

I'm getting the following errors:

gwt-source/trunk/plugins/xpcom$ make
(cd ../common && make)
make[1]: Entering directory `/home/ajc/gwt-source/trunk/plugins/common'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/ajc/gwt-source/trunk/plugins/common'
Makefile:148: Using firefox libraries at
../../../plugin-sdks/gecko-sdks/gecko-1.9.3/Linux_x86_64-gcc3/lib
[ ! -x
../../../plugin-sdks/gecko-sdks/gecko-1.9.3/Linux_x86_64-gcc3/bin/xpidl
-o \( -e prebuilt/ff40/include/IOOPHM.h -a ! -w
prebuilt/ff40/include/IOOPHM.h \) ] ||
../../../plugin-sdks/gecko-sdks/gecko-1.9.3/Linux_x86_64-gcc3/bin/xpidl
-I../../../plugin-sdks/gecko-sdks/gecko-1.9.3/idl -m header -e
prebuilt/ff40/include/IOOPHM.h IOOPHM.idl
g++ -g -O2 -fPIC
-I../../../plugin-sdks/gecko-sdks/gecko-1.9.3/Linux_x86_64-gcc3/include
-I../../../plugin-sdks/gecko-sdks/gecko-1.9.3/include
-Iprebuilt/ff40/include/ -rdynamic -m64 -DBROWSER=ff40 -DGECKO_19
-fshort-wchar -c -o build/Linux_x86_64-gcc3-ff40/ExternalWrapper.o -I.
-I../common ExternalWrapper.cpp
In file included from ExternalWrapper.h:21,
from ExternalWrapper.cpp:17:
mozincludes.h:11:26: error: xpcom-config.h: No such file or directory
mozincludes.h:12:28: error: mozilla-config.h: No such file or directory
In file included from ExternalWrapper.h:23,
from ExternalWrapper.cpp:17:
prebuilt/ff40/include/IOOPHM.h:10:25: error: nsISupports.h: No such file
or directory
In file included from ExternalWrapper.h:25,
from ExternalWrapper.cpp:17:
Preferences.h:23:22: error: nsCOMPtr.h: No such file or directory
Preferences.h:25:25: error: nsIObserver.h: No such file or directory
Preferences.h:26:28: error: nsIPrefBranch2.h: No such file or directory
In file included from FFSessionHandler.h:23,
from ExternalWrapper.h:26,
from ExternalWrapper.cpp:17:
SessionData.h:23:19: error: jsapi.h: No such file or directory
In file included from ExternalWrapper.cpp:17:
ExternalWrapper.h:31:41: error: nsISecurityCheckedComponent.h: No such
file or directory
ExternalWrapper.h:32:25: error: nsStringAPI.h: No such file or directory
ExternalWrapper.h:33:30: error: nsIWindowWatcher.h: No such file or
directory
ExternalWrapper.h:34:26: error: nsIDOMWindow.h: No such file or directory
ExternalWrapper.cpp:19:36: error: nsIHttpProtocolHandler.h: No such file
or directory
ExternalWrapper.cpp:21:22: error: nsNetCID.h: No such file or directory
ExternalWrapper.cpp:23:22: error: nsMemory.h: No such file or directory
ExternalWrapper.cpp:24:35: error: nsServiceManagerUtils.h: No such file
or directory
ExternalWrapper.cpp:25:30: error: nsIPromptService.h: No such file or
directory
ExternalWrapper.cpp:27:34: error: nsIDOMWindowInternal.h: No such file
or directory
ExternalWrapper.cpp:28:28: error: nsIDOMLocation.h: No such file or
directory
ExternalWrapper.cpp:29:28: error: nsXPCOMStrings.h: No such file or
directory
ExternalWrapper.cpp:30:32: error: nsICategoryManager.h: No such file or
directory
ExternalWrapper.cpp:31:31: error: nsIJSContextStack.h: No such file or
directory
ExternalWrapper.cpp:32:30: error: nsIScriptContext.h: No such file or
directory
ExternalWrapper.cpp:33:35: error: nsIScriptGlobalObject.h: No such file
or directory
ExternalWrapper.cpp:34:27: error: nsPIDOMWindow.h: No such file or directory
ExternalWrapper.cpp:37:42: error: nsIClassInfoImpl.h: No such file or
directory
In file included from ExternalWrapper.h:23,
from ExternalWrapper.cpp:17:
prebuilt/ff40/include/IOOPHM.h:27: error: expected initializer before
�:� token
make: *** [build/Linux_x86_64-gcc3-ff40/ExternalWrapper.o] Error 1

What am I doing wrong?

Thanks in advance

Alan

[Chris Conroy]

The short answer is that after preliminary support went in, the supporting libraries changed upstream. Also, when the prelim support went in Windows dev libraries weren't even available. I think John has a change in the works to get this updated but is blocked on something.

I suggest for the time being that you just use production mode for anything you specifically have to test on 3.7. If that won't work, consider using a slightly older version of 3.7 (from Jun 16 or so) to build the plugin.

prebuilt/ff40/include/IOOPHM.h:27: error: expected initializer before ‘:’ token

[John Tamplin]

On Wed, Aug 11, 2010 at 10:46 AM, Chris Conroy <con...@google.com> wrote:

The short answer is that after preliminary support went in, the supporting libraries changed upstream. Also, when the prelim support went in Windows dev libraries weren't even available. I think John has a change in the works to get this updated but is blocked on something.

Just being on vacation much of the last two weeks and having other things in front of it.  I intend to update all the platforms for 4.0b2 this week.

--
John A. Tamplin
Software Engineer (GWT), Google

[al...@mechnicality.com]

Thanks Chris and John

I'll hold off switching platforms for a few days, I have other things to do which don't require the webgl stuff.

I greatly appreciate all the work done on this and your responsiveness.

Regards


Alan

[csillag]

Hi,

I am using 64-bit Debian lenny/sid hybrid.
GWT plugin works all right with distribution's iceweasel 3.6.

Now I have downloaded FF 4.0 b4 (from mozilla), and I can not get the
plugin working.

From current SVN, I can build the plugin, and installation works fine,
it shows up in addons (as 1.0.8862M.20100828001436).

However, when trying to open a GWT app in dev mode, I get the missing
plugin message.

How can I debug why is the installed plugin not found, when needed?

Thank you for your help!

[csillag]

Hi John,

Could you please give us some update on the current status?

I have just downloaded the 64-bit version of FF4.0 B5 from mozilla,
installed it (on my Debian system),
updated my plugin svn dirs,
built the plugin (w. BROWSER=ff40), installed it
(shows up registered as 1.0.8725M.20100908004741),
and tried to run a GWT app (running in Eclipse, GWT 2.0.4)...
...but I only got a warning about not supporting anythin above 3.5.

Could you please help me finding out what am I doing wrong?

Thank you for your help!

Kristof Csillag

[skrat]

Hi all,

is there any progress on this issue? FF4 is almost done and we're
stuck with developing on FF3.6 which is slow as hell on MacOS, and
there's no Chromium plugin.

[csillag]

> I have just downloaded the 64-bit version of FF4.0 B5 from mozilla,
> installed it (on my Debian system),
> updated my plugin svn dirs,
> built the plugin (w. BROWSER=ff40), installed it
> (shows up registered as 1.0.8725M.20100908004741),
> and tried to run a GWT app (running in Eclipse, GWT 2.0.4)...
> ...but I only got a warning about not supporting anythin above 3.5.

To exclude any possibility of compiling with the wrong headers
/linking with the wrong libraries, I have just

- removed all my libmoz / libnss / libxul / iceweasel stuff from my
system
- downloaded the iceweasel 4.0 beta 5 source packages
- build the packages on my own system (with the locally installed
headers/libraries)
- installed all the required libraries / dev packages / applications

... so now I have a working iceweasel 4.0 beta 5 on my system, with
all the dependencies
as system libraries, with no alternate versions at all.

Then I have updated my plugin SVN dir, build the plugin (with
BROWSER=ff40),
installed the plugin, and it shows up between addons, but
when trying to open an app, it still says that
"Sorry, the GWT Developer Plugin only supports Firefox 3.0 and 3.5 at
present"

I am out of ideas, so I give up - unless someone can help, of couse.

Thank you:

Kristof

[csillag]

On szept. 8, 23:03, csillag <csillag.kris...@gmail.com> wrote:
> To exclude any possibility of compiling with the wrong headers

> /linking with the wrong libraries, I have just [...]

> ... so now I have a working iceweasel 4.0 beta 5 on my system, with
> all the dependencies
> as system libraries, with no alternate versions at all.

Now I realize that this did not make that much sense, since
the GWT dev plugin is compiled with it's own set of headers/libraries,
shipped in plugin-sdks.

I have tried to replace those with the ones on my system
(is. from xulrunner-2.0), and adjusting the compiler flags
to match that of the system libraries,
but unfortunatelly there seem to be some incompatible
API changes (for example, NS_DECL_CLASSINFO has disappeared),
so I can not get it compiled with the FF4 (=gecko 2.0) libraries.

So, it seems that this really needs the attention of the authors of
the plugin.

I hope this gets fixed soon, because my GWT apps totally fail with
FF4,
and I can not even start to debug them until I have a dev plugin
ready.

Thank you for your help:

Kristof

[Thomas Broyer]

On Sep 9, 2:38 am, csillag <csillag.kris...@gmail.com> wrote:
>
> I hope this gets fixed soon, because my GWT apps totally fail with
> FF4,
> and I can not even start to debug them until I have a dev plugin
> ready.

In the mean time, can't you compile with "-style PRETTY" and debug
using Firebug? (or the Web Console? haven't tried it yet)

[al...@mechnicality.com]

John, Chris

Its now 09/14/2010. Please could you update us on the status of this work? The plugin still doesn't seem to work with FF 4.06 beta.


Regards

Alan Chaney

On 08/11/2010 09:06 AM, John Tamplin wrote:

[skrat]

Are these first signs of GWT being forgotten? That there is less
resources being allocated for GWT team??

On Sep 14, 4:44 pm, "a...@mechnicality.com" <a...@mechnicality.com>
wrote:

[John Tamplin]

On Tue, Sep 14, 2010 at 10:44 AM, al...@mechnicality.com
<al...@mechnicality.com> wrote:
> Its now 09/14/2010. Please could you update us on the status of this work?
> The plugin still doesn't seem to work with FF 4.06 beta.

I am working on it right now. I have it working on FF40, but I am
still trying to get it where one XPI will work on both FF3 and FF4.

[al...@mechnicality.com]

Hi John

I understand why you need to achieve the FF3/FF4 cross-compatibility,
but is there any possible way that you could maybe branch a version for
just FF40? I'm sure others on the list would agree with me that this
would really, really help. I'm still using a very unstable and outdated
version of 3.7 and as my main interest is WebGL, which has now moved on
a lot, I really need an FF40 version.

Thanks in advance

Alan

[csillag]

On szept. 14, 17:38, "a...@mechnicality.com" <a...@mechnicality.com>
wrote:

> Hi John
>
> I understand why you need to achieve the FF3/FF4 cross-compatibility,
> but is there any possible way that you could maybe branch a version for
> just FF40? I'm sure others on the list would agree with me that this
> would really, really help.

I can only second that.

Kristof

[csillag]

On szept. 14, 17:21, John Tamplin <j...@google.com> wrote:
> On Tue, Sep 14, 2010 at 10:44 AM, a...@mechnicality.com

>
> <a...@mechnicality.com> wrote:
> > Its now 09/14/2010. Please could you update us on the status of this work?
> > The plugin still doesn't seem to work with FF 4.06 beta.
>
> I am working on it right now.  I have it working on FF40, but I am
> still trying to get it where one XPI will work on both FF3 and FF4.
>
> --
> John A. Tamplin
> Software Engineer (GWT), Google

Dear John,

Could you please tell us that is the current status of this?

[csillag]

Dear John,

On szept. 14, 17:21, John Tamplin <j...@google.com> wrote:

> On Tue, Sep 14, 2010 at 10:44 AM, a...@mechnicality.com

>
> <a...@mechnicality.com> wrote:
> > Its now 09/14/2010. Please could you update us on the status of this work?
> > The plugin still doesn't seem to work with FF 4.06 beta.
>
> I am working on it right now.  I have it working on FF40, but I am
> still trying to get it where one XPI will work on both FF3 and FF4.

could you please tell us what is the current status of this?
As mentioned previously, even an FF4-only version would be useful.

Best wishes:

Kristof

[slowpoison]

On Sep 14, 8:21 am, John Tamplin <j...@google.com> wrote:
> I am working on it right now.  I have it working on FF40, but I am
> still trying to get it where one XPI will work on both FF3 and FF4.

Any update about this, John?

[csillag]

Hi,

I am still waiting for this.
Could you please at least give us some info about what's happening?

Thank you:

Kristof

[skrat]

There is a big demand for this plugin. And unsatisfied :(

[Sebastian]

Any news on this Topic? A possible release-time would be enough ^^
just a sign of life.

[Chris Conroy]

The big hold up has been the fact that Firefox kept making breaking API
changes from beta release to beta release. We're chasing a moving target
here. I don't have a date to give you, but know that we haven't forgotten
about it. We'll be sure to announce when it's ready.

[Carfield Yim]

Sorry to hear that, will there any chance to have some kind of alert,
like mailing list to publish the update?

On Dec 7, 12:57 am, Chris Conroy <con...@google.com> wrote:
> The big hold up has been the fact that Firefox kept making breaking API  
> changes from beta release to beta release. We're chasing a moving target  
> here. I don't have a date to give you, but know that we haven't forgotten  
> about it. We'll be sure to announce when it's ready.
>

[Sebastian]

yes, I've experienced the api switches from beta to beta in FF4 by
myself. But due to the fact, the final is on the way, things should
get sorted in the next couple of months :)

Keep up the good work and thanks for giving some informations to us!

Seb

On Dec 6, 5:57 pm, Chris Conroy <con...@google.com> wrote:
> The big hold up has been the fact that Firefox kept making breaking API  
> changes from beta release to beta release. We're chasing a moving target  
> here. I don't have a date to give you, but know that we haven't forgotten  
> about it. We'll be sure to announce when it's ready.
>

[mort...@gmail.com]

I tried to build this as well.. although it did seem to build after
following most of the instructions here and on other sites, it didn't
work with Firefox 4.0b8 (osx).

Would be nice to know some updates.

[Chris Conroy]

I just committed r9525 which updates the xpcom plugin to support Gecko 2.0 (Firefox 4) on Linux. You need to use at least Firefox 4 beta 9 for it to work. The xulrunner SDK for mac is unavailable, and we'll follow on later with an update to the Windows build.

Feel free to download the crx out of svn if you want to give it a spin on Linux. It should be backwards compatible with 3.0-3.6.

[Thomas Broyer]

Er, isn't r9525 a fix for the Chrome-dev issue with V8's Crankshaft?

You probably meant to link to r9526? ;-)

(also s/download the crx out of svn/download the xpi out of svn/)

[Chris Conroy]

Yep, yep, and yep. I'm going to blame my inability to communicate sensibly on cabin fever from being ice-bound here in Atlanta all week.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[csillag]

Tried to build it from a fresh update, and after a while, the build
process has failed with this:

g++ -m64 -o build/Linux_x86_64-gcc3-ff40/libgwt_dev_ff40.so build/
Linux_x86_64-gcc3-ff40/ExternalWrapper.o build/Linux_x86_64-gcc3-ff40/
ModuleOOPHM.o build/Linux_x86_64-gcc3-ff40/FFSessionHandler.o build/
Linux_x86_64-gcc3-ff40/JavaObject.o build/Linux_x86_64-gcc3-ff40/
JSRunner.o build/Linux_x86_64-gcc3-ff40/Preferences.o build/
Linux_x86_64-gcc3-ff40/XpcomDebug.o ../common/libcommon64.a -shared -
m64 -L/home/csillag/local/lib/firefox-4.0b10pre -L../../plugin-sdks/
gecko-sdks/gecko-2.0.0/Linux_x86_64-gcc3/lib -Wl,-rpath-link,../../
plugin-sdks/gecko-sdks/gecko-2.0.0/Linux_x86_64-gcc3/lib -lxpcomglue_s
-lxpcom -lnspr4 -lmozalloc
/usr/bin/ld: cannot find -lxpcomglue_s
collect2: ld returned 1 exit status
make: *** [build/Linux_x86_64-gcc3-ff40/libgwt_dev_ff40.so] Error 1

......

BTW, checking out the contents of plugin-sdks, there really is no
xpcomglue stuff for gecko-2.0.0.

What am I missing here?

Thank you, again:

Kristof Csillag

On jan. 13, 00:02, Chris Conroy <con...@google.com> wrote:
> I just committed r9525<http://code.google.com/p/google-web-toolkit/source/detail?r=9525> which

[Chris Conroy]

You just need to update your plugin-sdks directory. i added the 2.0 stuff earlier this week

[csillag]

On jan. 13, 17:34, Chris Conroy <con...@google.com> wrote:
> You just need to update your plugin-sdks directory. i added the 2.0 stuff
> earlier this week
>
>

Of course I did update it before compiling.
It's at 9528.

Kristof

[Chris Conroy]

sigh, you're right. svn is acting up. looking into it...

--

[Chris Conroy]

I had been using the sdk provided dynamic libraries for building, and looks like codesite wasn't happy with the 200+ meg files.

http://code.google.com/p/google-web-toolkit/source/detail?r=9535 adds the stripped versions of the missing libraries.

[csillag]

On jan. 13, 21:33, Chris Conroy <con...@google.com> wrote:
> I had been using the sdk provided dynamic libraries for building, and looks
> like codesite wasn't happy with the 200+ meg files.
>

> http://code.google.com/p/google-web-toolkit/source/detail?r=9535adds the

> stripped versions of the missing libraries.

OK, now it builds, installs and runs OK!
(Testing with Minefield 4.0 b10pre )

Thank you for your help on this!

Now I can finally debug my stuff.

Kristof

[Chris Conroy]

We are pleased to announce that the GWT Developer Plugin now officially supports Firefox 4 on all platforms that Firefox ships on: Win x86, Linux x86/x86_64, Mac x86/x86_64. Please be sure that you are using Firefox 4 beta 9 or newer.

If you already have the plugin installed, you can use the normal add-on update process. If you are a Firefox 3.x user who has been waiting to try Firefox 4, the add-on will automatically update when you launch Firefox 4 with your current profile.

As always, you can always download the latest GWT Developer plugin for your browser from http://gwt.google.com/missing-plugin.

[csillag]

In case you have not yet noticed, the Mozilla guys did it again: they
managed to break this again with beta12.
Now FF4 crashes when I load my GWT app in dev mode.

Could you please take a look?

Thank you:

Kristof

[Chris Conroy]

http://code.google.com/p/google-web-toolkit/issues/detail?id=6084