Re: GWT dev plugin stopped working on Chrome 39

2014-11-28 Thread Igor Zubchenok
Nice plugin! Do you know if there is something similar for IntelliJ IDEA?

On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>
> SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
> https://github.com/sdbg/sdbg it's almost OK for me. 
> Also with new GPE it's very easy to switch between SuperDevMode and 
> DevMode debugging, so I use both of them now.
>
> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:
>>
>> Search Portable "Chrome", make sure it's the 32 bit version.
>>
>> Since its another year away, I wonder what the possibility of getting one 
>> more build of the browser DevMode plugin?  Maybe plug some memory leaks and 
>> recompile it so it will work with 64 bit Chrome, where possible?
>>
>> On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:
>>>
>>> Thank you Jens, this make a sense!
>>>
>>> SuperDevMode has ugly debugging. Unforutnately...
>>> Do you know where Chrome 38 OSX can be downloaded?
>>>
>>> Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>
 So you have to use a different/older browser or use SuperDevMode.

>>>

-- 
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 dev plugin stopped working on Chrome 39

2014-11-28 Thread Frank Hossfeld
Assuming you are using Intellij 14 ultimate: check the JavaScript debugging 
option inside the GWT running configuration. 

Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:
>
> Nice plugin! Do you know if there is something similar for IntelliJ IDEA?
>
> On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>>
>> SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
>> https://github.com/sdbg/sdbg it's almost OK for me. 
>> Also with new GPE it's very easy to switch between SuperDevMode and 
>> DevMode debugging, so I use both of them now.
>>
>> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:
>>>
>>> Search Portable "Chrome", make sure it's the 32 bit version.
>>>
>>> Since its another year away, I wonder what the possibility of getting 
>>> one more build of the browser DevMode plugin?  Maybe plug some memory leaks 
>>> and recompile it so it will work with 64 bit Chrome, where possible?
>>>
>>> On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:

 Thank you Jens, this make a sense!

 SuperDevMode has ugly debugging. Unforutnately...
 Do you know where Chrome 38 OSX can be downloaded?

 Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>>
> So you have to use a different/older browser or use SuperDevMode.
>


-- 
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 dev plugin stopped working on Chrome 39

2014-11-28 Thread Igor Zubchenok
This could probably work, but I don't see such option.
Check the screenshot:
https://www.dropbox.com/s/sgeh7ao6r9572tp/Screenshot%202014-11-28%2013.07.38.png?dl=0

On Friday, 28 November 2014 13:02:10 UTC+3, Frank Hossfeld wrote:
>
> Assuming you are using Intellij 14 ultimate: check the JavaScript 
> debugging option inside the GWT running configuration. 
>
> Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:
>>
>> Nice plugin! Do you know if there is something similar for IntelliJ IDEA?
>>
>> On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>>>
>>> SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
>>> https://github.com/sdbg/sdbg it's almost OK for me. 
>>> Also with new GPE it's very easy to switch between SuperDevMode and 
>>> DevMode debugging, so I use both of them now.
>>>
>>> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:

 Search Portable "Chrome", make sure it's the 32 bit version.

 Since its another year away, I wonder what the possibility of getting 
 one more build of the browser DevMode plugin?  Maybe plug some memory 
 leaks 
 and recompile it so it will work with 64 bit Chrome, where possible?

 On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:
>
> Thank you Jens, this make a sense!
>
> SuperDevMode has ugly debugging. Unforutnately...
> Do you know where Chrome 38 OSX can be downloaded?
>
> Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>>>
>> So you have to use a different/older browser or use SuperDevMode.
>>
>

-- 
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: SuggestBox and the underlying TextBox

2014-11-28 Thread Thomas Broyer
I've done some really crappy and brittle code in an app where we delay the 
check for a few milliseconds when triggered by ValueChangeEvent, to let the 
time for the SelectionEvent to possibly be triggered.

