Re: Getting started

2012-07-09 Thread Kanagaraj M
That come by default.

Just create New GWT Web Application project in eclipse.

Run as Web Application, thats it.

On Monday, 11 June 2012 16:23:20 UTC+5:30, vikash@Atos wrote:
>
> Hi, 
>
> Can you please suggest how the samples in Eclipse for GWT can be 
> configured in Eclipse and run? 
>
> Thanks, 
> Vikash 
>
> On May 31, 8:24 am, Kanagaraj M  wrote: 
> > Eclipse GWT plugin comes with a nice and simple sample project. 
> > You are free to run without any changes. 
> > 
> > 
> > 
> > On Wednesday, 30 May 2012 18:10:48 UTC+5:30, KAVI ARASAN wrote: 
> > 
> > > i am new to GWT, please help me in creating and running GWT 
> > > application in eclipse. 
> > > i need an tutorial which give the step by step process to create the 
> > > first GWT project.- Hide quoted text - 
> > 
> > - Show quoted text -

-- 
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/-/l4vLWZpvA8oJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: SimpleRPC example is not working fine

2012-07-09 Thread Kanagaraj M
Could not open the file in Ubuntu. Can you upload it in another format 
zip,tar, etc?

On Friday, 6 July 2012 19:00:58 UTC+5:30, vikash@Atos wrote:
>
> Hi,
>
> I tried to run SimpleRPC example, but it is not working fine and always 
> show the message in the onFailure method?
> Due to size of the file, I have deleted gwt-servlet.jar file from the 
> attachment.
>
> Please help.
>
>
> Thanks
>

-- 
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/-/u4K8NOjzSQwJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: unknown style in CellTable and scheduledCommand not work

2012-07-09 Thread Thomas Broyer
That "pale yellow" is the style for the currently "keyboard-selected" line.
Maybe tweak your KeyboardSelectionPolicy.

On Monday, July 9, 2012 8:22:04 AM UTC+2, tong123123 wrote:
>
> 1) when user press a Search button, a popupPanel is prompted and I use 
> scheduledCommand to set focus on the upper CellTable (the scheduledCommand 
> is placed in a panel calling the popupPanel, not inside popupPanel), but 
> still no success, the CellTable does not receive focus.
>
> 2) the result is shown as page1 as attached, then I press the forward 
> button in simpepager, the celltable display next page, then I press the 
> sixth record in the CellTable, from page3 as attached, the first row become 
> pale yellow in color!! why would this happen?
>

-- 
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/-/EHtws5JcT2QJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: AsyncDataProvider for a CellTable that must always have an item selected

2012-07-09 Thread Tiago
Ümit,

That's exactly what I've done. I've overridden the method setRowData(int, 
List
> Why don't you override the updateRowData method of your custom CellTable 
> to fire the SelectionChangedEvent?
> The AsyncDataProvider will call updateRowData and this will call it on all 
> attached displays thus also your custom CellTable.
>
>
> On Thursday, July 5, 2012 4:02:50 PM UTC+2, Tiago wrote:
>>
>> Hello,
>>
>> I'm writing a custom Composite widget which contains a CellTable. This 
>> CellTable must always have an item selected. (I wrote an implementation of 
>> DefaultSelectionModel to achieve that). And every time the selection 
>> changes, a specific SelectionEventHandler must be invoked to perform some 
>> modifications in the widget - modifications which depend on the selected 
>> element.
>>
>> This CellTable must be populated with an AsynDataProvider which is given 
>> by "user code", so I can't really change it to adapt to my widget 
>> "internals".
>>
>> How can I make sure that the selection model will fire a 
>> SelectionChangeEvent every time the range changes and the new data 
>> is asynchronously set by the provider?
>> The main problem here is that my SelectionEventHandler must 
>> be executed after the asynchronous request completes, because it depends on 
>> the data loaded from the server. If I simply add another RangeChangeHandler 
>> to the CellTable, even if I add it after the one added by the 
>> AsyncDataProvider, that is not enough because it is likely to execute 
>> before the call to the server returns.
>>
>> I saw there's an addValueChangeHandler on AbstractHasData, which could 
>> help me I guess, but unfortunately it is package protected, and the javadoc 
>> gives the impression it only works for CellBrowser, not CellTable.
>>
>> Anyone has any idea that could help me?
>> If there was a way to add a handler that would react after the 
>> AsyncDataProvider calls updateRowData that would be great...
>>
>> Thank you very much,
>> -- 
>> Tiago Rinck Caveden
>>
>> 

-- 
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/-/izezLQ9KwH0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: unknown style in CellTable and scheduledCommand not work

2012-07-09 Thread tong123123
My KeyboardSelectionPolicy is set to 
KeyboardSelectionPolicy.BOUND_TO_SELECTION.

in fact, in page 3 lower part, the detail information is come from 

> singleSelectionModel.getSelectedObject();
>
and the upper part CellTable (with pale yellow style), it is attached to 
the same SingleSelectionModel.

> table.setSelectionModel(singleSelectionMdoel);
>

so in attached page3,
the lower part, the log date is 2012-Jul-06 15:30:12.347, which is  equal 
to the blue highlighted record in upper celltable, and mean the 
selectionmodel.selectedObject is really point at the sixth record.
and the keyboardSelectionPolicy is BOUND_TO_SELECTION, so why the first row 
is currently "keyboard-selected" line? 




-- 
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/-/-4rAvAHWMK4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: unknown style in CellTable and scheduledCommand not work

2012-07-09 Thread Thomas Broyer


On Monday, July 9, 2012 10:53:05 AM UTC+2, tong123123 wrote:
>
> My KeyboardSelectionPolicy is set to 
> KeyboardSelectionPolicy.BOUND_TO_SELECTION.
>
> in fact, in page 3 lower part, the detail information is come from 
>
>> singleSelectionModel.getSelectedObject();
>>
> and the upper part CellTable (with pale yellow style), it is attached to 
> the same SingleSelectionModel.
>
>> table.setSelectionModel(singleSelectionMdoel);
>>
>
> so in attached page3,
> the lower part, the log date is 2012-Jul-06 15:30:12.347, which is  equal 
> to the blue highlighted record in upper celltable, and mean the 
> selectionmodel.selectedObject is really point at the sixth record.
> and the keyboardSelectionPolicy is BOUND_TO_SELECTION, so why the first 
> row is currently "keyboard-selected" line?
>
>
http://code.google.com/p/google-web-toolkit/issues/detail?id=7480
 

-- 
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/-/SxCWIVpqQGkJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Scheduler and DeferredCommand stopping in unit tests

2012-07-09 Thread salk31
Thanks Joseph,

I'd like to have events fired as the RPC queue changes but my boss, quite 
rightly, would kill me if I changed production code to get the unit tests 
to work ;) 

