GWT Developer Plugin for Firefox 6

2790 views
Skip to first unread message

Jason Yin

unread,
Aug 16, 2011, 3:51:51 PM8/16/11
to Google Web Toolkit
Hi

just upgraded to firefox 6 today.. and realized GWT Developer plugin
isn't compatible with it.
any ETA on when this will be available?

Thanks

Chris Conroy

unread,
Aug 16, 2011, 5:03:11 PM8/16/11
to google-we...@googlegroups.com
Jason,

Unfortunately, for the time being we're unable to keep pace with Mozilla's new release schedule since the plugin update process is quite manual. We'll be sure to announce to the list when FF6 support is ready. In the meantime, you'll just have to fall back to <=FF5 for DevMode.


--
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.


Jim Douglas

unread,
Aug 16, 2011, 10:24:10 PM8/16/11
to Google Web Toolkit
Bit of a firestorm over there...a proposal to hide the version number
from the user:

http://arstechnica.com/web/news/2011/08/firefox-6-ships-but-we-shouldnt-really-pay-attention.ars
https://bugzilla.mozilla.org/show_bug.cgi?id=678775

On Aug 16, 2:03 pm, Chris Conroy <con...@google.com> wrote:
> Jason,
>
> Unfortunately, for the time being we're unable to keep pace with Mozilla's
> new release schedule since the plugin update process is quite manual. We'll
> be sure to announce to the list when FF6 support is ready. In the meantime,
> you'll just have to fall back to <=FF5 for DevMode.
>

Jesper Rønn-Jensen

unread,
Aug 17, 2011, 5:51:45 AM8/17/11
to Google Web Toolkit
Jason Yin wrote:
>
> just upgraded to firefox 6 today.. and realized GWT Developer plugin isn't compatible with it.
>

Just to add to the thread: I changed version numbers inside the .xpi
file. But FF6 still complaints that it is incompatible. So I guess we
must have to wait for a release


Please keep us informed in this thread of:
* official updates to the gwt-dev-plugin.xpi
* any unofficial releases that work for FF6


Thanks!
/Jesper Rønn-Jensen
www.justaddwater.dk

Jason Yin

unread,
Aug 17, 2011, 12:05:52 PM8/17/11
to Google Web Toolkit
Hi Chris

Thank you for your reply.

Jason

On Aug 16, 5:03 pm, Chris Conroy <con...@google.com> wrote:
> Jason,
>
> Unfortunately, for the time being we're unable to keep pace with Mozilla's
> new release schedule since the plugin update process is quite manual. We'll
> be sure to announce to the list when FF6 support is ready. In the meantime,
> you'll just have to fall back to <=FF5 for DevMode.
>

Patrick Seebauer

unread,
Aug 18, 2011, 9:23:41 AM8/18/11
to Google Web Toolkit
In the changelogs of the svn repo there is “gecko linux” mentioned for
r10537, does that mean that firefox 6 is now supported for linux? And
if yes for both 32 and 64 bit?


On Aug 16, 11:03 pm, Chris Conroy <con...@google.com> wrote:
> Jason,
>
> Unfortunately, for the time being we're unable to keep pace with Mozilla's
> new release schedule since the plugin update process is quite manual. We'll
> be sure to announce to the list when FF6 support is ready. In the meantime,
> you'll just have to fall back to <=FF5 for DevMode.
>

tdk

unread,
Aug 24, 2011, 7:12:26 AM8/24/11
to Google Web Toolkit
are there any informations as to availabilty of the plugin for FF 6
under Windows (7, x64)?

For me it is crucial to have the plugin, otherwise I have to downgrade
my FF again...

Thomas Broyer

unread,
Aug 24, 2011, 7:49:46 AM8/24/11
to google-we...@googlegroups.com

JB

unread,
Aug 25, 2011, 9:07:42 AM8/25/11
to Google Web Toolkit
Just confirming I applied the patch linked by Thomas above and re-
built gwt-dev-plugin.xpi with:
BROWSER=ff06; make

And the plugin works (tested on Linux-x86).

This should make it very soon now!

Tony Rah

unread,
Aug 25, 2011, 10:48:35 AM8/25/11
to Google Web Toolkit
GWT Team,
Perhaps it would help if you posted a white paper on how to build the
pluggin and then the community could keep up with the new release
schedule until the official ones are available.

Olivier Hoareau

unread,
Aug 26, 2011, 3:06:30 AM8/26/11
to Google Web Toolkit
I second that!

Thomas Broyer

unread,
Aug 26, 2011, 4:26:59 AM8/26/11
to google-we...@googlegroups.com

Chris Conroy