But remember that this is a *suggest* box, not a "select box with 
type-ahead"; it gives suggestions (like Google Suggest, or your webmail 
searching your contacts list when typing in the "To:" or "Cc:" fields) but 
is otherwise free-form. Using the SuggestBox for a type-ahead listbox is 
misusing it; IMO you'd better look for another widget (and yes, there's no 
such widget in GWT proper), such as https://arcbees.github.io/gwtchosen/ 
(never used it, can't really comment)

On Friday, November 28, 2014 8:25:20 AM UTC+1, ckuetbach wrote:
>
> Hello,
>
> I have some trouble with the SuggestBox. 
>
> There are at least two Hadler at the SuggestBox:
>
> - ValueChangeHandler
> - SelectionHandler
>
> If I enter a Text into the SuggestBox and unfocus it, I get the 
> ValueChangeEvent, with the current Value (I need to validate the Input at 
> this moment)
>
> If I enter a Text into the SuggestBox and select one of the Selection, I 
> get two Events in this Order:
>
> 1. ValueChangeEvent with the SearchTerm of the TextBox
> 2. SelectionEvent with the selected Value
>
> My Problem is, that my Validation will validate the SearchTerm in the 
> ValueChangeEvent (Which may be wrong). In the following SelectionEvent, I 
> get the correct Value. 
> But in this case, I have already shown a warning Display, that the entered 
> Value is invalid.
>
>
> I think it may be this GWT Issue: 
> https://code.google.com/p/google-web-toolkit/issues/detail?id=1634
>
>
> Are there any ideas, how I can solve my problem?
>
>
>
> Thanks,
> Christian
>
>
>
>

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


Docs updated for 2.7 ?

2014-11-28 Thread David
Hi,

Are the docs for gwtproject updated for the 2.7 release ?
I read through the getting started section and I was expecting some
walkthrough of debugging to explain SuperDevMode but it still is the old
docs that expects us to use the old DevMode.

David

-- 
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: Docs updated for 2.7 ?

2014-11-28 Thread Thomas Broyer
There's still some work needed.
For example, the "logging" page is now incomplete or wrong, and still 
references the LoggingSample that no longer exists. And the getting 
started, tutorials and "compile & debug" sections/pages indeed need an 
update.
Contributions are more than welcome!

However, the superdevmode article has been updated for 
2.7: http://www.gwtproject.org/articles/superdevmode.html

On Friday, November 28, 2014 11:18:55 AM UTC+1, stuckagain wrote:
>
> Hi,
>
> Are the docs for gwtproject updated for the 2.7 release ?
> I read through the getting started section and I was expecting some 
> walkthrough of debugging to explain SuperDevMode but it still is the old 
> docs that expects us to use the old DevMode.
>
> David
>

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


[POLL] How much do you rely on gwt-maven-plugin gwt:compile's staleness check?

2014-11-28 Thread Thomas Broyer
Hi all,

I've started a poll for those of you that use the 
gwt-maven-plugin: 
https://groups.google.com/d/topic/codehaus-mojo-gwt-maven-plugin-users/g0avDvocNlY/discussion

-- 
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 dev plugin stopped working on Chrome 39

2014-11-28 Thread Frank Hossfeld
Have you tried to create a new GWT running configuration?   

Am Freitag, 28. November 2014 11:09:25 UTC+1 schrieb Igor Zubchenok:
>
> This could probably work, but I don't see such option.
> Check the screenshot:
>
> https://www.dropbox.com/s/sgeh7ao6r9572tp/Screenshot%202014-11-28%2013.07.38.png?dl=0
>
> On Friday, 28 November 2014 13:02:10 UTC+3, Frank Hossfeld wrote:
>>
>> Assuming you are using Intellij 14 ultimate: check the JavaScript 
>> debugging option inside the GWT running configuration. 
>>
>> Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:
>>>
>>> Nice plugin! Do you know if there is something similar for IntelliJ IDEA?
>>>
>>> On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:

 SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
 https://github.com/sdbg/sdbg it's almost OK for me. 
 Also with new GPE it's very easy to switch between SuperDevMode and 
 DevMode debugging, so I use both of them now.

 On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:
>
> Search Portable "Chrome", make sure it's the 32 bit version.
>
> Since its another year away, I wonder what the possibility of getting 
> one more build of the browser DevMode plugin?  Maybe plug some memory 
> leaks 
> and recompile it so it will work with 64 bit Chrome, where possible?
>
> On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:
>>
>> Thank you Jens, this make a sense!
>>
>> SuperDevMode has ugly debugging. Unforutnately...
>> Do you know where Chrome 38 OSX can be downloaded?
>>
>> Chrome is now 64 bit on OS X and the plugin is only 32 bit.

>>> So you have to use a different/older browser or use SuperDevMode.
>>>
>>

-- 
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: [POLL] How much do you rely on gwt-maven-plugin gwt:compile's staleness check?

2014-11-28 Thread Timothy Michael Spear
I use an explicit clean, compile, deploy set of processes when building a
release. For local testing, clean, compile, run when I want to test a
deployment. 
So no, I do not use the staleness check, and I would actually prefer
separate output directories.

Tim

From:  Thomas Broyer 
Reply-To:  
Date:  Friday, November 28, 2014 at 6:08 AM
To:  
Subject:  [POLL] How much do you rely on gwt-maven-plugin gwt:compile's
staleness check?

Hi all,

I've started a poll for those of you that use the gwt-maven-plugin:
https://groups.google.com/d/topic/codehaus-mojo-gwt-maven-plugin-users/g0avD
vocNlY/discussion
-- 
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: SuggestBox and the underlying TextBox

2014-11-28 Thread ckuetbach
Thanks for the anwser, I will take a look at the arcbee-project.


I think I found another trick to make the Suggestbox do what I want (There 
is no need for timer or delays): 
https://github.com/msh9/codinginthetrenches.com/blob/master/content/2012/catching-value-change-events-from-the-gwt-suggestbox.txt


-- 
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 SuperDevMode 2.7.0 and SDBG - some member variables are missing.

2014-11-28 Thread David
I'm trying out the enhanced SDM with GWT 2.7.

It only took me a few minutes to set it up, including installing the
sourcemaps debugger in eclipse and find an offline chrome installer (I'm
not connected to the internet on my dev machine). So great work there!

Now I'm trying out debugging in Chrome and SDBG however I found that some
member variables of my Activity class do not show up in SDBG. I noticed
that some of my member variables are under Local->this in chrome, but some
are one level deeper in Local->this->__proto__

These members are just declared in my activity yet they are somehow stored
differently.

Now with SDBG I can only seem to see member variables under Local->this and
not the ones under Local->this->__proto__ ( I shall complain to the people
writing that great plugin).

How come I see this difference ? Is there a way to influence this ?

It will take time to getting used to finding the member variables and how
to inspect them. I hope SDBG gets updated to perform some kind of mapping
to real java member field structures instead.

-- 
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: Docs updated for 2.7 ?

2014-11-28 Thread David
I found the section on superdevmode, I must say it has greatly improved. I
need to work with -noserver and it just works nicely. Maybe the
superdevmode plugin could show the codeserver URL as well, but I found the
URL in the console output.

I also am using SDBG in eclipse and that works much nicer than the
sourcemap support in chrome.

As for contributions ... I'm not native English so I don't think my English
is good enough for writing documentation. I don't have a lot of spare time
either :-(. I am really impressed that you seem to be able to combine a
paying job with a lot of opensource work. I just can not handle both.

On Fri, Nov 28, 2014 at 11:46 AM, Thomas Broyer  wrote:

> There's still some work needed.
> For example, the "logging" page is now incomplete or wrong, and still
> references the LoggingSample that no longer exists. And the getting
> started, tutorials and "compile & debug" sections/pages indeed need an
> update.
> Contributions are more than welcome!
>
> However, the superdevmode article has been updated for 2.7:
> http://www.gwtproject.org/articles/superdevmode.html
>
>
> On Friday, November 28, 2014 11:18:55 AM UTC+1, stuckagain wrote:
>>
>> Hi,
>>
>> Are the docs for gwtproject updated for the 2.7 release ?
>> I read through the getting started section and I was expecting some
>> walkthrough of debugging to explain SuperDevMode but it still is the old
>> docs that expects us to use the old DevMode.
>>
>> David
>>
>  --
> 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: GWT dev plugin stopped working on Chrome 39

2014-11-28 Thread Igor Zubchenok
I tired, no results. There is still no check for JS debugging options.
IDEA 14.

https://www.dropbox.com/s/woz02oiblw14qi4/Screenshot%202014-11-28%2017.03.36.png?dl=0

On Friday, 28 November 2014 14:34:56 UTC+3, Frank Hossfeld wrote:
>
> Have you tried to create a new GWT running configuration?   
>
> Am Freitag, 28. November 2014 11:09:25 UTC+1 schrieb Igor Zubchenok:
>>
>> This could probably work, but I don't see such option.
>> Check the screenshot:
>>
>> https://www.dropbox.com/s/sgeh7ao6r9572tp/Screenshot%202014-11-28%2013.07.38.png?dl=0
>>
>> On Friday, 28 November 2014 13:02:10 UTC+3, Frank Hossfeld wrote:
>>>
>>> Assuming you are using Intellij 14 ultimate: check the JavaScript 
>>> debugging option inside the GWT running configuration. 
>>>
>>> Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:

 Nice plugin! Do you know if there is something similar for IntelliJ 
 IDEA?

 On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>
> SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
> https://github.com/sdbg/sdbg it's almost OK for me. 
> Also with new GPE it's very easy to switch between SuperDevMode and 
> DevMode debugging, so I use both of them now.
>
> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:
>>
>> Search Portable "Chrome", make sure it's the 32 bit version.
>>
>> Since its another year away, I wonder what the possibility of getting 
>> one more build of the browser DevMode plugin?  Maybe plug some memory 
>> leaks 
>> and recompile it so it will work with 64 bit Chrome, where possible?
>>
>> On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:
>>>
>>> Thank you Jens, this make a sense!
>>>
>>> SuperDevMode has ugly debugging. Unforutnately...
>>> Do you know where Chrome 38 OSX can be downloaded?
>>>
>>> Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>
 So you have to use a different/older browser or use SuperDevMode.

>>>

-- 
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 dev plugin stopped working on Chrome 39

2014-11-28 Thread Igor Zubchenok
GWT Support plugin v1.0

https://www.dropbox.com/s/bvxuh5hel8goj59/Screenshot%202014-11-28%2017.05.00.png?dl=0

On Friday, 28 November 2014 17:04:19 UTC+3, Igor Zubchenok wrote:
>
> I tired, no results. There is still no check for JS debugging options.
> IDEA 14.
>
>
> https://www.dropbox.com/s/woz02oiblw14qi4/Screenshot%202014-11-28%2017.03.36.png?dl=0
>
> On Friday, 28 November 2014 14:34:56 UTC+3, Frank Hossfeld wrote:
>>
>> Have you tried to create a new GWT running configuration?   
>>
>> Am Freitag, 28. November 2014 11:09:25 UTC+1 schrieb Igor Zubchenok:
>>>
>>> This could probably work, but I don't see such option.
>>> Check the screenshot:
>>>
>>> https://www.dropbox.com/s/sgeh7ao6r9572tp/Screenshot%202014-11-28%2013.07.38.png?dl=0
>>>
>>> On Friday, 28 November 2014 13:02:10 UTC+3, Frank Hossfeld wrote:

 Assuming you are using Intellij 14 ultimate: check the JavaScript 
 debugging option inside the GWT running configuration. 

 Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:
>
> Nice plugin! Do you know if there is something similar for IntelliJ 
> IDEA?
>
> On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>>
>> SuperDevMode debugging is not so convenient as DevMode, but with SDBG 
>> https://github.com/sdbg/sdbg it's almost OK for me. 
>> Also with new GPE it's very easy to switch between SuperDevMode and 
>> DevMode debugging, so I use both of them now.
>>
>> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:
>>>
>>> Search Portable "Chrome", make sure it's the 32 bit version.
>>>
>>> Since its another year away, I wonder what the possibility of 
>>> getting one more build of the browser DevMode plugin?  Maybe plug some 
>>> memory leaks and recompile it so it will work with 64 bit Chrome, where 
>>> possible?
>>>
>>> On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote:

 Thank you Jens, this make a sense!

 SuperDevMode has ugly debugging. Unforutnately...
 Do you know where Chrome 38 OSX can be downloaded?

 Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>>
> So you have to use a different/older browser or use SuperDevMode.
>


-- 
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 dev plugin stopped working on Chrome 39

2014-11-28 Thread Igor Zubchenok
Thanks everyone! Issue is solved! I just had to enable JavaScript debugger 
plugin! :-) hehe

On Friday, 28 November 2014 17:05:41 UTC+3, Igor Zubchenok wrote:
>
> GWT Support plugin v1.0
>
>
> https://www.dropbox.com/s/bvxuh5hel8goj59/Screenshot%202014-11-28%2017.05.00.png?dl=0
>
> On Friday, 28 November 2014 17:04:19 UTC+3, Igor Zubchenok wrote:
>>
>> I tired, no results. There is still no check for JS debugging options.
>> IDEA 14.
>>
>>
>> https://www.dropbox.com/s/woz02oiblw14qi4/Screenshot%202014-11-28%2017.03.36.png?dl=0
>>
>> On Friday, 28 November 2014 14:34:56 UTC+3, Frank Hossfeld wrote:
>>>
>>> Have you tried to create a new GWT running configuration?   
>>>
>>> Am Freitag, 28. November 2014 11:09:25 UTC+1 schrieb Igor Zubchenok:

 This could probably work, but I don't see such option.
 Check the screenshot:

 https://www.dropbox.com/s/sgeh7ao6r9572tp/Screenshot%202014-11-28%2013.07.38.png?dl=0

 On Friday, 28 November 2014 13:02:10 UTC+3, Frank Hossfeld wrote:
>
> Assuming you are using Intellij 14 ultimate: check the JavaScript 
> debugging option inside the GWT running configuration. 
>
> Am Freitag, 28. November 2014 10:55:23 UTC+1 schrieb Igor Zubchenok:
>>
>> Nice plugin! Do you know if there is something similar for IntelliJ 
>> IDEA?
>>
>> On Wednesday, 26 November 2014 00:12:32 UTC+3, Slava Pankov wrote:
>>>
>>> SuperDevMode debugging is not so convenient as DevMode, but with 
>>> SDBG https://github.com/sdbg/sdbg it's almost OK for me. 
>>> Also with new GPE it's very easy to switch between SuperDevMode and 
>>> DevMode debugging, so I use both of them now.
>>>
>>> On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote:

 Search Portable "Chrome", make sure it's the 32 bit version.

 Since its another year away, I wonder what the possibility of 
 getting one more build of the browser DevMode plugin?  Maybe plug some 
 memory leaks and recompile it so it will work with 64 bit Chrome, 
 where 
 possible?

 On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok 
 wrote:
>
> Thank you Jens, this make a sense!
>
> SuperDevMode has ugly debugging. Unforutnately...
> Do you know where Chrome 38 OSX can be downloaded?
>
> Chrome is now 64 bit on OS X and the plugin is only 32 bit.
>>>
>> So you have to use a different/older browser or use SuperDevMode.
>>
>

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


How to wrap horizontal panel

2014-11-28 Thread Om
 

My requirement is that i need to find segregate hyperlink and text and wrap 
them into panel currently using horizontal panel but couldn't able to wrap.

Please help here is code snippet 


 for (String splitedComment : splitedComments) {

  if(!(splitedComment.matches(urlPathPattern) || 
splitedComment.matches(UNCPathPattern))){

  if(splitedComment.length()>0) {

  HTML txt=new HTML();

  txt.setHTML(splitedComment + " ");

  //lbl = new Label(splitedComment+" ");

   }

  });

 hyperlinkPanel.add(txt);

  }

  } else {

  link0 = new Anchor();

  link0.setText(splitedComment);

  link0.setHref(splitedComment);

  link0.setTarget("_blank");

  HTML txt=new HTML();

  txt.setHTML(" ");

hyperlinkPanel.add(link0);

  hyperlinkPanel.add(txt);

  }