I've just tried using a Timer (the GWT one) but still stalls :(

Regards

Sam

On Saturday, July 7, 2012 2:48:46 AM UTC+1, Joseph Lust wrote:
>
> I have found that scheduling a deferred event can be at times an 
> anti-pattern. For example, let's say I've got a bunch of UI elements 
> getting initialized. I had in the past used a deferred command to finish 
> the UI init once everything is there. In this case there would be errors 
> that occurred 5% of time when a user was on a stressed browser/old client 
> and the event was returned before all init tasks were complete.
>
> The better way to deal with this I've found is the EventBus and latches. 
> Let's say I needed 10 things setup before the UI can continue, then those 
> 10 things will throw an event to that latch listener and once all 10 are 
> complete, it fires an event to carry on now at the UI is ready. Perhaps 
> this is applicable to your case.
>
> Hope that helps.
>
>
> Sincerely,
> Joseph
>

-- 
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/-/R03ijicVfdAJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



How to test presenter that contains overlay type lightweight collections?

2012-07-09 Thread Alex Luya
I tried to define  interface for lightweight collections as blow, but it
can't be compiled successfully. Any mistake here?

//...Interface...

@SingleJsoImpl(JsArrayExtImpl.class)
public interface JsArrayExt{

public  void add(int addBefore, M model) ;
.
}


//Implementation

