GWT Developer Plugin for Firefox 6

[Jason Yin]

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]

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]

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]

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]

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]

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]

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]

I bet it shouldn't be long: http://gwt-code-reviews.appspot.com/1523805/

[JB]

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]

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]

I second that!

[Thomas Broyer]

Is anything more than http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/README.txt and http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/xpcom/README.txt needed?

[Chris Conroy]

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:

Is anything more than http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/README.txt and http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/xpcom/README.txt needed?

--

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

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/iavfWWhp1xoJ.

[comzine]

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]

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]

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]

I tried it with FF6 on linux 32 bits (mandriva 2010.2), it works fine
there. Many thanks
Lukas

[Thomas Broyer]

Same here on Ubuntu 11.04 64bits.

[Fabricio Pizzichillo]

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.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/BE-SUO_3FjAJ.

[Michael Vogt]

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]

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]

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]

Thank you up till now it still works for windows 32...

[Renee Lau]

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]

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]

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]

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]

Works great for me on Mac OSX

[mo]

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]

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]

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]

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]

FYI:

I have pushed the xpi out: https://dl.google.com/dl/gwt/plugins/firefox/1.0.10582/gwt-dev-plugin.xpi

Once I finish testing it with all the browser once more I'll make that the default for the missing plugin page.

-Alan

--

[HakunaMatata]

Worked on Lion without a hitch!!

[David Dawson]

How's this looking? 

The missing plugin page still seems to read only up to FF5.

We're waiting on this being fully released until we let our developers upgrade to FF6.

Thanks.

David.

[ialpert]

looks like it's been updated

[Alan Leung]

The missing plugin page is also updated.

-Alan

[Jim Douglas]

...and then repeat for Firefox 7 (scheduled for release next Tuesday).

https://wiki.mozilla.org/Releases

[Robert W]

Tday I updated addon in ff6 :)

[Daniel Dunér]

The new FF6 plugin seems to run much faster. In comparison, the
Cromium plugin feels so slow it might as well be standing still. Is
this a correct and generally true observation?

[snayrb99]

Supposedly mozilla's jetpack SDK (https://wiki.mozilla.org/Labs/
Jetpack/Roadmap) will make it faster to develop and migrate add on's.
At this point however it is unclear to me whether the jetpack API
supports all API function calls required by the GWT developer plugin.
So I guess my questions are

1. Can the GWT developer plugin be migrated to jetpack?
2. If it can be migrated, is there a plan to migrate it?

[Tapas Adhikary]

Firefox is talking about the version 10 by Nov 8,2011 (https://wiki.mozilla.org/Releases#Firefox_10)

Whats the plan for the GWT dev plug-in development?

Do you guys have any news on how this plug-in is going to cope up with this crazy release cycles of Firefox?

[leathrum]

Um...  OK... As much as I hate to be the one to throw gasoline on the fire here...  FF 7?  GWT plug-in is disabled again when the update happens.

[Come to think of it, what exactly is the deal with all of these FF updates?  I seem to recall using FF3.6 just about a year ago.]

[Alek]

The same

I've updated accidentally FF to 7 version... don't work again

Have to use meditative Chrome plugin... :(

[Sujay]

Is the plugin available for FireFox 8 yet?

[Ivan Dimitrijevic]

Check this out https://groups.google.com/forum/?hl=en#!searchin/google-web-toolkit/firefox$208/google-web-toolkit/wElYN-Thi2M/221xKU-wmeEJ
--
S postovanjem,
Ivan Dimitrijevic, dipl.ing. ISiT, MSc
di...@dnjcompany.com
http://dimi.dnjcompany.com

On Tue, Nov 15, 2011 at 16:16, Sujay <sujay...@gmail.com> wrote:

Is the plugin available for FireFox 8 yet?