-- 
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 2.5-rc1 feature uirender is not working as expected.

2014-11-28 Thread Aleksey Popryadukhin
Thank you for answer.

Sorry for response delaying I tried to get GWT 2.8-SNAPSHOT.

I have such code:
PlayCell.java

public class PlayCell extends AbstractCell {

  private static final PlayCellBinder cellRenderer = 
GWT.create(PlayCellBinder.class);

  interface PlayCellBinder extends UiRenderer {
void render(SafeHtmlBuilder sb, PlayCellProxy myCellRenderer);
  }

  @Override
  public void render(Context context, PlayCellProxy value, SafeHtmlBuilder sb) {
if (value == null) {
  return;
}
cellRenderer.render(sb, value);
  }

}


PlayCell.ui.xml







Title:


Player:





PlayCellProxy.java

public class PlayCellProxy {

  private PlayDto playDto;

  public PlayCellProxy(PlayDto playDto) {
this.playDto = playDto;
  }

  public String getTitle() {
return playDto.getTitle();
  }

  public String getWhitePlayer() {
return playDto.getWhitePlayer();
  }

  public String getBlackPlayer() {
return playDto.getBlackPlayer();
  }

  public String getDeskHtml() {
return playDto.getDeskHtml();
  }

}


With such code page is rendered. But fields of playCellProxy are empty.

