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
On jan. 26, 21:19, Chris Conroy con...@google.com wrote:
We are pleased to
http://code.google.com/p/google-web-toolkit/issues/detail?id=6084
On Mon, Mar 7, 2011 at 9:45 AM, csillag csillag.kris...@gmail.com wrote:
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
Er, isn't r9525 a fix for the Chrome-dev issue with V8's Crankshaft?
You probably meant to link to
r9526http://code.google.com/p/google-web-toolkit/source/detail?r=9526?
;-)
(also s/download the crx out of svn/download the xpi out of svn/)
--
You received this message because you are
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.
On Thu, Jan 13, 2011 at 5:04 AM, Thomas Broyer t.bro...@gmail.com wrote:
Er, isn't r9525 a fix for the Chrome-dev issue with V8's Crankshaft?
You probably
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
You just need to update your plugin-sdks directory. i added the 2.0 stuff
earlier this week
On Thu, Jan 13, 2011 at 11:10 AM, csillag csillag.kris...@gmail.com wrote:
Tried to build it from a fresh update, and after a while, the build
process has failed with this:
g++ -m64 -o
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
--
You received this message because you are subscribed to the Google
sigh, you're right. svn is acting up. looking into it...
On Thu, Jan 13, 2011 at 12:07 PM, csillag csillag.kris...@gmail.com wrote:
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
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
I just committed
r9525http://code.google.com/p/google-web-toolkit/source/detail?r=9525 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
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.
On Nov 9 2010, 4:34 am, csillag csillag.kris...@gmail.com wrote:
On okt. 26, 00:54,
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
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
Any news on this Topic? A possible release-time would be enough ^^
just a sign of life.
On 11 Nov., 16:07, skrat dusan.malia...@gmail.com wrote:
There is a big demand for this plugin. And unsatisfied :(
On Nov 9, 11:34 am, csillag csillag.kris...@gmail.com wrote:
On okt. 26, 00:54,
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.
On Dec 5, 10:09
There is a big demand for this plugin. And unsatisfied :(
On Nov 9, 11:34 am, csillag csillag.kris...@gmail.com wrote:
On okt. 26, 00:54, slowpoison slowpoi...@slowpoison.net wrote:
On Sep 14, 8:21 am, John Tamplin j...@google.com wrote:
I am working on it right now. I have it working on
On okt. 26, 00:54, slowpoison slowpoi...@slowpoison.net wrote:
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?
Hi,
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?
--
You received this message because you are subscribed to the Google
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
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
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:
On Wed, Aug 11, 2010 at 10:46 AM, Chris Conroy con...@google.com
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, Chris
Its now 09/14/2010. Please could you update us on the status of this
work? The plugin still doesn't seem
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
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
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
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
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.
On Sep 8, 1:07 am, csillag csillag.kris...@gmail.com wrote:
Hi John,
On aug. 11, 18:06, John Tamplin j...@google.com wrote:
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
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
Hi John,
On aug. 11, 18:06, John Tamplin j...@google.com wrote:
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
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
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
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
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
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
On 08/11/2010 09:06 AM, John Tamplin wrote:
On Wed, Aug 11, 2010 at
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
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?
--
You received this message
On Tue, Jun 15, 2010 at 9:09 AM, Alan Chaney a...@mechnicality.com wrote:
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
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
On 06/14/2010
Firefox 3.7 is the nightly (Minefield) build; is it possible to
switch back to the current released version (3.6.3)?
On Jun 14, 1:18 pm, Alan Chaney a...@mechnicality.com wrote:
When I try to install the dev plugin on my Ubuntu 10.04 x64 system I get:
No suitable plugins were found
Seems to
40 matches
Mail list logo
