Re: Out of curiosity: Why is gwt-maven-plugin not marked as @threadsafe?

[Thomas Broyer]

It's actually been done, shipped in 2.6.
https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/52b4394af1db8873043c6435ba63b9405655d337

On Friday, June 13, 2014 4:59:41 PM UTC+2, André Zimmermann wrote:
>
> Hey there, I found a reply from Thomas about this topic here 
> https://groups.google.com/d/msg/codehaus-mojo-gwt-maven-plugin-users/3L-B-1L6w84/t228UPuy_LIJ
> I think they are threadsafe and so does Thomas. They need to verify it and 
> patch it. 
>
> Em quarta-feira, 6 de fevereiro de 2013 10h59min59s UTC-2, Oliver Krylow 
> escreveu:
>>
>> Encountered the following warning upon running the maven command `mvn -T 
>> 16 ` on one of my better build machines :).
>>
>>
>> [WARNING] 
>> *
>> [WARNING] * Your build is requesting parallel execution, but project 
>>  *
>> [WARNING] * contains the following plugin(s) that are not marked as   
>> *
>> [WARNING] * @threadSafe to support parallel building. 
>> *
>> [WARNING] * While this /may/ work fine, please look for plugin updates   
>>  *
>> [WARNING] * and/or request plugins be made thread-safe.   
>> *
>> [WARNING] * If reporting an issue, report it against the plugin in   
>>  *
>> [WARNING] * question, not against maven-core 
>>  *
>> [WARNING] 
>> *
>> [WARNING] The following plugins are not marked @threadSafe in 
>> gwt-cryptojs:
>> [WARNING] org.codehaus.mojo:gwt-maven-plugin:2.5.0
>> [WARNING] 
>> *
>>
>>
>> I am pretty sure the gwt compiler itself supports parallel compilation of 
>> permutations, so is there something in the plugin that is not threadsafe? 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Out of curiosity: Why is gwt-maven-plugin not marked as @threadsafe?

[André Zimmermann]

Hey there, I found a reply from Thomas about this topic 
here 
https://groups.google.com/d/msg/codehaus-mojo-gwt-maven-plugin-users/3L-B-1L6w84/t228UPuy_LIJ
I think they are threadsafe and so does Thomas. They need to verify it and 
patch it. 

Em quarta-feira, 6 de fevereiro de 2013 10h59min59s UTC-2, Oliver Krylow 
escreveu:
>
> Encountered the following warning upon running the maven command `mvn -T 
> 16 ` on one of my better build machines :).
>
>
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project  *
> [WARNING] * contains the following plugin(s) that are not marked as   *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe.   *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core  *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in gwt-cryptojs:
> [WARNING] org.codehaus.mojo:gwt-maven-plugin:2.5.0
> [WARNING] *
>
>
> I am pretty sure the gwt compiler itself supports parallel compilation of 
> permutations, so is there something in the plugin that is not threadsafe? 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[Joseph Lust]

If you're irked, you can let the Chrome Team know on their NPAPI thread 
.
 
It seems there have been a lot of people impacted, not just GWT users.

I also threw the above steps up online 
 
so hopefully others can work around this for now if they've got code that 
must be deved/shipped pronto.

If you're seriously perturbed, you can always contribute to a solution, 
which I believe is the SDBG Eclipse plugin .

Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Share code between GWT projects

[Thomas Broyer]

OK, so I can't help you (don't know Eclipse enough; never even used that 
feature). I strongly believe that an IDE is not a build tool/system, and 
you definitely need one, whichever it is (make, Ant, Maven, Gradle, a shell 
script, whatever).

Hope someone with Eclipse skills will help you.