четверг, 27 ноября 2014 г., 10:06:04 UTC+3 пользователь Vasu написал:
>
> you need to provide your code snippets which will enable us to help you.
>
> [image: Pandurang Patil on about.me]
>
> Pandurang Patil
> about.me/pandurangpatil
>   
> website: http://www.agnie.net 
> twitter: @agniesoftware
> Cell : +91-9823241535
>
> On Wed, Nov 26, 2014 at 12:15 AM, Aleksey Popryadukhin  > wrote:
>
>> Hi all.
>>
>> I'm see this old topic but I stuck with this problem. I tried to remove 
>> the type tag but I'm getting an error anyway in compile time. @UiFactory 
>> either not working. Any clue?
>>
>> четверг, 26 июля 2012 г., 15:26:22 UTC+3 пользователь Vasu написал:
>>>
>>> Woow.. really quick thanks Rodrigo. Also would like to thanks Thomas for 
>>> giving right direction.
>>>
>>> On Thursday, 26 July 2012 02:41:03 UTC+5:30, Rodrigo Chandia wrote:

 I think this patch (under review) fixes this issue:

 http://gwt-code-reviews.appspot.com/1794803  

 On Tuesday, July 24, 2012 3:27:29 PM UTC-4, Rodrigo Chandia wrote:
>
> Hmm, this seems like a bug to me. Hopefully I'll have a fix ready for 
> rc2.
>
>
> On Mon, Jul 23, 2012 at 11:11 PM, Vasu wrote:
>
>>
>> Yea  you are absolutely right. It worked when I removed type 
>> attribute from  tag. I was wondering it has to identify type 
>> to 
>> call respective methods on the same and I realized that it tries to 
>> match 
>> the variable name with that of name of the parameter to render method 
>> (which I marked in blue color in below code). 
>>
>> 
>> 
>> --
>> interface MyUiRenderer extends UiRenderer {
>> void render(SafeHtmlBuilder sb, *Person person*);
>> }
>> 
>> --
>>  
>>
>>
>>
>> So Finally working code looks like this.
>>
>>
>> PersonCell.java
>> 
>> 
>> --
>>
>>
>> public class PearsonCell extends AbstractCell {
>>
>>
>> interface MyUiRenderer extends UiRenderer {
>> void render(SafeHtmlBuilder sb, Person person);
>>
>> }
>>
>> private static MyUiRendererrenderer= 
>> GWT.create(MyUiRenderer.class);
>>
>> @Override
>> public void render(com.google.gwt.cell.client.Cell.Context 
>> context, Person value, SafeHtmlBuilder sb) {
>> renderer.render(sb, value);
>> }
>>
>> }
>>
>> 
>> 
>> --
>>
>> PersonCell.ui.xml
>> 
>> 
>> --
>>
>> 
>> 
>>
>> 
>> First Name :
>> 
>> 
>> 
>> 
>> Last Name :
>> 
>> 
>> 
>> 
>> 
>> Email :
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --

Re: add mobile version to existing GWT app?

2014-11-28 Thread Magnus
Hi,

ok, but this leads me to the question, why we don't use REST/JSON right 
from the beginning?
Isn't it a potential option for nearly any web application today to be 
complemented by a mobile version some day?

Are there any tutorials out there for building web apps based on GWT with 
mobile versions for Android/iOS?

Magnus

-- 
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: add mobile version to existing GWT app?

2014-11-28 Thread Jens

>
> ok, but this leads me to the question, why we don't use REST/JSON right 
> from the beginning?
>

At the beginning of a project you usually know what you want to do. So if 
you want native clients for different platforms then you will start with 
some sort of REST/JSON or protobuff/thrift/... backend.

 

> Isn't it a potential option for nearly any web application today to be 
> complemented by a mobile version some day?
>

Sure but "mobile version" does not automatically mean native client for 
each mobile platform. If your web app works in a mobile web browser then 
you not necessarily need a native app. Often a mobile friendly web app is 
good enough.


Are there any tutorials out there for building web apps based on GWT with 
> mobile versions for Android/iOS?
>

At GWT.create in early 2015 there will be a talk about the hybrid apps from 
Google which have a client for web but also native clients for iOS / 
Android. These hybrid apps share about 70% of the code base between these 
platforms.