public class JsArrayExtImpl extends
JsArray implementsJsArrayExt
{
  protected JsArrayExtImpl() { }

  @Override
  public final native void add(int addBefore, M model) /*-{
this.splice(addBefore, 0, model);
  }-*/;
}
but got error:
Exception in thread "Code server for gwttest from Mozilla/5.0 (X11;
Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1
on ...GWTTest.html?gwt.codesvr=127.0.0.1:9997 @ SR;E74|oFVbz;?F%"
java.lang.NullPointerException
at com.google.gwt.dev.shell.ModuleSpace.dispose(ModuleSpace.java:146)
at
com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:215)
at
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:525)
at
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363)
at java.lang.Thread.run(Thread.java:722)`

-- 
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-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: PopupPanel size problem

2012-07-09 Thread tong123123
is using a percentage of Window.getClientHeight() and 
Window.getClientWidth() the correct direction?

On Monday, July 9, 2012 4:37:33 PM UTC+8, tong123123 wrote:
>
> In developer guide
> https://developers.google.com/web-toolkit/doc/2.4/DevGuideUiPanels
> seems it must explicit set the size inside PopupPanel
> in section
>
>> Using a LayoutPanel without RootLayoutPanel 
>
>
>
> my PopupPanel encloses a DockLayoutPanel and the DockLayoutPanel has size
>
>> setSize("1230px", "720px");
>>
>
> the problem is different computer will have different resolution, so 
> sometime the PopupPanel is too large to see in the client's computer, 
> sometime it is too small to see in another client's computer, any method to 
> resolve it?
>
> the popuppanel is shown as attached (this resolution is just match in my 
> pc, but not in others clients pc).
>
>
>
>

-- 
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/-/O0JkE2ZKRugJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: PopupPanel size problem

2012-07-09 Thread ashwin.desi...@gmail.com
are you setting the size of the docklayout panel or making it use all the
available size of your popuppanel? Yes you can use window %.

I would suggest you set min width and height for your popup panel and make
the docklayout panel cover the width and height of your popup.  Setting min
width and height would ensure that even on small screens your widget would
render tidily.

~Ashwin

On Mon, Jul 9, 2012 at 3:50 PM, tong123123  wrote:

> is using a percentage of Window.getClientHeight() and
> Window.getClientWidth() the correct direction?
>
>
> On Monday, July 9, 2012 4:37:33 PM UTC+8, tong123123 wrote:
>>
>> In developer guide
>> https://developers.google.com/**web-toolkit/doc/2.4/**DevGuideUiPanels
>> seems it must explicit set the size inside PopupPanel
>> in section
>>
>>> Using a LayoutPanel without RootLayoutPanel
>>
>>
>>
>> my PopupPanel encloses a DockLayoutPanel and the DockLayoutPanel has size
>>
>>> setSize("1230px", "720px");
>>>
>>
>> the problem is different computer will have different resolution, so
>> sometime the PopupPanel is too large to see in the client's computer,
>> sometime it is too small to see in another client's computer, any method to
>> resolve it?
>>
>> the popuppanel is shown as attached (this resolution is just match in my
>> pc, but not in others clients pc).
>>
>>
>>
>>  --
> 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/-/O0JkE2ZKRugJ.
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
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-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Scheduler and DeferredCommand stopping in unit tests

2012-07-09 Thread salk31
Maybe related to this:
http://code.google.com/p/google-web-toolkit/issues/detail?id=2391 

(Only just remembered that Timer exists!)

On Friday, July 6, 2012 10:23:02 AM UTC+1, salk31 wrote:
>
> Has anybody else had cases where Scheduler and DeferredCommands have 
> stopped being scheduled/run when used in unit tests?
>
> We have a lot of async code so need to use them a lot but currently, 
> seemingly at random, our tests stall until they get timed out. Even setting 
> up a periodic job that is never meant to stop will fail at the same 
> time/point as our normal jobs.
>
> Lot of code going on with 
> junit/GWTTestCase/htmlunit/jetty/requestfactory/database... and because it 
> is hard to reproduce it is proving tough to fix.
>
> Many thanks
>
> Sam
>
>

-- 
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/-/C_QWvxPApJYJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Google IO 2012 : no GWT session ?

2012-07-09 Thread Ümit Seren
Sounds really good. 
I got some time to watch some of the I/O conference videos specifically on 
HTML5 and web technologies. 
One of the talks that got me really exciting was the one about Web 
components (https://developers.google.com/events/io/sessions/gooio2012/205/
).
Considering that GWT really advocates encapsulation and components that 
seems to be a natural fit for it. 
Maybe it's too early to comments on that but as you are in the steering 
committee, are there any plans to embrace these new technologies with 
future GWT versions?

cheers
Ümit

On Sunday, July 8, 2012 4:01:42 PM UTC+2, Daniel Kurka wrote:
>
> I have been on IO all week and talked to many people from the GWT team and 
> other GWT developers.
>
> I am not worried at all about GWTs future. It had a bad marketing in the 
> last year due to many reasons which we will turn around in the upcoming 
> months with the GWT steering committee.
>
> The GWT 2.5 release is one of the biggest GWT ever and has many new things 
> in there. Wait for Rays talk to appear (in which I play a very small role) 
> on the youtube in a few days to clear things up for you.
>
> -Daniel
>
>
>
>
> Am 06.07.2012 um 22:04 schrieb Murray:
>
> Daniel,
>
> I was at Google I/O last week and decided ask for myself.. the responses I 
> got, was NOT good
> I flat out asked one Googler, working a developer "bar" in the main lobby 
>  (not sure what team he was on) 
> "..should I continue my project that's not yet released, in GWT or 
> what..?" and he appeared to be reluctant
> to say...suggesting that something was up! he then went on to say he would 
> change it to DART as it
> is not yet a complete standard So then I asked "..what about 
> JSP/Appengine or Python?"  and with a big Grin
> on if face he shuck his head affirmatively violently ... as if to say 
> he doesn't want it to be said that "he told me so"
>
> right now we need some GWT folks to step up and 
> say something definitive!!!  this "rumor" has been going around for 
> a while now.. and there were no Sessions on GWT at the IO2012 other than 
> Porting GWT to DART !!!
>
> I went to a session on Appengine /REST and a a question was asked at the 
> end of the session regarding 
> REST and GWT the answer was also suspect...
>
> I think this link will take you to the session ..forward to the end...
>  https://developers.google.com/events/io/sessions/gooio2012/121/
>
>
>
>
>
> On Friday, June 22, 2012 1:54:29 PM UTC-4, Daniel Kurka wrote:
>>
>> I can assure you (since I am deeply invested in GWT) that GWT is in no 
>> way of being phased out. The main reason is the amount of other talks 
>> (android, google+) being added to the conference, reducing talk time for 
>> everyone else.
>> As Thomas said before there is something big coming for GWT which will be 
>> announced in Rays talk at IO.
>>
>> There are a lot of google products relying on GWT which is not something 
>> that you could change in a short amount of time. Dart may be an interesting 
>> project, but it is not going to change the way google currently depends on 
>> GWT (at least not in the next years).
>>
>> The fact that the GWT team is looking for team members on the google 
>> employment list should also put you in the direction that this is no where 
>> near dead.
>>
>> So hopefully as a contributer to the project I can calm you nerves a 
>> little.
>>
>> -Daniel
>>
>>
>>
>>
>>
>>
>> Am 19.06.2012 um 19:29 schrieb Thomas Lefort:
>>
>>
>> https://groups.google.com/forum/?fromgroups#!topic/Google-Web-Toolkit-Employment/NJmWmKsXQlI
>>
>> sounds pretty healthy to me :)
>>
>> I bet competition will be fierce!
>>
>>
>> On Thursday, 17 May 2012 08:00:00 UTC+2, Celinio Fernandes wrote:
>>>
>>> Hello,
>>> I just noticed that the schedule for Google IO 2012 is now available : 
>>> https://developers.google.com/events/io/sessions
>>> Not sure whether it is definitive or not.
>>> I see that this year there is no session dedicated to GWT. How come ? 
>>> But there are 2 sessions dedicated to Dart. Is this a sign ?
>>>
>>>
>>>
>>>
>> -- 
>> 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/-/m0up22vaGNoJ.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>>
>>
> -- 
> 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/-/Jh2IrAfsH8MJ.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options,

Re: GWT 2.5 RC1 Is Here!

2012-07-09 Thread wytten
For some reason our app often fails to load when using the xsiframe linker.
When 2.5.0 releases will the default linker be supported for Super Dev Mode?

Thanks!

On Wednesday, June 27, 2012 3:39:07 PM UTC-5, Rajeev Dayal wrote:
>
> Hey all,
>
> We're excited to announce the GWT 2.5 Release Candidate! Read about it on 
> the GWT Blog , 
> and download it here  
> (bottom 
> of the page). The RC has been uploaded to Maven Central with the version 
> string of 2.5.0-rc1.
>
> Please give it a try and let us know your feedback! Also, many thanks to 
> all of you for your contributions. Without your help, we wouldn't have had 
> a GWT 2.5 release at all!
>
>
> -Rajeev, on behalf of the GWT team
>

-- 
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/-/B7pdDHaQTi0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Super Dev Mode general question

2012-07-09 Thread sannysan...@gmail.com
Hello, 

I recently found this topic about Super Dev Mode appearing in GWT 2.5.
I am happy that new way of debugging is coming to the GWT development 
process.
But I am not happy that there are plans to discard current DevMode in the 
future. At least, each official mentioning of SuperDevMode means that it 
will replace current DevMode.

If this is true, then I am not happy at all.

Debugging in the IDE of choice was always top feature of GWT for me. 
Ability to freely navigate code, use typesafe autocompletion in evaluate 
expression boxes, drop stack frame feature and all other hundreds of 
java-specific little features is great joy. Forcing developers to discard 
all this and be tied to browser is at least major regress.

I could not find any discussion on this topic, if there's any, PLEASE 
direct me to the page where it all was discussed and decision was made, i 
want to see the arguments. I found only "browser plugins are instable" 
topic. But people, concept is already working satisfactory for several 
years and I don't want to lose it in future because it is not 100% perfect 
and crashes sometimes. 

Telling "source code maps are being implemented in browsers at the moment" 
and at the same time arguing that SuperDevMode will make us 
browser-independent seems like lame joke. At least, not all browsers will. 
But even if all major browsers (Chrome, FF, Safari, IE) will, source maps 
is only part of the picture. The debugging in all browsers has its own 
interface, keymaps etc, and, as I wrote above it never compares to the 
IDE/Native java debugging. In other words, it does not compare!

TLDR: questions:
1) Is it true that SuperDevMode will replace DevMode
2) If yes, then for the sake of God, why such regress?

Alex.

-- 
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/-/WeZAgTLfKH4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Video from io 2012 : "The History and Future of Google Web Toolkit"

2012-07-09 Thread Gilberto
Waiting for it as well:

http://www.youtube.com/user/GoogleDevelopers/videos?query=gwt

http://www.youtube.com/user/GoogleDevelopers/videos?query=%22google+web+toolkit%22

(Couldn't find a way to make OR queries in YouTube =/)

On Friday, July 6, 2012 4:57:28 AM UTC-3, Nicolas Antoniazzi wrote:
>
> Does anyone know if there is a video about the gwt session from io 2012: 
> "The History and Future of Google Web Toolkit" by Ray Cromwell?
>
> I know that it was not live streamed, but I tought that we could get a 
> delayed video.
>

-- 
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/-/OpHr7ZKBUi0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Google IO 2012 : no GWT session ?

2012-07-09 Thread Joshua Kappon
We're hoping that the steering committee will make steps for reaching and 
expanding the GWT community more actively.
I think that a great step in this direction is establishing a road-map with 
the help of the community.

Regular GWT Hangouts could also be nice ;)


On Sunday, July 8, 2012 5:01:42 PM UTC+3, Daniel Kurka wrote:
>
> I have been on IO all week and talked to many people from the GWT team and 
> other GWT developers.
>
> I am not worried at all about GWTs future. It had a bad marketing in the 
> last year due to many reasons which we will turn around in the upcoming 
> months with the GWT steering committee.
>
> The GWT 2.5 release is one of the biggest GWT ever and has many new things 
> in there. Wait for Rays talk to appear (in which I play a very small role) 
> on the youtube in a few days to clear things up for you.
>
> -Daniel
>
>
>
>
> Am 06.07.2012 um 22:04 schrieb Murray:
>
> Daniel,
>
> I was at Google I/O last week and decided ask for myself.. the responses I 
> got, was NOT good
> I flat out asked one Googler, working a developer "bar" in the main lobby 
>  (not sure what team he was on) 
> "..should I continue my project that's not yet released, in GWT or 
> what..?" and he appeared to be reluctant
> to say...suggesting that something was up! he then went on to say he would 
> change it to DART as it
> is not yet a complete standard So then I asked "..what about 
> JSP/Appengine or Python?"  and with a big Grin
> on if face he shuck his head affirmatively violently ... as if to say 
> he doesn't want it to be said that "he told me so"
>
> right now we need some GWT folks to step up and 
> say something definitive!!!  this "rumor" has been going around for 
> a while now.. and there were no Sessions on GWT at the IO2012 other than 
> Porting GWT to DART !!!
>
> I went to a session on Appengine /REST and a a question was asked at the 
> end of the session regarding 
> REST and GWT the answer was also suspect...
>
> I think this link will take you to the session ..forward to the end...
>  https://developers.google.com/events/io/sessions/gooio2012/121/
>
>
>
>
>
> On Friday, June 22, 2012 1:54:29 PM UTC-4, Daniel Kurka wrote:
>>
>> I can assure you (since I am deeply invested in GWT) that GWT is in no 
>> way of being phased out. The main reason is the amount of other talks 
>> (android, google+) being added to the conference, reducing talk time for 
>> everyone else.
>> As Thomas said before there is something big coming for GWT which will be 
>> announced in Rays talk at IO.
>>
>> There are a lot of google products relying on GWT which is not something 
>> that you could change in a short amount of time. Dart may be an interesting 
>> project, but it is not going to change the way google currently depends on 
>> GWT (at least not in the next years).
>>
>> The fact that the GWT team is looking for team members on the google 
>> employment list should also put you in the direction that this is no where 
>> near dead.
>>
>> So hopefully as a contributer to the project I can calm you nerves a 
>> little.
>>
>> -Daniel
>>
>>
>>
>>
>>
>>
>> Am 19.06.2012 um 19:29 schrieb Thomas Lefort:
>>
>>
>> https://groups.google.com/forum/?fromgroups#!topic/Google-Web-Toolkit-Employment/NJmWmKsXQlI
>>
>> sounds pretty healthy to me :)
>>
>> I bet competition will be fierce!
>>
>>
>> On Thursday, 17 May 2012 08:00:00 UTC+2, Celinio Fernandes wrote:
>>>
>>> Hello,
>>> I just noticed that the schedule for Google IO 2012 is now available : 
>>> https://developers.google.com/events/io/sessions
>>> Not sure whether it is definitive or not.
>>> I see that this year there is no session dedicated to GWT. How come ? 
>>> But there are 2 sessions dedicated to Dart. Is this a sign ?
>>>
>>>
>>>
>>>
>> -- 
>> 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/-/m0up22vaGNoJ.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>>
>>
> -- 
> 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/-/Jh2IrAfsH8MJ.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>

-- 
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/-/wi

Re: Super Dev Mode general question

2012-07-09 Thread Thomas Broyer


On Monday, July 9, 2012 3:24:19 PM UTC+2, sanny...@gmail.com wrote:
>
> Hello, 
>
> I recently found this topic about Super Dev Mode appearing in GWT 2.5.
> I am happy that new way of debugging is coming to the GWT development 
> process.
> But I am not happy that there are plans to discard current DevMode in the 
> future. At least, each official mentioning of SuperDevMode means that it 
> will replace current DevMode.
>
> If this is true, then I am not happy at all.
>
> Debugging in the IDE of choice was always top feature of GWT for me. 
> Ability to freely navigate code, use typesafe autocompletion in evaluate 
> expression boxes, drop stack frame feature and all other hundreds of 
> java-specific little features is great joy. Forcing developers to discard 
> all this and be tied to browser is at least major regress.
>
> I could not find any discussion on this topic, if there's any, PLEASE 
> direct me to the page where it all was discussed and decision was made, i 
> want to see the arguments. I found only "browser plugins are instable" 
> topic. But people, concept is already working satisfactory for several 
> years and I don't want to lose it in future because it is not 100% perfect 
> and crashes sometimes. 
>
> Telling "source code maps are being implemented in browsers at the moment" 
> and at the same time arguing that SuperDevMode will make us 
> browser-independent seems like lame joke. At least, not all browsers will. 
> But even if all major browsers (Chrome, FF, Safari, IE) will, source maps 
> is only part of the picture. The debugging in all browsers has its own 
> interface, keymaps etc, and, as I wrote above it never compares to the 
> IDE/Native java debugging. In other words, it does not compare!
>
> TLDR: questions:
> 1) Is it true that SuperDevMode will replace DevMode
>

Who knows?
More seriously, you can be assured DevMode will stay for quite some time.
 

> 2) If yes, then for the sake of God, why such regress?
>

Browser plugins are a nightmare to maintain.
The plugin for Chrome is known to be buggy and unstable.
Every 6 weeks, the plugin for Firefox has to be updated (we could choose to 
only support Firefox ESR, but I doubt you'd be happy; I wouldn't be).
I've heard there had been issues with the Safari plugin on OS X at some 
point, due to a browser upgrade.
The only stable plugin for now is the one for IE, and even that one 
required some work to make it compatible with IE9 and the newer versions of 
Windows.
Generally, browser vendors don't help us maintain plugins.

Due to this fact, no new plugin is being developed, so debugging in Opera, 
or Safari on Windows, won't ever be possible (OK, that's rhetoric anyway, 
as nobody minds ;-) ).

But now we also have to support mobile development: iOS, Chrome for 
Android, Firefox Mobile, Windows 8, etc. and those browsers don't even 
allow us to use plugins!
And that's where SuperDevMode shines with its plugin-free approach: it 
brings DevMode to any single browser out there, at the expense of using the 
browser's own dev tools.

So, what the future is?
Honestly, to me, the future is in wire protocols for JS debuggers. Opera 
has had one for long, Chrome too. Mozilla is building one. I can't tell for 
IE but at least you can debug a local IE instance so it's better than 
nothing, and we can have hopes that DevMode as we know it will be supported 
for quite a long time (compared to other browsers).
With such protocols, your IDE could connect to your browser and use 
SourceMaps to give you (almost) the same debugging experience as if you 
were running your code "natively" (technically, I believe it could also be 
made so; based on an experiment I made a few years back to bring DevMode to 
Adobe AIR through the Flash debugger). This, to me, is the way forward. It 
would however require a tremendous amount of work, so it's not going to 
happen any time soon. http://code.google.com/p/chromedevtools/ could help 
here I guess, but it's still a very tiny part of what's needed to bring the 
same level of debugging as with the current DevMode.

10 years after the Internet Bubble, web dev is only starting to make its 
revolution towards "professionalization" (MVC was seen as a thing of the 
past until Backbone et al. revived it). GWT is ahead of its time here with 
leveraging Java dev tools, but web dev is still for the most part the same 
as 10 years ago. console.log replaced window.alert, but it hasn't really 
changed.

I believe, DevMode (as we know it) will fade away, either replaced by 
SuperDevMode or something based on it (better integrated in the IDE), or 
rewritten atop wire debugging protocols instead of plugins. It will take 
time though, and in the mean time DevMode won't change, and SuperDevMode 
helps us support new browsers at virtually no cost.

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

Re: gwtc X closure optimizations

2012-07-09 Thread Alan Leung
A few more noteworthy ones:

Variable name reuse:
  var x = .;  print(x); var y = ..; print(y)
  becomes
var x = .;  print(x);   x  = ..; print(x)

More aggressive inlining with variables and functions.

A lot more small optimizations that saves a char here and there.

Closure Compiler would also put more effort into your JSNI code for obvious
reasons.

-Alan



On Thu, Jul 5, 2012 at 9:31 AM, Thomas Broyer  wrote:

>
>
> On Thursday, July 5, 2012 5:37:08 AM UTC+2, Magno Machado wrote:
>>
>> I was impressed to see the results achieved on gwt 2.5 by combining the
>> gwt compiler and closure compiler.
>>
>> Well, I always thought there's nothing that closure could do that the gwt
>> compiler couldn't already do, because gwtc have a lot more information
>> about the source than closure compiler.
>>
>
> Yes and no: Closure has "static typing" via JSDoc annotations, and uses
> the same kind of monolithic compilation (i.e. I know everything about what
> will run, so I know what is never used that I can remove).
>
> So I wonder what kind of optimizations closure is doing that were not
>> already done by the gwt compiler?
>>
>
> One small optimization I've read on the Closure Compiler group that I know
> GWT doesn't do: ["ab", "cd", "ef", "ghij"] is compiled into
> "ab,cd,ef,ghij".split(",") !
> (it's more in terms of perfs than in code size I guess though).
> I don't know about the other differences.
>
> --
> 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/-/EBpT-fnjCHcJ.
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
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-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



GWT 2.5RC1 - UiRenderer

2012-07-09 Thread Deepak Singh
Hi,

I updated my GWT sdk to 2.5Rc1 and eclipse plugin.

I am trying to use UiRenderer. I find that there is no option available
with new eclipse plugin to generate auto UiRenderer as we have for UiBinder
with sample code.

Any idea on how can i get some UiRenderer generated with sample code ?

I have an existing UiBinder with click events consumed and want to use it
as cell. I am getting lot of errors while converting it according to the
doc available at
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiBinder#Rendering_HTML_for_Cells

Thats the reason i want some sample code working.

Any help appreciated.

Thanks
Deepak Singh

-- 
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-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Super Dev Mode general question

2012-07-09 Thread Dennis Haupt
i don't know about eclipse, but intellij can remote-debug chrome and
firefox, including the evaluation of expressions.
it probably won't be long before they add support for source maps, too.
i wouldn't worry too much.

Am 09.07.2012 16:51, schrieb Thomas Broyer:
> 
> 
> On Monday, July 9, 2012 3:24:19 PM UTC+2, sanny...@gmail.com wrote:
> 
> Hello, 
> 
> I recently found this topic about Super Dev Mode appearing in GWT 2.5.
> I am happy that new way of debugging is coming to the GWT
> development process.
> But I am not happy that there are plans to discard current DevMode
> in the future. At least, each official mentioning of SuperDevMode
> means that it will replace current DevMode.
> 
> If this is true, then I am not happy at all.
> 
> Debugging in the IDE of choice was always top feature of GWT for me.
> Ability to freely navigate code, use typesafe autocompletion in
> evaluate expression boxes, drop stack frame feature and all other
> hundreds of java-specific little features is great joy. Forcing
> developers to discard all this and be tied to browser is at least
> major regress.
> 
> I could not find any discussion on this topic, if there's any,
> PLEASE direct me to the page where it all was discussed and decision
> was made, i want to see the arguments. I found only "browser plugins
> are instable" topic. But people, concept is already working
> satisfactory for several years and I don't want to lose it in future
> because it is not 100% perfect and crashes sometimes. 
> 
> Telling "source code maps are being implemented in browsers at the
> moment" and at the same time arguing that SuperDevMode will make us
> browser-independent seems like lame joke. At least, not all browsers
> will. But even if all major browsers (Chrome, FF, Safari, IE) will,
> source maps is only part of the picture. The debugging in all
> browsers has its own interface, keymaps etc, and, as I wrote above
> it never compares to the IDE/Native java debugging. In other words,
> it does not compare!
> 
> TLDR: questions:
> 1) Is it true that SuperDevMode will replace DevMode
> 
> 
> Who knows?
> More seriously, you can be assured DevMode will stay for quite some time.
>  
> 
> 2) If yes, then for the sake of God, why such regress?
> 
> 
> Browser plugins are a nightmare to maintain.
> The plugin for Chrome is known to be buggy and unstable.
> Every 6 weeks, the plugin for Firefox has to be updated (we could choose
> to only support Firefox ESR, but I doubt you'd be happy; I wouldn't be).
> I've heard there had been issues with the Safari plugin on OS X at some
> point, due to a browser upgrade.
> The only stable plugin for now is the one for IE, and even that one
> required some work to make it compatible with IE9 and the newer versions
> of Windows.
> Generally, browser vendors don't help us maintain plugins.
> 
> Due to this fact, no new plugin is being developed, so debugging in
> Opera, or Safari on Windows, won't ever be possible (OK, that's rhetoric
> anyway, as nobody minds ;-) ).
> 
> But now we also have to support mobile development: iOS, Chrome for
> Android, Firefox Mobile, Windows 8, etc. and those browsers don't even
> allow us to use plugins!
> And that's where SuperDevMode shines with its plugin-free approach: it
> brings DevMode to any single browser out there, at the expense of using
> the browser's own dev tools.
> 
> So, what the future is?
> Honestly, to me, the future is in wire protocols for JS debuggers. Opera
> has had one for long, Chrome too. Mozilla is building one. I can't tell
> for IE but at least you can debug a local IE instance so it's better
> than nothing, and we can have hopes that DevMode as we know it will be
> supported for quite a long time (compared to other browsers).
> With such protocols, your IDE could connect to your browser and use
> SourceMaps to give you (almost) the same debugging experience as if you
> were running your code "natively" (technically, I believe it could also
> be made so; based on an experiment I made a few years back to bring
> DevMode to Adobe AIR through the Flash debugger). This, to me, is the
> way forward. It would however require a tremendous amount of work, so
> it's not going to happen any time
> soon. http://code.google.com/p/chromedevtools/ could help here I guess,
> but it's still a very tiny part of what's needed to bring the same level
> of debugging as with the current DevMode.
> 
> 10 years after the Internet Bubble, web dev is only starting to make its
> revolution towards "professionalization" (MVC was seen as a thing of the
> past until Backbone et al. revived it). GWT is ahead of its time here
> with leveraging Java dev tools, but web dev is still for the most part
> the same as 10 years ago. console.log replaced window.alert, but it
> hasn't really changed.
> 
> I believe, DevMode (as we know it) will fade away, either r

Re: Download file from server to client - w Servlet etc PLEASE?

2012-07-09 Thread MIKE
Hi,
>
>
I got the following error. Any help please ? 

HTTP ERROR: 405

HTTP method GET is not supported by this URL

RequestURI=/name/Download

*Powered by Jetty:// *

-- 
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/-/w0EG54RwWQ0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Super Dev Mode general question

2012-07-09 Thread Clint Gilbert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I understand that browser plugins are problematic.  I wouldn't want to
be responsible for building a new plugin for each week's Firefox
release.  (Obviously, I'm joking.)

But debuggers in current Java IDEs are very robust and full-featured.
 Every Javascript debugger in every browser that I've ever tried has
been inadequate in comparison.

Hopefully regular dev mode will live on for long enough for JS
debuggers to improve significantly, though I fear that will take a
long time.

Count me among those who will miss the useful features of the existing
dev mode when it goes away.

On 07/09/2012 10:51 AM, Thomas Broyer wrote:
> 
> 
> On Monday, July 9, 2012 3:24:19 PM UTC+2, sanny...@gmail.com
> wrote:
> 
> Hello,
> 
> I recently found this topic about Super Dev Mode appearing in GWT
> 2.5. I am happy that new way of debugging is coming to the GWT 
> development process. But I am not happy that there are plans to
> discard current DevMode in the future. At least, each official
> mentioning of SuperDevMode means that it will replace current
> DevMode.
> 
> If this is true, then I am not happy at all.
> 
> Debugging in the IDE of choice was always top feature of GWT for
> me. Ability to freely navigate code, use typesafe autocompletion
> in evaluate expression boxes, drop stack frame feature and all
> other hundreds of java-specific little features is great joy.
> Forcing developers to discard all this and be tied to browser is at
> least major regress.
> 
> I could not find any discussion on this topic, if there's any, 
> PLEASE direct me to the page where it all was discussed and
> decision was made, i want to see the arguments. I found only
> "browser plugins are instable" topic. But people, concept is
> already working satisfactory for several years and I don't want to
> lose it in future because it is not 100% perfect and crashes
> sometimes.
> 
> Telling "source code maps are being implemented in browsers at the 
> moment" and at the same time arguing that SuperDevMode will make
> us browser-independent seems like lame joke. At least, not all
> browsers will. But even if all major browsers (Chrome, FF, Safari,
> IE) will, source maps is only part of the picture. The debugging in
> all browsers has its own interface, keymaps etc, and, as I wrote
> above it never compares to the IDE/Native java debugging. In other
> words, it does not compare!
> 
> TLDR: questions: 1) Is it true that SuperDevMode will replace
> DevMode
> 
> 
> Who knows? More seriously, you can be assured DevMode will stay for
> quite some time.
> 
> 
> 2) If yes, then for the sake of God, why such regress?
> 
> 
> Browser plugins are a nightmare to maintain. The plugin for Chrome
> is known to be buggy and unstable. Every 6 weeks, the plugin for
> Firefox has to be updated (we could choose to only support Firefox
> ESR, but I doubt you'd be happy; I wouldn't be). I've heard there
> had been issues with the Safari plugin on OS X at some point, due
> to a browser upgrade. The only stable plugin for now is the one for
> IE, and even that one required some work to make it compatible with
> IE9 and the newer versions of Windows. Generally, browser vendors
> don't help us maintain plugins.
> 
> Due to this fact, no new plugin is being developed, so debugging
> in Opera, or Safari on Windows, won't ever be possible (OK, that's
> rhetoric anyway, as nobody minds ;-) ).
> 
> But now we also have to support mobile development: iOS, Chrome
> for Android, Firefox Mobile, Windows 8, etc. and those browsers
> don't even allow us to use plugins! And that's where SuperDevMode
> shines with its plugin-free approach: it brings DevMode to any
> single browser out there, at the expense of using the browser's own
> dev tools.
> 
> So, what the future is? Honestly, to me, the future is in wire
> protocols for JS debuggers. Opera has had one for long, Chrome too.
> Mozilla is building one. I can't tell for IE but at least you can
> debug a local IE instance so it's better than nothing, and we can
> have hopes that DevMode as we know it will be supported for quite a
> long time (compared to other browsers). With such protocols, your
> IDE could connect to your browser and use SourceMaps to give you
> (almost) the same debugging experience as if you were running your
> code "natively" (technically, I believe it could also be made so;
> based on an experiment I made a few years back to bring DevMode to
> Adobe AIR through the Flash debugger). This, to me, is the way
> forward. It would however require a tremendous amount of work, so 
> it's not going to happen any time soon.
> http://code.google.com/p/chromedevtools/ could help here I guess, 
> but it's still a very tiny part of what's needed to bring the same
> level of debugging as with the current DevMode.
> 
> 10 years after the Internet Bubble, web dev is only starting to
> make its revolution towards "professionalization" (MVC was seen as
> a thing of the past unt

Re: Super Dev Mode general question

2012-07-09 Thread Daniel Kurka
Ray mentioned on IO that they were talking somehow already (I am not 100% sure 
about the state), but there was something about direct support for that in 
intellij

Am 09.07.2012 um 20:48 schrieb Dennis Haupt:

> i don't know about eclipse, but intellij can remote-debug chrome and
> firefox, including the evaluation of expressions.
> it probably won't be long before they add support for source maps, too.
> i wouldn't worry too much.
> 
> Am 09.07.2012 16:51, schrieb Thomas Broyer:
>> 
>> 
>> On Monday, July 9, 2012 3:24:19 PM UTC+2, sanny...@gmail.com wrote:
>> 
>>Hello, 
>> 
>>I recently found this topic about Super Dev Mode appearing in GWT 2.5.
>>I am happy that new way of debugging is coming to the GWT
>>development process.
>>But I am not happy that there are plans to discard current DevMode
>>in the future. At least, each official mentioning of SuperDevMode
>>means that it will replace current DevMode.
>> 
>>If this is true, then I am not happy at all.
>> 
>>Debugging in the IDE of choice was always top feature of GWT for me.
>>Ability to freely navigate code, use typesafe autocompletion in
>>evaluate expression boxes, drop stack frame feature and all other
>>hundreds of java-specific little features is great joy. Forcing
>>developers to discard all this and be tied to browser is at least
>>major regress.
>> 
>>I could not find any discussion on this topic, if there's any,
>>PLEASE direct me to the page where it all was discussed and decision
>>was made, i want to see the arguments. I found only "browser plugins
>>are instable" topic. But people, concept is already working
>>satisfactory for several years and I don't want to lose it in future
>>because it is not 100% perfect and crashes sometimes. 
>> 
>>Telling "source code maps are being implemented in browsers at the
>>moment" and at the same time arguing that SuperDevMode will make us
>>browser-independent seems like lame joke. At least, not all browsers
>>will. But even if all major browsers (Chrome, FF, Safari, IE) will,
>>source maps is only part of the picture. The debugging in all
>>browsers has its own interface, keymaps etc, and, as I wrote above
>>it never compares to the IDE/Native java debugging. In other words,
>>it does not compare!
>> 
>>TLDR: questions:
>>1) Is it true that SuperDevMode will replace DevMode
>> 
>> 
>> Who knows?
>> More seriously, you can be assured DevMode will stay for quite some time.
>> 
>> 
>>2) If yes, then for the sake of God, why such regress?
>> 
>> 
>> Browser plugins are a nightmare to maintain.
>> The plugin for Chrome is known to be buggy and unstable.
>> Every 6 weeks, the plugin for Firefox has to be updated (we could choose
>> to only support Firefox ESR, but I doubt you'd be happy; I wouldn't be).
>> I've heard there had been issues with the Safari plugin on OS X at some
>> point, due to a browser upgrade.
>> The only stable plugin for now is the one for IE, and even that one
>> required some work to make it compatible with IE9 and the newer versions
>> of Windows.
>> Generally, browser vendors don't help us maintain plugins.
>> 
>> Due to this fact, no new plugin is being developed, so debugging in
>> Opera, or Safari on Windows, won't ever be possible (OK, that's rhetoric
>> anyway, as nobody minds ;-) ).
>> 
>> But now we also have to support mobile development: iOS, Chrome for
>> Android, Firefox Mobile, Windows 8, etc. and those browsers don't even
>> allow us to use plugins!
>> And that's where SuperDevMode shines with its plugin-free approach: it
>> brings DevMode to any single browser out there, at the expense of using
>> the browser's own dev tools.
>> 
>> So, what the future is?
>> Honestly, to me, the future is in wire protocols for JS debuggers. Opera
>> has had one for long, Chrome too. Mozilla is building one. I can't tell
>> for IE but at least you can debug a local IE instance so it's better
>> than nothing, and we can have hopes that DevMode as we know it will be
>> supported for quite a long time (compared to other browsers).
>> With such protocols, your IDE could connect to your browser and use
>> SourceMaps to give you (almost) the same debugging experience as if you
>> were running your code "natively" (technically, I believe it could also
>> be made so; based on an experiment I made a few years back to bring
>> DevMode to Adobe AIR through the Flash debugger). This, to me, is the
>> way forward. It would however require a tremendous amount of work, so
>> it's not going to happen any time
>> soon. http://code.google.com/p/chromedevtools/ could help here I guess,
>> but it's still a very tiny part of what's needed to bring the same level
>> of debugging as with the current DevMode.
>> 
>> 10 years after the Internet Bubble, web dev is only starting to make its
>> revolution towards "professionalization" (MVC was seen as a thing of the
>> past until Backbone

Re: Google IO 2012 : no GWT session ?

2012-07-09 Thread Daniel Kurka
I am open to listen to what GWT developers have to say and to get a good 
feedback loop going.

So if you have something in mind please bring it up in the gwt contributer list 
I will take a look for sure!

-Daniel



Am 09.07.2012 um 16:01 schrieb Joshua Kappon:

> We're hoping that the steering committee will make steps for reaching and 
> expanding the GWT community more actively.
> I think that a great step in this direction is establishing a road-map with 
> the help of the community.
> 
> Regular GWT Hangouts could also be nice ;)
> 
> 
> On Sunday, July 8, 2012 5:01:42 PM UTC+3, Daniel Kurka wrote:
> I have been on IO all week and talked to many people from the GWT team and 
> other GWT developers.
> 
> I am not worried at all about GWTs future. It had a bad marketing in the last 
> year due to many reasons which we will turn around in the upcoming months 
> with the GWT steering committee.
> 
> The GWT 2.5 release is one of the biggest GWT ever and has many new things in 
> there. Wait for Rays talk to appear (in which I play a very small role) on 
> the youtube in a few days to clear things up for you.
> 
> -Daniel
> 
> 
> 
> 
> Am 06.07.2012 um 22:04 schrieb Murray:
> 
>> Daniel,
>> 
>> I was at Google I/O last week and decided ask for myself.. the responses I 
>> got, was NOT good
>> I flat out asked one Googler, working a developer "bar" in the main lobby  
>> (not sure what team he was on) 
>> "..should I continue my project that's not yet released, in GWT or what..?" 
>> and he appeared to be reluctant
>> to say...suggesting that something was up! he then went on to say he would 
>> change it to DART as it
>> is not yet a complete standard So then I asked "..what about 
>> JSP/Appengine or Python?"  and with a big Grin
>> on if face he shuck his head affirmatively violently ... as if to say he 
>> doesn't want it to be said that "he told me so"
>> 
>> right now we need some GWT folks to step up and say something definitive!!!  
>> this "rumor" has been going around for 
>> a while now.. and there were no Sessions on GWT at the IO2012 other than 
>> Porting GWT to DART !!!
>> 
>> I went to a session on Appengine /REST and a a question was asked at the end 
>> of the session regarding 
>> REST and GWT the answer was also suspect...
>> 
>> I think this link will take you to the session ..forward to the end...
>>  https://developers.google.com/events/io/sessions/gooio2012/121/
>> 
>> 
>> 
>> 
>> 
>> On Friday, June 22, 2012 1:54:29 PM UTC-4, Daniel Kurka wrote:
>> I can assure you (since I am deeply invested in GWT) that GWT is in no way 
>> of being phased out. The main reason is the amount of other talks (android, 
>> google+) being added to the conference, reducing talk time for everyone else.
>> As Thomas said before there is something big coming for GWT which will be 
>> announced in Rays talk at IO.
>> 
>> There are a lot of google products relying on GWT which is not something 
>> that you could change in a short amount of time. Dart may be an interesting 
>> project, but it is not going to change the way google currently depends on 
>> GWT (at least not in the next years).
>> 
>> The fact that the GWT team is looking for team members on the google 
>> employment list should also put you in the direction that this is no where 
>> near dead.
>> 
>> So hopefully as a contributer to the project I can calm you nerves a little.
>> 
>> -Daniel
>> 
>> 
>> 
>> 
>> 
>> 
>> Am 19.06.2012 um 19:29 schrieb Thomas Lefort:
>> 
>>> https://groups.google.com/forum/?fromgroups#!topic/Google-Web-Toolkit-Employment/NJmWmKsXQlI
>>> 
>>> sounds pretty healthy to me :)
>>> 
>>> I bet competition will be fierce!
>>> 
>>> 
>>> On Thursday, 17 May 2012 08:00:00 UTC+2, Celinio Fernandes wrote:
>>> Hello,
>>> I just noticed that the schedule for Google IO 2012 is now available : 
>>> https://developers.google.com/events/io/sessions
>>> Not sure whether it is definitive or not.
>>> I see that this year there is no session dedicated to GWT. How come ? 
>>> But there are 2 sessions dedicated to Dart. Is this a sign ?
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> 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/-/m0up22vaGNoJ.
>>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> google-web-toolkit+unsubscr...@googlegroups.com.
>>> For more options, visit this group at 
>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>> 
>> 
>> -- 
>> 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/-/Jh2IrAfsH8MJ.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> goog

Server class 'XXX' could not be found in the web app, but was found on the system classpath

2012-07-09 Thread joerg.hohwil...@googlemail.com
I am developing an open-source software using GWT 2.4.0 and maven3 with 
~100 modules.
Now I have trouble with GWT development mode in Eclipse (I just started 
with the new GWT client).

There are various warnings of this kind:

[WARN] Server class 'XXX' could not be found in the web app, but was found 
on the system classpath
   [WARN] Adding classpath entry 'XXX' to the web app classpath for this 
session

So far so good - I read and understood the documentation what this is about.
However, I now have the opposite problem:

[09 Jul 2012 21:30:46] ERROR 
[org.springframework.web.servlet.DispatcherServlet][initServletBean]: 
Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'RemoteInvocationGenericServiceUrlMapping' defined in class 
path resource [net/sf/mmm/service/beans-service-gwt.xml]: Initialization of 
bean failed; nested exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
named 'RemoteInvocationGenericServiceServlet' is defined

The reason for this problem is that I am using CDI annotations like @Named 
and therefore make spring to find my server-side components automatically 
on the classpath.
Now only these modules get on the classpath that are somehow directly 
referenced from my web.xml and what is happening from there explicitly.
In other words as long as the module (JAR) containing 
RemoteInvocationGenericServiceUrlMapping is not somehow referenced on 
bootstrap causing the according:
   [WARN] Adding classpath entry 'XXX' to the web app classpath for this 
session
the class will not be on Jettys classpath and is therefore not found by 
spring.

Acording to:
http://google-web-toolkit.googlecode.com/svn/trunk/distro-source/core/src/doc/helpInfo/webAppClassPath.html

You this behaviour is reaching the opposite of what it aims to do:
My application does not run in dev mode but works fine in prod mode if 
deployed to any servlet container.
Of course I could add all the JARs of my modules to WEB-INF/lib but then I 
would need to build all of them for each development cycle I do and
GWT is already slow enough to startup so then I could also go and build and 
deploy my entire WAR for every test I do what makes efficient development 
totally impossible.

So in the end my question is:
Is there some magic way to trigger this
   [WARN] Adding classpath entry 'XXX' to the web app classpath for this 
session
thing by a configuration or so for all my entries of the system classpath?

Thanks a lot
  Jörg

-- 
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/-/Ncp7rB6XQeQJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: How to set and get value of SuggestBox

2012-07-09 Thread Arash
- Create an editor for the type being displayed by suggestBox 
- Wrap a suggestbox inside this editor
- implement LeavValueEditor of the type being edited
- usage in the editor using this suggest box
@UiField
SuggestBoxWrapper type;

- SuggestBoxWrapper.ui.xml




public class SuggestBoxWrapper extends Composite implements 
LeafValueEditor {

private final MultiWordSuggestOracle suggestionOracle = new 
MultiWordSuggestOracle();

private static SuggestBoxWrapperUiBinder uiBinder = 
GWT.create(SuggestBoxWrapperUiBinder.class);

interface SuggestBoxWrapperUiBinder extends UiBinder {
}

public SuggestBoxWrapper() {
initWidget(uiBinder.createAndBindUi(this));
}

@UiField(provided = true)
SuggestBox suggestBox = new SuggestBox(suggestionOracle);


@Override
public void setValue(EnumType enumType) {
String display = (enumType == null) ? "" : enumType.toString();
suggestBox.getTextBox().setText(display);
}

@Override
public EnumType getValue() {
EnumType enumType;

String text = suggestBox.getTextBox().getText();
try {
//convert the input text to your EnumType
enumType = EnumType.fromString(text);

} catch (IllegalArgumentException iaE) {
EnumType = null;
}
return EnumType;
}

public void setValues(Collection values) {
Collection suggestions = new ArrayList();

for (EnumType type : values) {
suggestions.add(type.toString());
}
suggestionOracle.addAll(suggestions);
suggestionOracle.setDefaultSuggestionsFromText(suggestions);
}

}

>
>

-- 
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/-/r1iSh7NsEBUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Re: Google IO 2012 : no GWT session ?

2012-07-09 Thread Ed

>
> The GWT 2.5 release is one of the biggest GWT ever and has many new things 
> in there.  

@Daniel: why?
I hope you can convince me, as I don't share this feeling with you till now.

- Ed

-- 
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/-/9a1pQwiqHwEJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Elemental in GWT 2.5 is what?

2012-07-09 Thread mp31415
I'm trying to make some sense from that Elemental feature. But I'm 
definitely missing something. On 2.5 main page there is a link to a brief 
article about Elemental which really does not add much. GWT team is 
notoriously bad on documentation side and it's not getting any better. Just 
please don't tell me to shut up and use something else. It's impossible to 
see the big picture without some background information, like what was 
missing before, what real purpose of the feature is. It's very nice that we 
can now call some latest API but what about the more trivial stuff that say 
 UiBinder was in charge so far? Or maybe it is not about UI but more about 
better hiding JSO types? Or something totally different at all?

It's not any better with all other features in fact, but right now my gripe 
is about Elemental. 

I looked at the Collide project code. They reference elemental.* packages 
all over the place and elemental classes carry copyright statement from 
2010. So is it new or just recently opened by Google?

I mean we get some random pieces of information from GWT team which I have 
a hard time stitching together.
And I didn't download yet 2.5 RC, as I prefer to understand things first, 
before diving into some low-level details.

Thanks.

-- 
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/-/EHhuWV6M5ZUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.