On Thursday, June 12, 2014 10:13:18 AM UTC+2, Julien wrote:
>
> I'm only "exporting" with Eclipse, I've seen lots of topics saying that 
> Maven would help me but I want to try doing it with Eclipse and GWT Plugin 
> only as I don't really have time to learn how to use Maven for now
>
> Le mercredi 11 juin 2014 19:33:11 UTC+2, Thomas Broyer a écrit :
>>
>>
>>
>> On Wednesday, June 11, 2014 10:34:16 AM UTC+2, Julien wrote:
>>>
>>> Hi there,
>>> I'm trying to share some code between my GWT projects so I was thinking 
>>> about doing something like that :
>>>
>>>
>>> 
>>>
>>> I succeeded to make it work in eclipse and in developer mode by adding 
>>> needed projects to build path,
>>> but when I compile with GWT, it only export classes that are inside the 
>>> current project and there is no trace of needed classes from other 
>>> projects...
>>> So this can't work on the production server :/
>>>
>>
>> "compile with GWT" and "[classes on] production server" are antonymous.
>> "compile with GWT" is about taking source code and transpiling it to 
>> JavaScript. What you deploy on your server is the result of the GWT 
>> compilation for the client side *and* of a standard Java compilation for 
>> the server side.
>>  
>>
>>> Could someone explain how sharing code like this should be done please ? 
>>> I've been looking everywhere and I can't find the answer
>>>
>>
>> What tool are you using to build/package your WAR? Ant? Maven? Or are you 
>> "exporting" using Eclipse?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Dev mode throws MissingResourceException on SerializationStreamFactory.createStreamReader()

[Célio Cidral]

>
> RPC serialization is not symetric (what the client writes can be read by 
> the server, but not the client; what the server writes can be read by the 
> client, but not the server), so this won't work.
> Here, "you" try to interpret as JS (because RPC uses eval()) what 
> definitely is NOT JS, so you're having a syntax error (looking at the stack 
> trace, it's an "invalid label", meaning that it chokes on a ":" char in the 
> payload).


When you mentioned that serialization is asymmetric I checked the stack 
trace again and realized what I did wrong.  I said that I'm doing 
client->server serialization and vice versa, but what I did in fact in the 
server side was taking the string representing the object that was 
serialized in the client side and replying it "as is" to the client (doh!). 
 That was my (broken) proof of concept test.  I fixed the code in the 
server side by serializing the deserialized object with 
ServerSerializationStreamWriter, and now my proof of concept code works.

The part of the stack trace that helped me realize the problem was this:

at 
com.google.gwt.dev.js.rhino.TokenStream.reportSyntaxError(TokenStream.java:1592)


The MissingResourceException, though, kind of obscured the real problem.


Em sexta-feira, 13 de junho de 2014 09h25min45s UTC-3, Célio Cidral 
escreveu:
>
> That looks like a bug in DevMode's CompilingClassLoader.
>
>
> I wonder if someone ever worked around that problem before.
>
> RPC serialization is not symetric (what the client writes can be read by 
>> the server, but not the client; what the server writes can be read by the 
>> client, but not the server), so this won't work.
>> Here, "you" try to interpret as JS (because RPC uses eval()) what 
>> definitely is NOT JS, so you're having a syntax error (looking at the stack 
>> trace, it's an "invalid label", meaning that it chokes on a ":" char in the 
>> payload).
>
>
> I oversimplified that sample code.  What I'm doing exactly is 
> client->server (de)serialization and vice versa.
>
>
> Em quarta-feira, 11 de junho de 2014 20h48min09s UTC-3, Thomas Broyer 
> escreveu:
>>
>>
>>
>> On Wednesday, June 11, 2014 11:01:02 PM UTC+2, Célio Cidral wrote:
>>>
>>> This is what happens 
>>> when SerializationStreamFactory.createStreamReader() is called in dev mode:
>>>
>>> java.util.MissingResourceException: Can't find bundle for base name 
>>> com.google.gwt.dev.js.rhino.Messages, locale en_US
>>>
>>>
>>> A quick google search shows that a few other people had this issue 
>>> before, but none of them got an answer.  Does anyone have an idea of how to 
>>> work around this?
>>>
>>
>> That looks like a bug in DevMode's CompilingClassLoader. BUT:
>>  
>>
>>> I'm using GWT 2.6.1 from the central Maven repository.  Here's some code 
>>> to help reproduce the error:
>>>
>>>   SerializationStreamFactory ssf = 
>>> GWT.create(SignalProcessingService.class);
>>>   SerializationStreamWriter writer = ssf.createStreamWriter();
>>>   writer.writeObject(new Foo("bar"));
>>>   String serializedObject = writer.toString();
>>>
>>>   SerializationStreamReader reader = ssf.createStreamReader(
>>> serializedObject); //exception is thrown here
>>>
>>
>> RPC serialization is not symetric (what the client writes can be read by 
>> the server, but not the client; what the server writes can be read by the 
>> client, but not the server), so this won't work.
>> Here, "you" try to interpret as JS (because RPC uses eval()) what 
>> definitely is NOT JS, so you're having a syntax error (looking at the stack 
>> trace, it's an "invalid label", meaning that it chokes on a ":" char in the 
>> payload).
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Petition for a standalone Chome installer allowing DevMode