-- 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: Running new auto compile super dev mode from maven plugin

2014-11-28 Thread SP Gingras
Hi Thomas,

I tested "compile on refresh" (CoR) with your archetypes, and it works fine 
(using mvn gwt:run).

However, CoR does not work in my project (gwt 2.7, using mvn gwt:run).

File changes don't seem to be picked up by SDM:

[INFO] GET /recompile/App
[INFO]Job com.myproject.App_1_4
[INFO]   starting job: com.myproject.App_1_4
[INFO]   binding: user.agent=safari
[INFO]   *skipped compile because no input files have changed*
[INFO]   0.038s total -- Compile completed

I have a particular maven structure where I have a root GWT module that 
aggregates a dozen of other GWT modules.
The parent GWT module is in its own Maven module, and all child GWT modules 
are in separate Maven modules. 
The parent Maven module contains 0 java code. All java code is located in 
the child Maven modules

/
├── app (Maven module, contains 1 gwt module inheriting all child GWT 
modules, no Java code here)
├── module1 (Maven module, pom)
│   ├── client (Maven module, contains 1 GWT module + Java files)
│   ├── server
├── module2 (Maven module, pom)
│   ├── client (Maven module, contains 1 GWT module + Java files)
│   ├── server
├── module3 (Maven module, pom)
│   ├── client (Maven module, contains 1 GWT module + Java files)
│   ├── server

 
I tried changing UiBinder files, View or Presenter files (using GWTP here), 
no changes are ever picked up.

Any hints?