unread,
Aug 26, 2011, 10:50:53 AM8/26/11
to google-we...@googlegroups.com
That's more or less it to build against existing source and plugin sdks.

Upgrading to a new version is certainly more involved due to the repackaging of the original SDK, updating the makefile, manifest, and rdf install template in the easy case. In the hard case it involves dealing with breaking API changes from the new version :P

Though, if you just care about building a single platform locally, that takes away most of the repackaging headaches. It sounds like there may be sufficient demand for instructions for this use case (e.g. when we are lagging a release), so I'll mark that as a TODO for me to write up a wiki entry on this subject.

On Fri, Aug 26, 2011 at 4:26 AM, Thomas Broyer <t.br...@gmail.com> wrote:

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

comzine

unread,
Aug 29, 2011, 4:22:32 PM8/29/11
to Google Web Toolkit
I switched from Chrome to FF under Linux cause of annoying windows
telling me the GWT web page is unresponsive during debugging. This bug
is already known, but should be more important and easier to fix than
solving problems with FF Changelog due Chrome is also built by Google!
Please help me! There's no comfortable way to debug my GWT projects.

On Aug 26, 4:50 pm, Chris Conroy <con...@google.com> wrote:
> That's more or less it to build against existing source and plugin sdks.
>
> Upgrading to a new version is certainly more involved due to the repackaging
> of the original SDK, updating the makefile, manifest, and rdf install
> template in the easy case. In the hard case it involves dealing with
> breaking API changes from the new version :P
>
> Though, if you just care about building a single platform locally, that
> takes away most of the repackaging headaches. It sounds like there may be
> sufficient demand for instructions for this use case (e.g. when we are
> lagging a release), so I'll mark that as a TODO for me to write up a wiki
> entry on this subject.
>
>
>
>
>
>
>
> On Fri, Aug 26, 2011 at 4:26 AM, Thomas Broyer <t.bro...@gmail.com> wrote:
> > Is anything more than
> >http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugi...
> >  and
> >http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugi...needed?

Chris Conroy

unread,
Aug 29, 2011, 4:57:03 PM8/29/11
to google-we...@googlegroups.com
Just run a Firefox binary that's supported by the plugin.

For chrome, you can always launch a separate instance with --disable-hang-monitor to get rid of that popup behavior. I recommend doing this with a separate --user-data-dir as well for a devmode only profile since you want that popup when you are just on a random site that gets into an infinite js loop.

Alan Leung

unread,
Aug 30, 2011, 2:42:01 PM8/30/11
to google-we...@googlegroups.com
FWIW, I just checked in xpi file.

If you feel adventurous, you can fetch it from the SVN and install it. Please let me know if you have any issues.

I plan to put it on the auto download page later this week.

I apologize for the delay.

-Alan 

Lukas Laag

unread,
Aug 30, 2011, 5:13:28 PM8/30/11
to Google Web Toolkit
I tried it with FF6 on linux 32 bits (mandriva 2010.2), it works fine
there. Many thanks
Lukas

Thomas Broyer

unread,
Aug 31, 2011, 4:01:56 AM8/31/11
to google-we...@googlegroups.com
Same here on Ubuntu 11.04 64bits.

Fabricio Pizzichillo

unread,
Aug 31, 2011, 6:02:26 AM8/31/11
to google-we...@googlegroups.com
Hi all
Can you pass the path to download the 
plugin?

Thanks!

2011/8/31 Thomas Broyer <t.br...@gmail.com>
Same here on Ubuntu 11.04 64bits.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

Michael Vogt

unread,
Aug 31, 2011, 6:34:42 AM8/31/11
to google-we...@googlegroups.com
Hello.

> Can you pass the path to download the plugin?
>

I got it from here:
http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/prebuilt/


Greetings,
Michael

Fabricio Pizzichillo

unread,
Aug 31, 2011, 6:38:15 AM8/31/11
to google-we...@googlegroups.com
Thanks Michael

2011/8/31 Michael Vogt <vme...@googlemail.com>
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

amos

unread,
Sep 2, 2011, 2:22:06 PM9/2/11
to Google Web Toolkit
Awesome. Thanks.

On Aug 31, 6:34 am, Michael Vogt <vmei...@googlemail.com> wrote:
> Hello.
>
> > Can you pass the path to download the plugin?
>
> I got it from here:http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/preb...
>
> Greetings,
> Michael

Muhammad Haikal Satria

unread,
Sep 3, 2011, 12:11:48 AM9/3/11
to Google Web Toolkit
Thank you up till now it still works for windows 32...

Renee Lau