[Thomas Broyer]

On Friday, June 13, 2014 3:55:58 PM UTC+2, Thomas Broyer wrote:
>
> I think you're preaching to the chore,
>

Oops! "choir", obviously!
(heh, what not being a native english speaker can make you say/right ;-) )

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Petition for a standalone Chome installer allowing DevMode

[Thomas Broyer]

I think you're preaching to the chore, and I believe developers inside 
Google who are using GWT (Groups, AdWords, Docs, Wallet, etc.) feel your 
pain too as they suffer the Chrome team's choice as well.
Go talk to the Google Chrome guys instead (and get attention from other 
people using NPAPI plugins, not only only GWT DevMode). I'm afraid your 
message here is near to useless.

On Thursday, June 12, 2014 8:24:44 PM UTC+2, Warren Baltz wrote:
>
> Many people were surprised that their DevMode no longer worked recently. I 
> am one of them.  I am aware of Super Dev Mode. It's not always the answer.
>
> After some digging I found that I can disable Chrome's auto update, but I 
> still need an older version to install. Google has made it very difficult 
> to get an older version. I understand their interest in security, stability 
> and new features. But it feels like the rug was pulled out from under 
> developers using DevMode.
>
> If anyone else would like a standalone installer for an older Chrome that 
> still allows DevMode, please leave a brief comment. I'd like this thread to 
> get some attention quickly and hopefully provide some relief.  I have a 
> major project derailed because of this change, and I imagine there are 
> others like me. Time is critical here.  What do you say, Google?  Help a 
> developer out?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Petition for a standalone Chome installer allowing DevMode

[fenyoapa]

It is very needful, and not only on chrome but on latest FF.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[Jens]

Alternatively you can download any Chrome version for Windows from 
portableapps.com. I am not sure if older versions are directly accessible 
through their website but you can find them on http://sourceforge.net/:

http://sourceforge.net/projects/portableapps/files/Google%20Chrome%20Portable/

and

http://sourceforge.net/projects/portableapps/files/Google%20Chrome%20Portable/Additional%20Versions/


These versions do not have auto update and can safely be installed on a usb 
drive or similar.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Ignoring requestFactory responses on page reload

[Alberto Mancini]

Hi,
may be not a solution in your context but a choice can be also using
http://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/Window.html#addWindowClosingHandler%28com.google.gwt.user.client.Window.ClosingHandler%29
to inform the user that should wait until the response is ready.
I think it is at least less dangerous than ignoring eventual errors.

Alberto.








On Thu, Jun 12, 2014 at 9:22 AM, Samin Pour  wrote:

>  Hi Everyone
>
> My question might be very basic but couldn't find the answer anywhere.
>
> I'm working with requestFactory and send some requests to the server at
> almost the same time. One of these request takes couple of seconds, if the
> user refresh the page before the  response is ready,  obviously the
> onFailure() method of the "Receiver" class will be called to catch the
> Error (the message is just "Server Error 0") and therefore throw an
> Exception into user's face.
>
> Now this my question, can I ask the receiver not to wait for the response
> anymore? Or is there a way to check for all the awaiting receivers and tell
> them to ignore all incoming responses? I know I can ignore the
> "ServerFailure" on the OnFailure() method or just log it, but then I can't
> distinguish between a page refresh or real server malfunction.
>
> Any ideas? Would be happy if somebody can help  :)
>
> Cheers
> Samin
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Dev mode throws MissingResourceException on SerializationStreamFactory.createStreamReader()

[Célio Cidral]

>
> That looks like a bug in DevMode's CompilingClassLoader.


I wonder if someone ever worked around that problem before.