On Wednesday, November 5, 2014 2:16:43 AM UTC-5, Michael Wiles wrote:
>
> Hi all...
>
> So I'm trying out gwt 2.7-rc1
>
> I'm using the same maven config as I had for 2.6
>
> I precompile all my sources so when I start the app it picks up the gwt 
> module. 
>
> When I run the app for the first time it correctly says "compiling" (as it 
> doesn't precompile) and once done the app loads.
>
> But after that when I refresh it doesn't pick up that there are changes 
> and recompiles...
>
> I have to do a full recompile to pick up the changes.
>
> Michael
>

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


CellTable gets cut off at bottom of browser window; vertical scroll unavailable

2014-11-28 Thread Jordan Shweky
Hi,

I created a CellTable to which rows and columns can be added depending on 
the needs of the user.  However, when the table is longer than the height 
of the browser window, no scroll bar appears.  Honestly I would have 
expected the browser to do this automatically, but when I tried wrapping 
everything on the page in scroll bars with CSS, even the scroll bar 
attached to the table was grayed out, which seems to indicate that the 
browser doesn't even acknowledge the existence of the content being cut off 
at the bottom.

I tried wrapping the entire element in a ScrollPanel widget, but between 
requiring a specified size and the fact that if the table isn't so large, 
the scroll bar will still be there, that doesn't seem to be the best 
solution.  

This is an incredibly important aspect of this project, and I'm relatively 
new to GWT.  Any help would be greatly appreciated.

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


Chrome GWT Plugin required but is already installed

2014-11-28 Thread Alex
This just suddenly started happening to me. I'm developing using the Maven 
gwt plugin on OS X against Google Chrome. I've been using it for many 
months with no problem. Now I get prompted to download the plugin again 
with the message:
Development Mode requires the GWT Developer Plugin

But I already have it installed. I've tried removing it and re-installing 
but I still get this message. 

Any help would be greatly appreciated!

Thanks,

Alex

-- 
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: REST Service on Backend which Framework in GWT?

2014-11-28 Thread marian lux
Thank you. Dropwizard looks quite interesting and I think I could give it a 
try. Only the micro service conzept could be problematic. My applicatoin is big 
and I am not sure if I want to split it up in different backend projects

But my question was more in frontend direction using REST in GWT: 
E.g what is the difference between REST support in gwtresty and gwtquery 
project. Which one should I give a try?

THX
-- Marian

-- 
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: REST Service on Backend which Framework in GWT?

2014-11-28 Thread Jens

>
> But my question was more in frontend direction using REST in GWT: 
> E.g what is the difference between REST support in gwtresty and gwtquery 
> project. Which one should I give a try? 


Take a look at both documentations and choose the one you feel comfortable 
with? 

-- 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: Chrome GWT Plugin required but is already installed

2014-11-28 Thread Jens
Latest Chrome on Mac OS is now 64bit but the browser plugin is only 32bit 
so it does not work anymore.

You can:
- downgrade your Chrome to version 38 and turn off auto update
- use Firefox 24 ESR or 26 (GWT plugin does not work in newer versions of 
Firefox)
- instead of DevMode use SuperDevMode which does not require any browser 
plugins.

-- 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: Chrome GWT Plugin required but is already installed

2014-11-28 Thread Alex
Thank you Jens. This would explain it. 

I can't find any way to downgrade Google Chrome on my mac. I don't appear 
to have a Google Software Update app as some webpage suggested I should. 

GWT 2.7.0 won't compile my application (2.6.1 has no problem). The error 
message is so cryptic there's no hope to figure out why. 

I've tried for 3 hrs now to get Super Dev Mode to work but the 
documentation is terrible so I can't figure it out. I'm hoping you can help 
with that since I'm out of options. 

I can't understand the GWT documentation on running SuperDevMode. It says:

If you are not using Dev Mode, first you need to compile the GWT 
application and launch a web server that serves its output files.


I don't know what that means. Are they suggesting that I simply create a 
standard war file and deploy that on a web server like Tomcat? 

The instructions on running the code-server are also lacking details. I've 
no idea how to launch this codeserver or set up my classpaths. I've tried 
using the maven gwt:run-codeserver goal and it does a bunch of compilation 
and looks to launch a server but when I visit the URL I get this error in 
my browser:

HTTP ERROR: 500

Problem accessing /. Reason:


org.eclipse.jetty.http.gzip.CompressedResponseWrapper.newCompressedStream(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;JII)Lorg/eclipse/jetty/http/gzip/AbstractCompressedStream;

and in the console I get:

[ERROR] java.lang.AbstractMethodError: 
org.eclipse.jetty.http.gzip.CompressedResponseWrapper.newCompressedStream(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;JII)Lorg/eclipse/jetty/http/gzip/AbstractCompressedStream;
[ERROR] at 
org.eclipse.jetty.http.gzip.CompressedResponseWrapper.getOutputStream(CompressedResponseWrapper.java:347)
[ERROR] at 
com.google.gwt.dev.codeserver.PageUtil.sendJsonAndHtml(PageUtil.java:89)
[ERROR] at com.google.gwt.dev.codeserver.WebServer.doGet(WebServer.java:174)
[ERROR] at 
com.google.gwt.dev.codeserver.WebServer.handleRequest(WebServer.java:158)
[ERROR] at 
com.google.gwt.dev.codeserver.WebServer.access$000(WebServer.java:65)
[ERROR] at 
com.google.gwt.dev.codeserver.WebServer$1.doGet(WebServer.java:123)
[ERROR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
[ERROR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
[ERROR] at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669)
[ERROR] at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1336)
[ERROR] at 
org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
[ERROR] at 
org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
[ERROR] at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307)
[ERROR] at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:453)
[ERROR] at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)
[ERROR] at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072)
[ERROR] at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382)
[ERROR] at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
[ERROR] at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006)
[ERROR] at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
[ERROR] at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
[ERROR] at org.eclipse.jetty.server.Server.handle(Server.java:365)
[ERROR] at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
[ERROR] at 
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926)
[ERROR] at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988)
[ERROR] at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
[ERROR] at 
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
[ERROR] at 
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
[ERROR] at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
[ERROR] at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
[ERROR] at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
[ERROR] at 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
[ERROR] at java.lang.Thread.run(Thread.java:745)


Any ideas why this isn't working?

Thanks,

Alex

On Friday, November 28, 2014 2:27:04 PM UTC-8, Jens wrote:
>
> Latest Chrome on Mac OS is now 64bit but the browser plugin is only 32bit 
> so it does not work anymore.
>
> You can:
> - downgrade your Chrome to version 38 and turn off auto update
> - use Firefox 24 ESR or 26 (GWT plugin does not