unread,
Sep 5, 2011, 3:43:48 AM9/5/11
to Google Web Toolkit
Thanks a lot! it works for me!



On 8月31日, 下午6時34分, Michael Vogt <vmei...@googlemail.com> wrote:
> Hello.
>
> > Can you pass the path to download the plugin?
>
> I got it from here:http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/preb...
>
> Greetings,
> Michael

Jim Douglas

unread,
Sep 9, 2011, 10:33:07 AM9/9/11
to Google Web Toolkit
Any progress on the Firefox 6 plugin? This page still reports that
the highest supported version is 5.0:

http://gwt.google.com/samples/MissingPlugin/MissingPlugin.html

On Aug 16, 2:03 pm, Chris Conroy <con...@google.com> wrote:
> Jason,
>
> Unfortunately, for the time being we're unable to keep pace with Mozilla's
> new release schedule since the plugin update process is quite manual. We'll
> be sure to announce to the list when FF6 support is ready. In the meantime,
> you'll just have to fall back to <=FF5 for DevMode.
>

Thomas Broyer

unread,
Sep 9, 2011, 10:39:11 AM9/9/11
to google-we...@googlegroups.com
In case you missed it: https://groups.google.com/d/msg/google-web-toolkit/SNNKn7VK9-Y/hLqvyt3X56cJ

I'm using it since then without any problem so far. Don't why it hasn't been "promoted" yet.

Jim Douglas

unread,
Sep 9, 2011, 11:15:10 AM9/9/11
to Google Web Toolkit
Thanks, Thomas. Yes, I saw that, and I suppose I should have
clarified that I'm asking about the status of the actual production
version, as opposed to "go fetch it from such and such repository."

On Sep 9, 7:39 am, Thomas Broyer <t.bro...@gmail.com> wrote:
> In case you missed
> it:https://groups.google.com/d/msg/google-web-toolkit/SNNKn7VK9-Y/hLqvyt...

Dan

unread,
Sep 9, 2011, 12:35:36 PM9/9/11
to google-we...@googlegroups.com
Works great for me on Mac OSX

mo

unread,
Sep 11, 2011, 2:54:55 AM9/11/11
to Google Web Toolkit
Works for me too, thx.
FF 6.0 on Gentoo / 64bit

On 31 Aug., 12:34, Michael Vogt <vmei...@googlemail.com> wrote:
> Hello.
>
> > Can you pass the path to download the plugin?
>
> I got it from here:http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/preb...
>
> Greetings,
> Michael

snayrb99

unread,
Sep 12, 2011, 3:09:15 PM9/12/11
to Google Web Toolkit

Would it make sense to modify the plugin build to work with any future
of firefox (something like <em:maxVersion>*</em:maxVersion>?) rather
than tie to a specific version of firefox? I understand the reason for
being strict about versions in the past but with FF on a fast release
cycle it seems unlikely that plugin contract will change as newer
versions of firefox are released. At a minimum, older versions of the
contract should be supported for a few releases giving FF plugin
developers a chance to migrate to newer versions of the contract on a
different release cycle.

Just a thought.

Chris Conroy

unread,
Sep 12, 2011, 7:05:59 PM9/12/11
to google-we...@googlegroups.com
On Mon, Sep 12, 2011 at 3:09 PM, snayrb99 <brya...@comcast.net> wrote:

Would it make sense to modify the plugin build to work with any future
of firefox (something like <em:maxVersion>*</em:maxVersion>?) rather
than tie to a specific version of firefox? I understand the reason for
being strict about versions in the past but with FF on a fast release
cycle it seems unlikely that plugin contract will change as newer
versions of firefox are released.
This will not work. Under the new rapid release regime we must link against the gecko libraries with the proper module::kVersion set or the plugin will fail to load at runtime.

 
At a minimum, older versions of the
contract should be supported for a few releases giving FF plugin
developers a chance to migrate to newer versions of the contract on a
different release cycle.

Indeed, hopefully we get some deprecation period before the API actually changes, but this is up to Mozilla. Recently they were going to remove nsIDomWindowInternal (an API that we and many other plugins use) and have since backtracked and announced just a deprecation for FF8. Other APIs that we rely on may not be so lucky.

 
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

snayrb99

unread,
Sep 13, 2011, 1:17:21 PM9/13/11
to Google Web Toolkit

Thank you for a very illuminating answer. It seems rather sad that FF
plugins MUST link against a library that is browser version dependent.
Most products I have dealt with provide some kind of adapter layer to
allow older versions of plugins to be used with newer versions of
software. I suppose they must have there reasons though.

Alan Leung

unread,
Sep 13, 2011, 3:38:40 PM9/13/11