RPC serialization is not symetric (what the client writes can be read by 
> the server, but not the client; what the server writes can be read by the 
> client, but not the server), so this won't work.
> Here, "you" try to interpret as JS (because RPC uses eval()) what 
> definitely is NOT JS, so you're having a syntax error (looking at the stack 
> trace, it's an "invalid label", meaning that it chokes on a ":" char in the 
> payload).


I oversimplified that sample code.  What I'm doing exactly is 
client->server (de)serialization and vice versa.


Em quarta-feira, 11 de junho de 2014 20h48min09s UTC-3, Thomas Broyer 
escreveu:
>
>
>
> On Wednesday, June 11, 2014 11:01:02 PM UTC+2, Célio Cidral wrote:
>>
>> This is what happens when SerializationStreamFactory.createStreamReader() 
>> is called in dev mode:
>>
>> java.util.MissingResourceException: Can't find bundle for base name 
>> com.google.gwt.dev.js.rhino.Messages, locale en_US
>>
>>
>> A quick google search shows that a few other people had this issue 
>> before, but none of them got an answer.  Does anyone have an idea of how to 
>> work around this?
>>
>
> That looks like a bug in DevMode's CompilingClassLoader. BUT:
>  
>
>> I'm using GWT 2.6.1 from the central Maven repository.  Here's some code 
>> to help reproduce the error:
>>
>>   SerializationStreamFactory ssf = 
>> GWT.create(SignalProcessingService.class);
>>   SerializationStreamWriter writer = ssf.createStreamWriter();
>>   writer.writeObject(new Foo("bar"));
>>   String serializedObject = writer.toString();
>>
>>   SerializationStreamReader reader = ssf.createStreamReader(
>> serializedObject); //exception is thrown here
>>
>
> RPC serialization is not symetric (what the client writes can be read by 
> the server, but not the client; what the server writes can be read by the 
> client, but not the server), so this won't work.
> Here, "you" try to interpret as JS (because RPC uses eval()) what 
> definitely is NOT JS, so you're having a syntax error (looking at the stack 
> trace, it's an "invalid label", meaning that it chokes on a ":" char in the 
> payload).
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT 2.5.1 DevMode - Unexpected module reload with Firefox

[Arnaud Brochard]

Hi folks,

I just updated my company's application to GWT 2.5.1 and noticed an 
unexpected behavior with Firefox, not present in 2.4.0. On each URL #token 
change (either manually in the navigator address bar, or via the 
Window.Location.assign method), I noticed that the GWT module is fully 
reloaded (in Firebug, the .cache.js file is instantiated again). 
This is not the case with Chrome, or Firefox with GWT 2.4.0.

As the application is quite large and slow to instantiate in devmode, I 
would like to fix this behavior (either in my code if I did something bad, 
or in GWT is this was added in 2.5.X). I tried to debug the bootstrap 
javascript, set a bunch of breakpoints anywhere (any code that can clear 
the document contents, or history change, such as location.reload, 
window.onunload, the history events, etc.), but I can't find anything

So I got no clue right now. Do you know of any changes between 2.4.0 and 
2.5.1 which could trigger this behavior ? 


-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Ignoring requestFactory responses on page reload

[Samin Pour]

 Hi Everyone

My question might be very basic but couldn't find the answer anywhere. 

I'm working with requestFactory and send some requests to the server at 
almost the same time. One of these request takes couple of seconds, if the 
user refresh the page before the  response is ready,  obviously the 
onFailure() method of the "Receiver" class will be called to catch the 
Error (the message is just "Server Error 0") and therefore throw an 
Exception into user's face.

Now this my question, can I ask the receiver not to wait for the response 
anymore? Or is there a way to check for all the awaiting receivers and tell 
them to ignore all incoming responses? I know I can ignore the 
"ServerFailure" on the OnFailure() method or just log it, but then I can't 
distinguish between a page refresh or real server malfunction.

Any ideas? Would be happy if somebody can help  :)

Cheers
Samin


-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[Peter Cliff]

Sounds like this:

http://chrome.blogspot.co.uk/2014/05/protecting-chrome-users-from-malicious.html

Apparently it is possible to install extensions in "Developer Mode" - see:

https://developer.chrome.com/extensions/getstarted#unpacked

But with the imminent demise of NPAPI I'm thinking now would be the time to 
switch to SuperDevMode?

Bit of background here:

http://www.theregister.co.uk/2014/05/27/chrome_extension_lockdown/

Pete

On Thursday, 12 June 2014 12:59:02 UTC+1, AJ wrote:
>
> I started up Chrome today and received notification that the GWT Plugin 
> has been disabled
>
> For your protection, you can only use Chrome extensions that you get from 
> the Chrome Web Store
>
> At the moment I find no way to enable it, not even with developer mode 
> enabled
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[Warren Baltz]

The same thing happened to me. 

I am in the middle of a project nearing a deadline and this is NOT ok.  I 
like a lot of the features offered by GAE/GWT.  But if Google thinks it's 
alright to break my development environment without asking, then they are 
not a safe technology provider.

I desperately hope someone from Google is reading this and taking action. I 
have the feeling they are about to lose a lot of developer support. I'm on 
the fence now and exploring other options. Too bad. These are such good 
tools.



On Thursday, June 12, 2014 6:59:02 AM UTC-5, AJ wrote:
>
> I started up Chrome today and received notification that the GWT Plugin 
> has been disabled
>
> For your protection, you can only use Chrome extensions that you get from 
> the Chrome Web Store
>
> At the moment I find no way to enable it, not even with developer mode 
> enabled
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[Distal Twitch]

This just happened to me too... at a very bad time.  I have a critical 
deadline fast-approaching and my development setup just stopped working 
thanks to this update.

I really like GWT and GAE, but my confidence in Google has been seriously 
shaken. I've spent an entire day just trying to get my development computer 
working again (not working yet). That's time not spent on my project.



On Thursday, June 12, 2014 6:59:02 AM UTC-5, AJ wrote:
>
> I started up Chrome today and received notification that the GWT Plugin 
> has been disabled
>
> For your protection, you can only use Chrome extensions that you get from 
> the Chrome Web Store
>
> At the moment I find no way to enable it, not even with developer mode 
> enabled
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Petition for a standalone Chome installer allowing DevMode

[Warren Baltz]

Many people were surprised that their DevMode no longer worked recently. I 
am one of them.  I am aware of Super Dev Mode. It's not always the answer.

After some digging I found that I can disable Chrome's auto update, but I 
still need an older version to install. Google has made it very difficult 
to get an older version. I understand their interest in security, stability 
and new features. But it feels like the rug was pulled out from under 
developers using DevMode.

If anyone else would like a standalone installer for an older Chrome that 
still allows DevMode, please leave a brief comment. I'd like this thread to 
get some attention quickly and hopefully provide some relief.  I have a 
major project derailed because of this change, and I imagine there are 
others like me. Time is critical here.  What do you say, Google?  Help a 
developer out?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: you can only use Chrome extensions that you get from the Chrome Web Store

[john wolfe]

On Thursday, June 12, 2014 6:59:02 AM UTC-5, AJ wrote:
>
> I started up Chrome today and received notification that the GWT Plugin 
> has been disabled
>
> For your protection, you can only use Chrome extensions that you get from 
> the Chrome Web Store
>
> At the moment I find no way to enable it, not even with developer mode 
> enabled
>

you can get around this by downloading the "Dev Channel for Windows" build 
of chrome here http://www.chromium.org/getting-involved/dev-channel

you may have to restart chrome or drag n drop .crx files again but i was 
able to just click enable on most disabled extensions.  shouldnt change 
your chrome experience. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT designer crash

[Jérôme Serré]

Le vendredi 13 juin 2014 10:56:08 UTC+2, Jérôme Serré a écrit :
>
> Hello,
>  
> i'm a newbee with GWT. please be kind ^^
> When i want to use GWT desgner on Test_GWT.java (first app) there is a 
> crash !
> it is possible become a bad installation. I join a report file.
>  
> Thank u for your help.
>  
> Jérôme
>
 
 
 
Hello.
 
Finally i installed 2.6.1 gwt designer and it works !

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Supporting deprecated/unknown browsers

[Jens]

Take a look at: https://gwt-review.googlesource.com/#/c/7780/

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.