Re: Is GWT 3.0 /GWT 2.9 dead?

[Craig Mitchell]

>
> *GWT is for large projects.*


GWT is also great for small projects.  I'm using it for a little game I 
made  https://drift.team/  It's brilliant, as I can reuse the game logic 
code, to replay the game on the server, and make sure the person didn't 
hack the game and cheat.  :D

Big thanks to the community for keeping GWT going.  Looking forward to 
GWT3.0!

I do wonder if/when WASM supports garbage collection, then it'd be possible 
to make a good Java to WASM compiler.  GWT would then have some serious 
competition.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/c95ca5da-88e8-4be0-ae12-59af7ef2fc6c%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Luis Fernando Planella Gonzalez]

It is great to know we can use the snapshot with support for Java 11 
already!
Unfortunately, except for the GWT team and those that follow the project 
closely, it looks like GWT is stuck at the 2.8.2 release 2.5 years ago, 
because the GWT official website contains no information on this. Maybe it 
would be good to put some text in the home page pointing to this.
I'm surely much more optimistic now that I know there is an usable updated 
version.
Great work, guys!

Em quinta-feira, 20 de fevereiro de 2020 08:01:43 UTC-3, Ahmad Bawaneh 
escreveu:
>
> And lets not forget that it is not so long since j2cl was made public.
>
> On Thursday, February 20, 2020 at 1:00:33 PM UTC+2, Ahmad Bawaneh wrote:
>>
>> You dont need to maintain a separate branch or code base, you can use the 
>> latest snapshot which is as stable as a release, i am pretty sure when 2.9 
>> is release you will only need to switch version and everything still works, 
>> if you can use the snapshot for some reason you can use the unofficial 
>> release as discussed here 
>> https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion
>>  or 
>> you can fork and release internally.
>>
>> and the community work, we need to know that the active members in the 
>> community is small, that is said we could have made a GWT3.0 a lot earlier, 
>> we could have focused in shipping a working maven plugin for j2cl and call 
>> the day, but most of the efforts is focused in making sure that old apps 
>> will be able to migrate to gwt3.0 without much effort and this part in 
>> specific is very important and very hard and consumes a lot of time, GWT 
>> apps in general are big apps and making GWT3.0 that only works for new apps 
>> only or requires app rewrite does not make any sense.
>>
>> to get more insight on what have been done check this list
>>
>> https://ci.vertispan.com/ 
>>
>> On Wednesday, February 19, 2020 at 3:21:03 PM UTC+2, Luis Fernando 
>> Planella Gonzalez wrote:
>>>
>>> It has always been said that GWT is active when similar questions are 
>>> asked in the forum.
>>> However, given that the last version, 2.8.2, was released on Oct 19, 
>>> 2017 and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I 
>>> can't see it as "active".
>>> At least it smells bad!
>>> Even the 1.0 release of Elemental can't be used, because it requires 
>>> newer components than the pre-packaged version.
>>> It is a sad thing, because I work on a large project using GWT since its 
>>> 1.5.0 version, and our project is actively developed and still evolving.
>>> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 
>>> 11 in the coming months, and it would be a burden to maintain a separated 
>>> Java version only for the frontend part (been there, done that with Java 8).
>>> The fact is that since Google left the project, things are way too slow.
>>> Understandable, as it is based on best effor from the brave developers, 
>>> but still disheartening.
>>> Still, I don't loose hope that GWT will be still maintained.
>>>
>>> Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky 
>>> escreveu:

 Frank - Thanks for the reply, but it would be good to understand the 
 plans to complete the GWT 2.9 release - particularly with reference to 
 Java 
 11 support.  Any insight there?

 On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:
>
> Atm the community is very active. We are working on GWT modules: 
> replacing generators and JSNI, testig the migraed moules against J2CL, 
> etc.
> Besides that, many new frameworks are evolving.
>
> Take a look at this rooms:
> https://gitter.im/gwtproject/gwt
> https://gitter.im/vertispan/j2cl
> https://gitter.im/DominoKit/domino
> to get more infos.
>


-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9bf77f8d-2c11-4d1f-98f2-aa1ca188eb43%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Ahmad Bawaneh]

And lets not forget that it is not so long since j2cl was made public.

On Thursday, February 20, 2020 at 1:00:33 PM UTC+2, Ahmad Bawaneh wrote:
>
> You dont need to maintain a separate branch or code base, you can use the 
> latest snapshot which is as stable as a release, i am pretty sure when 2.9 
> is release you will only need to switch version and everything still works, 
> if you can use the snapshot for some reason you can use the unofficial 
> release as discussed here 
> https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion
>  or 
> you can fork and release internally.
>
> and the community work, we need to know that the active members in the 
> community is small, that is said we could have made a GWT3.0 a lot earlier, 
> we could have focused in shipping a working maven plugin for j2cl and call 
> the day, but most of the efforts is focused in making sure that old apps 
> will be able to migrate to gwt3.0 without much effort and this part in 
> specific is very important and very hard and consumes a lot of time, GWT 
> apps in general are big apps and making GWT3.0 that only works for new apps 
> only or requires app rewrite does not make any sense.
>
> to get more insight on what have been done check this list
>
> https://ci.vertispan.com/ 
>
> On Wednesday, February 19, 2020 at 3:21:03 PM UTC+2, Luis Fernando 
> Planella Gonzalez wrote:
>>
>> It has always been said that GWT is active when similar questions are 
>> asked in the forum.
>> However, given that the last version, 2.8.2, was released on Oct 19, 2017 
>> and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't 
>> see it as "active".
>> At least it smells bad!
>> Even the 1.0 release of Elemental can't be used, because it requires 
>> newer components than the pre-packaged version.
>> It is a sad thing, because I work on a large project using GWT since its 
>> 1.5.0 version, and our project is actively developed and still evolving.
>> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11 
>> in the coming months, and it would be a burden to maintain a separated Java 
>> version only for the frontend part (been there, done that with Java 8).
>> The fact is that since Google left the project, things are way too slow.
>> Understandable, as it is based on best effor from the brave developers, 
>> but still disheartening.
>> Still, I don't loose hope that GWT will be still maintained.
>>
>> Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky 
>> escreveu:
>>>
>>> Frank - Thanks for the reply, but it would be good to understand the 
>>> plans to complete the GWT 2.9 release - particularly with reference to Java 
>>> 11 support.  Any insight there?
>>>
>>> On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:

 Atm the community is very active. We are working on GWT modules: 
 replacing generators and JSNI, testig the migraed moules against J2CL, etc.
 Besides that, many new frameworks are evolving.

 Take a look at this rooms:
 https://gitter.im/gwtproject/gwt
 https://gitter.im/vertispan/j2cl
 https://gitter.im/DominoKit/domino
 to get more infos.

>>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/aeb65c19-7e99-47ab-bee9-12699a90625d%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Ahmad Bawaneh]

You dont need to maintain a separate branch or code base, you can use the 
latest snapshot which is as stable as a release, i am pretty sure when 2.9 
is release you will only need to switch version and everything still works, 
if you can use the snapshot for some reason you can use the unofficial 
release as discussed here 
https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion
 or 
you can fork and release internally.

and the community work, we need to know that the active members in the 
community is small, that is said we could have made a GWT3.0 a lot earlier, 
we could have focused in shipping a working maven plugin for j2cl and call 
the day, but most of the efforts is focused in making sure that old apps 
will be able to migrate to gwt3.0 without much effort and this part in 
specific is very important and very hard and consumes a lot of time, GWT 
apps in general are big apps and making GWT3.0 that only works for new apps 
only or requires app rewrite does not make any sense.

to get more insight on what have been done check this list

https://ci.vertispan.com/ 

On Wednesday, February 19, 2020 at 3:21:03 PM UTC+2, Luis Fernando Planella 
Gonzalez wrote:
>
> It has always been said that GWT is active when similar questions are 
> asked in the forum.
> However, given that the last version, 2.8.2, was released on Oct 19, 2017 
> and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't 
> see it as "active".
> At least it smells bad!
> Even the 1.0 release of Elemental can't be used, because it requires newer 
> components than the pre-packaged version.
> It is a sad thing, because I work on a large project using GWT since its 
> 1.5.0 version, and our project is actively developed and still evolving.
> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11 
> in the coming months, and it would be a burden to maintain a separated Java 
> version only for the frontend part (been there, done that with Java 8).
> The fact is that since Google left the project, things are way too slow.
> Understandable, as it is based on best effor from the brave developers, 
> but still disheartening.
> Still, I don't loose hope that GWT will be still maintained.
>
> Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky 
> escreveu:
>>
>> Frank - Thanks for the reply, but it would be good to understand the 
>> plans to complete the GWT 2.9 release - particularly with reference to Java 
>> 11 support.  Any insight there?
>>
>> On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:
>>>
>>> Atm the community is very active. We are working on GWT modules: 
>>> replacing generators and JSNI, testig the migraed moules against J2CL, etc.
>>> Besides that, many new frameworks are evolving.
>>>
>>> Take a look at this rooms:
>>> https://gitter.im/gwtproject/gwt
>>> https://gitter.im/vertispan/j2cl
>>> https://gitter.im/DominoKit/domino
>>> to get more infos.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/c49cad20-7392-449c-a7cc-cf28016e1b44%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Peter Donald]

On Thu, Feb 20, 2020 at 8:58 AM Jens  wrote:

>
> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11
>> in the coming months, and it would be a burden to maintain a separated Java
>> version only for the frontend part (been there, done that with Java 8).
>>
>
> Java 11 syntax additions are available in GWT snapshot releases:
> https://gwt-review.googlesource.com/c/gwt/+/21540
>

And in an unofficial release in Maven central ;)

https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion

-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc56TbpZfpGTfdF%2BWyn5Pf41d-WZB2nDkkMeZBNRke2baw%40mail.gmail.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Jens]

> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11 
> in the coming months, and it would be a burden to maintain a separated Java 
> version only for the frontend part (been there, done that with Java 8).
>

Java 11 syntax additions are available in GWT snapshot releases: 
https://gwt-review.googlesource.com/c/gwt/+/21540

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/248fd9b1-a33b-4d7e-ae77-ab6c73b1ae3e%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[vitaly goji]

GWT WORKS. I use 2.8 and I don't see reason to upgrade or switch.
GWT is for large projects. You can use your widgets and GWT will provide
structure and tooling.

On Wed, Feb 19, 2020, 5:21 AM Luis Fernando Planella Gonzalez <
lfpg@gmail.com> wrote:

> It has always been said that GWT is active when similar questions are
> asked in the forum.
> However, given that the last version, 2.8.2, was released on Oct 19, 2017
> and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't
> see it as "active".
> At least it smells bad!
> Even the 1.0 release of Elemental can't be used, because it requires newer
> components than the pre-packaged version.
> It is a sad thing, because I work on a large project using GWT since its
> 1.5.0 version, and our project is actively developed and still evolving.
> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11
> in the coming months, and it would be a burden to maintain a separated Java
> version only for the frontend part (been there, done that with Java 8).
> The fact is that since Google left the project, things are way too slow.
> Understandable, as it is based on best effor from the brave developers,
> but still disheartening.
> Still, I don't loose hope that GWT will be still maintained.
>
> Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky
> escreveu:
>>
>> Frank - Thanks for the reply, but it would be good to understand the
>> plans to complete the GWT 2.9 release - particularly with reference to Java
>> 11 support.  Any insight there?
>>
>> On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:
>>>
>>> Atm the community is very active. We are working on GWT modules:
>>> replacing generators and JSNI, testig the migraed moules against J2CL, etc.
>>> Besides that, many new frameworks are evolving.
>>>
>>> Take a look at this rooms:
>>> https://gitter.im/gwtproject/gwt
>>> https://gitter.im/vertispan/j2cl
>>> https://gitter.im/DominoKit/domino
>>> to get more infos.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/498010d4-aca5-4430-8707-c61d15a0cffb%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAOa5rhOoMmSgWLx70dtTOZdoQpGQ_wrEYH68aXUYdkOSfWo3VQ%40mail.gmail.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Luis Fernando Planella Gonzalez]

It has always been said that GWT is active when similar questions are asked 
in the forum.
However, given that the last version, 2.8.2, was released on Oct 19, 2017 
and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't 
see it as "active".
At least it smells bad!
Even the 1.0 release of Elemental can't be used, because it requires newer 
components than the pre-packaged version.
It is a sad thing, because I work on a large project using GWT since its 
1.5.0 version, and our project is actively developed and still evolving.
I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11 
in the coming months, and it would be a burden to maintain a separated Java 
version only for the frontend part (been there, done that with Java 8).
The fact is that since Google left the project, things are way too slow.
Understandable, as it is based on best effor from the brave developers, but 
still disheartening.
Still, I don't loose hope that GWT will be still maintained.

Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky 
escreveu:
>
> Frank - Thanks for the reply, but it would be good to understand the plans 
> to complete the GWT 2.9 release - particularly with reference to Java 11 
> support.  Any insight there?
>
> On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:
>>
>> Atm the community is very active. We are working on GWT modules: 
>> replacing generators and JSNI, testig the migraed moules against J2CL, etc.
>> Besides that, many new frameworks are evolving.
>>
>> Take a look at this rooms:
>> https://gitter.im/gwtproject/gwt
>> https://gitter.im/vertispan/j2cl
>> https://gitter.im/DominoKit/domino
>> to get more infos.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/498010d4-aca5-4430-8707-c61d15a0cffb%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Jeff Zemsky]

Frank - Thanks for the reply, but it would be good to understand the plans 
to complete the GWT 2.9 release - particularly with reference to Java 11 
support.  Any insight there?

On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote:
>
> Atm the community is very active. We are working on GWT modules: replacing 
> generators and JSNI, testig the migraed moules against J2CL, etc.
> Besides that, many new frameworks are evolving.
>
> Take a look at this rooms:
> https://gitter.im/gwtproject/gwt
> https://gitter.im/vertispan/j2cl
> https://gitter.im/DominoKit/domino
> to get more infos.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/61ae1f73-9bdb-4131-9ccc-f27808e44437%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Frank Hossfeld]

Atm the community is very active. We are working on GWT modules: replacing 
generators and JSNI, testig the migraed moules against J2CL, etc.
Besides that, many new frameworks are evolving.

Take a look at this rooms:
https://gitter.im/gwtproject/gwt
https://gitter.im/vertispan/j2cl
https://gitter.im/DominoKit/domino
to get more infos.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/a3ae5c60-6dc7-43f0-b3c9-02a6e6d18bf9%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Frank Hossfeld]

You should ask this question here: https://gitter.im/gwtproject/gwt

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/27aad5bc-85d3-41b1-a642-f9d5e0985b58%40googlegroups.com.

Is GWT 3.0 /GWT 2.9 dead?

[Hrishikesh Joshi]

Since last 6-7 months there is almost no progress on milestone for GWT 
2.9.is is about 62 %.  Is the community still working on these versions or 
there in no plan to work on these to support Java 11 + releases?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f53b16ec-2580-4118-944d-6a8c2f0ff7be%40googlegroups.com.

Re: Is GWT is Dead?

[Pablo Nussembaum]

Google Inbox is 70% GWT code:

https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html

https://news.ycombinator.com/item?id=8554339


On 06/09/16 17:06, Vassilis Virvilis wrote:
> ok then gmail being written in GWT is urban myth.
>
> However looks like google group is written in GWT 
> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ
> <https://groups.google.com/forum/#%21msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ>
>
> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzmatad...@gmail.com 
> <mailto:jazzmatad...@gmail.com>> wrote:
>
> Gmail was created waaayyy before GWT was created.
>
> On 6 September 2016 at 21:31, Vassilis Virvilis <vasv...@gmail.com 
> <mailto:vasv...@gmail.com>> wrote:
>
> About 1) Isn't gmail written in GWT? I think I have read it 
> somewhere...
>
>     About 7) There is GWTcon2016 http://www.gwtcon.org/
>
> GWT doesn't look dead to me - but your questions have valid points.
>
>Vassilis
>
> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.jal...@gmail.com 
> <mailto:ali.jal...@gmail.com>> wrote:
>
> Hi,
>
> I think GWT is not dead, but its development rate is decreased. I 
> think that last public product of Google which written in GWT was Inbox
> 
> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html> which 
> announced in late 2014. But AdWords
> 
> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html> 
> (one of main GWT applications in Google) were re-written by Dart and 
> AngularJS (which announced in March 2016).
>
> There are some good points about GWT which mentioned in this post 
> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html> and some 
> pretty works about 2.8-RC2 release,
> JsInterop, GWTPolymer, GWTMaterial, Angular2Boot, ...
>
> But there are some vague points about GWT:
>
> 1. Which projects in Google written based on GWT in 2015-2016?
> 2. Were there any change in steering committee 
> <http://www.gwtproject.org/steering.html> members (companies) in last two 
> years?
> 3. New GWT compiler (J2CL) when will be released? Is its 
> development started yet?
> 4. Why there is no official Java (GWT) version of Angular2 
> <https://angular.io/docs/ts/latest/quickstart.html> (while there are JS, 
> TypeScript & Dart versions)?
> 5. How many people in Google work in GWT team (compared to Dart & 
> AngularJs teams)?
> 6. What is other companies roadmap about investment & development 
> based on GWT (like Vaadin, Sencha, ...)?
> 7. Is there any planned GWT Con or GWT Create conferences?
>
> I'm developing various applications with GWT for about 8 years 
> and I really enjoy it. It seems GWT development rate is not good enough 
> compared to other Google or Web tools and it makes
> me worried about its future.
>
> Is that correct?
>
> Regards.
>
>
> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres 
> <igna...@bacamt.com <mailto:igna...@bacamt.com>> wrote:
>
> Just curious, what and why are you waiting GWT 3? GWT is 
> pretty awesome right now…
>
> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com 
> <mailto:sameen@gmail.com>> wrote:
>
> Team,
>   My Apologies for asking this question again.
>
> Is GWT is Dead or Alive ? From past 2 years i am waiting 
> for GWT 3.0 but still is not released? Can any one from Steering committee 
> explain whats going on or Any progress on GWT
> 3.0 .   
> -- 
> You received this message because you are subscribed to 
> the Google Groups "GWT Users" group.
> To unsubscribe from this group and stop receiving emails 
> from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com
> <mailto:google-web-toolkit+unsubscr...@googlegroups.com>.
> To post to this group, send email to 
> google-web-toolkit@googlegroups.com 
> <mailto:google-web-toolkit@googlegroups.com>.
> Visit this group at 
> https://groups.google.com/group/google-web-toolkit 
> <https://groups.google.com/group/google-web-toolkit>.
> For more options, visit 
> https://groups.google.com/d/

Re: Is GWT is Dead?

[Gourab Panda]

Back 2010-2011(approx.) when I was using GWT, there were these discussion(*in
My Team*) on why GMAIL is reverting back it implementation from GWT to its
original implementation. Not sure about the authenticity of those news.

Found a link where there is similar discussion about this topic:
https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit

On Fri, Sep 9, 2016 at 3:38 PM, Gourab Panda <goura...@gmail.com> wrote:

> Back 2010-2011(approx.) when I was using GWT, there were these
> discussion(in May) on why GMAIL is reverting back it implementation from
> GWT to its original implementation. Not sure about the authenticity of
> those news.
>
> Found a link where there is similar discussion about this topic:
> https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit
>
> On Thu, Sep 8, 2016 at 3:03 AM, Paul Stockley <pstockl...@gmail.com>
> wrote:
>
>> I think you are getting confused with Goggle Wave.
>>
>> On Wednesday, September 7, 2016 at 5:07:41 AM UTC+1, Gourab wrote:
>>>
>>> >> ok then gmail being written in GWT is urban myth.
>>>
>>> It was rewritten in GWT and later reverted back to it's original
>>> implementation.
>>>
>>> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis <vas...@gmail.com>
>>> wrote:
>>>
>>>> ok then gmail being written in GWT is urban myth.
>>>>
>>>> However looks like google group is written in GWT
>>>> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjj
>>>> k5y9RQbw/hCWzIrZ1vzcJ
>>>>
>>>> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzma...@gmail.com>
>>>> wrote:
>>>>
>>>>> Gmail was created waaayyy before GWT was created.
>>>>>
>>>>> On 6 September 2016 at 21:31, Vassilis Virvilis <vas...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> About 1) Isn't gmail written in GWT? I think I have read it
>>>>>> somewhere...
>>>>>>
>>>>>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>>>>>
>>>>>> GWT doesn't look dead to me - but your questions have valid points.
>>>>>>
>>>>>>Vassilis
>>>>>>
>>>>>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.j...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I think GWT is not dead, but its development rate is decreased. I
>>>>>>> think that last public product of Google which written in GWT was
>>>>>>> Inbox
>>>>>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
>>>>>>> which announced in late 2014. But AdWords
>>>>>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>>>>>> (one of main GWT applications in Google) were re-written by Dart and
>>>>>>> AngularJS (which announced in March 2016).
>>>>>>>
>>>>>>> There are some good points about GWT which mentioned in this post
>>>>>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html>
>>>>>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>>>>>> GWTMaterial, Angular2Boot, ...
>>>>>>>
>>>>>>> But there are some vague points about GWT:
>>>>>>>
>>>>>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>>>>>> 2. Were there any change in steering committee
>>>>>>> <http://www.gwtproject.org/steering.html> members (companies) in
>>>>>>> last two years?
>>>>>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>>>>>> started yet?
>>>>>>> 4. Why there is no official Java (GWT) version of Angular2
>>>>>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there
>>>>>>> are JS, TypeScript & Dart versions)?
>>>>>>> 5. How many people in Google work in GWT team (compared to Dart &
>>>>>>> AngularJs teams)?
>>>>>>> 6. What is other companies roadmap about investment & development
>>>>>>> based on GWT (like Vaadin, Sencha, ...)?
>>>>>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>>>

Re: Is GWT is Dead?

[Gourab Panda]

Back 2010-2011(approx.) when I was using GWT, there were these
discussion(in May) on why GMAIL is reverting back it implementation from
GWT to its original implementation. Not sure about the authenticity of
those news.

Found a link where there is similar discussion about this topic:
https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit

On Thu, Sep 8, 2016 at 3:03 AM, Paul Stockley <pstockl...@gmail.com> wrote:

> I think you are getting confused with Goggle Wave.
>
> On Wednesday, September 7, 2016 at 5:07:41 AM UTC+1, Gourab wrote:
>>
>> >> ok then gmail being written in GWT is urban myth.
>>
>> It was rewritten in GWT and later reverted back to it's original
>> implementation.
>>
>> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis <vas...@gmail.com>
>> wrote:
>>
>>> ok then gmail being written in GWT is urban myth.
>>>
>>> However looks like google group is written in GWT
>>> https://groups.google.com/forum/#!msg/google-web-toolkit/
>>> Mjjk5y9RQbw/hCWzIrZ1vzcJ
>>>
>>> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzma...@gmail.com>
>>> wrote:
>>>
>>>> Gmail was created waaayyy before GWT was created.
>>>>
>>>> On 6 September 2016 at 21:31, Vassilis Virvilis <vas...@gmail.com>
>>>> wrote:
>>>>
>>>>> About 1) Isn't gmail written in GWT? I think I have read it
>>>>> somewhere...
>>>>>
>>>>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>>>>
>>>>> GWT doesn't look dead to me - but your questions have valid points.
>>>>>
>>>>>Vassilis
>>>>>
>>>>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.j...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I think GWT is not dead, but its development rate is decreased. I
>>>>>> think that last public product of Google which written in GWT was
>>>>>> Inbox
>>>>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
>>>>>> which announced in late 2014. But AdWords
>>>>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>>>>> (one of main GWT applications in Google) were re-written by Dart and
>>>>>> AngularJS (which announced in March 2016).
>>>>>>
>>>>>> There are some good points about GWT which mentioned in this post
>>>>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html>
>>>>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>>>>> GWTMaterial, Angular2Boot, ...
>>>>>>
>>>>>> But there are some vague points about GWT:
>>>>>>
>>>>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>>>>> 2. Were there any change in steering committee
>>>>>> <http://www.gwtproject.org/steering.html> members (companies) in
>>>>>> last two years?
>>>>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>>>>> started yet?
>>>>>> 4. Why there is no official Java (GWT) version of Angular2
>>>>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there are
>>>>>> JS, TypeScript & Dart versions)?
>>>>>> 5. How many people in Google work in GWT team (compared to Dart &
>>>>>> AngularJs teams)?
>>>>>> 6. What is other companies roadmap about investment & development
>>>>>> based on GWT (like Vaadin, Sencha, ...)?
>>>>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>>>>
>>>>>> I'm developing various applications with GWT for about 8 years and I
>>>>>> really enjoy it. It seems GWT development rate is not good enough 
>>>>>> compared
>>>>>> to other Google or Web tools and it makes me worried about its future.
>>>>>>
>>>>>> Is that correct?
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>>>>> ign...@bacamt.com> wrote:
>>>>>>
>>>>>>> Just curious, what and why are you waiting GWT 3? GWT is pretty
&

Re: Is GWT is Dead?

[Paul Stockley]

I think you are getting confused with Goggle Wave.

On Wednesday, September 7, 2016 at 5:07:41 AM UTC+1, Gourab wrote:
>
> >> ok then gmail being written in GWT is urban myth.
>
> It was rewritten in GWT and later reverted back to it's original 
> implementation. 
>
> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis <vas...@gmail.com 
> > wrote:
>
>> ok then gmail being written in GWT is urban myth.
>>
>> However looks like google group is written in GWT 
>> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ
>>
>> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzma...@gmail.com 
>> > wrote:
>>
>>> Gmail was created waaayyy before GWT was created.
>>>
>>> On 6 September 2016 at 21:31, Vassilis Virvilis <vas...@gmail.com 
>>> > wrote:
>>>
>>>> About 1) Isn't gmail written in GWT? I think I have read it somewhere...
>>>>
>>>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>>>
>>>> GWT doesn't look dead to me - but your questions have valid points.
>>>>
>>>>Vassilis
>>>>
>>>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.j...@gmail.com 
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I think GWT is not dead, but its development rate is decreased. I 
>>>>> think that last public product of Google which written in GWT was 
>>>>> Inbox 
>>>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html> 
>>>>> which announced in late 2014. But AdWords 
>>>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>>>>  
>>>>> (one of main GWT applications in Google) were re-written by Dart and 
>>>>> AngularJS (which announced in March 2016).
>>>>>
>>>>> There are some good points about GWT which mentioned in this post 
>>>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html> 
>>>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer, 
>>>>> GWTMaterial, Angular2Boot, ...
>>>>>
>>>>> But there are some vague points about GWT:
>>>>>
>>>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>>>> 2. Were there any change in steering committee 
>>>>> <http://www.gwtproject.org/steering.html> members (companies) in last 
>>>>> two years?
>>>>> 3. New GWT compiler (J2CL) when will be released? Is its development 
>>>>> started yet?
>>>>> 4. Why there is no official Java (GWT) version of Angular2 
>>>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there are 
>>>>> JS, TypeScript & Dart versions)?
>>>>> 5. How many people in Google work in GWT team (compared to Dart & 
>>>>> AngularJs teams)?
>>>>> 6. What is other companies roadmap about investment & development 
>>>>> based on GWT (like Vaadin, Sencha, ...)?
>>>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>>>
>>>>> I'm developing various applications with GWT for about 8 years and I 
>>>>> really enjoy it. It seems GWT development rate is not good enough 
>>>>> compared 
>>>>> to other Google or Web tools and it makes me worried about its future.
>>>>>
>>>>> Is that correct?
>>>>>
>>>>> Regards.
>>>>>
>>>>>
>>>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>>>> ign...@bacamt.com > wrote:
>>>>>
>>>>>> Just curious, what and why are you waiting GWT 3? GWT is pretty 
>>>>>> awesome right now…
>>>>>>
>>>>>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <samee...@gmail.com 
>>>>>> > wrote:
>>>>>>
>>>>>>> Team,
>>>>>>>   My Apologies for asking this question again.
>>>>>>>
>>>>>>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0 
>>>>>>> but still is not released? Can any one from Steering committee explain 
>>>>>>> whats going on or Any progress on GWT 3.0 .   
>>>>>>>
>>>>>>> -- 
>>>>>>&

Re: Is GWT is Dead?

[Thomas Broyer]

On Wednesday, September 7, 2016 at 6:07:41 AM UTC+2, Gourab wrote:
>
> >> ok then gmail being written in GWT is urban myth.
>
> It was rewritten in GWT and later reverted back to it's original 
> implementation.
>

I think it's the first time I hear about this. Any source to back this 
claim? 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Vassilis Virvilis]

Oooh techno gossip fuel!!!

 Any idea why?

On Wed, Sep 7, 2016 at 7:07 AM, Gourab Panda <goura...@gmail.com> wrote:

> >> ok then gmail being written in GWT is urban myth.
>
> It was rewritten in GWT and later reverted back to it's original
> implementation.
>
> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis <vasv...@gmail.com>
> wrote:
>
>> ok then gmail being written in GWT is urban myth.
>>
>> However looks like google group is written in GWT
>> https://groups.google.com/forum/#!msg/google-web-toolkit/
>> Mjjk5y9RQbw/hCWzIrZ1vzcJ
>>
>> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzmatad...@gmail.com>
>> wrote:
>>
>>> Gmail was created waaayyy before GWT was created.
>>>
>>> On 6 September 2016 at 21:31, Vassilis Virvilis <vasv...@gmail.com>
>>> wrote:
>>>
>>>> About 1) Isn't gmail written in GWT? I think I have read it somewhere...
>>>>
>>>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>>>
>>>> GWT doesn't look dead to me - but your questions have valid points.
>>>>
>>>>Vassilis
>>>>
>>>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.jal...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I think GWT is not dead, but its development rate is decreased. I
>>>>> think that last public product of Google which written in GWT was
>>>>> Inbox
>>>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
>>>>> which announced in late 2014. But AdWords
>>>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>>>> (one of main GWT applications in Google) were re-written by Dart and
>>>>> AngularJS (which announced in March 2016).
>>>>>
>>>>> There are some good points about GWT which mentioned in this post
>>>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html>
>>>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>>>> GWTMaterial, Angular2Boot, ...
>>>>>
>>>>> But there are some vague points about GWT:
>>>>>
>>>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>>>> 2. Were there any change in steering committee
>>>>> <http://www.gwtproject.org/steering.html> members (companies) in last
>>>>> two years?
>>>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>>>> started yet?
>>>>> 4. Why there is no official Java (GWT) version of Angular2
>>>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there are
>>>>> JS, TypeScript & Dart versions)?
>>>>> 5. How many people in Google work in GWT team (compared to Dart &
>>>>> AngularJs teams)?
>>>>> 6. What is other companies roadmap about investment & development
>>>>> based on GWT (like Vaadin, Sencha, ...)?
>>>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>>>
>>>>> I'm developing various applications with GWT for about 8 years and I
>>>>> really enjoy it. It seems GWT development rate is not good enough compared
>>>>> to other Google or Web tools and it makes me worried about its future.
>>>>>
>>>>> Is that correct?
>>>>>
>>>>> Regards.
>>>>>
>>>>>
>>>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>>>> igna...@bacamt.com> wrote:
>>>>>
>>>>>> Just curious, what and why are you waiting GWT 3? GWT is pretty
>>>>>> awesome right now…
>>>>>>
>>>>>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:
>>>>>>
>>>>>>> Team,
>>>>>>>   My Apologies for asking this question again.
>>>>>>>
>>>>>>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0
>>>>>>> but still is not released? Can any one from Steering committee explain
>>>>>>> whats going on or Any progress on GWT 3.0 .
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups &

Re: Is GWT is Dead?

[Gourab Panda]

>> ok then gmail being written in GWT is urban myth.

It was rewritten in GWT and later reverted back to it's original
implementation.

On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis <vasv...@gmail.com> wrote:

> ok then gmail being written in GWT is urban myth.
>
> However looks like google group is written in GWT
> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/
> hCWzIrZ1vzcJ
>
> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzmatad...@gmail.com>
> wrote:
>
>> Gmail was created waaayyy before GWT was created.
>>
>> On 6 September 2016 at 21:31, Vassilis Virvilis <vasv...@gmail.com>
>> wrote:
>>
>>> About 1) Isn't gmail written in GWT? I think I have read it somewhere...
>>>
>>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>>
>>> GWT doesn't look dead to me - but your questions have valid points.
>>>
>>>Vassilis
>>>
>>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.jal...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I think GWT is not dead, but its development rate is decreased. I think
>>>> that last public product of Google which written in GWT was Inbox
>>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
>>>> which announced in late 2014. But AdWords
>>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>>> (one of main GWT applications in Google) were re-written by Dart and
>>>> AngularJS (which announced in March 2016).
>>>>
>>>> There are some good points about GWT which mentioned in this post
>>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html>
>>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>>> GWTMaterial, Angular2Boot, ...
>>>>
>>>> But there are some vague points about GWT:
>>>>
>>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>>> 2. Were there any change in steering committee
>>>> <http://www.gwtproject.org/steering.html> members (companies) in last
>>>> two years?
>>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>>> started yet?
>>>> 4. Why there is no official Java (GWT) version of Angular2
>>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there are
>>>> JS, TypeScript & Dart versions)?
>>>> 5. How many people in Google work in GWT team (compared to Dart &
>>>> AngularJs teams)?
>>>> 6. What is other companies roadmap about investment & development based
>>>> on GWT (like Vaadin, Sencha, ...)?
>>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>>
>>>> I'm developing various applications with GWT for about 8 years and I
>>>> really enjoy it. It seems GWT development rate is not good enough compared
>>>> to other Google or Web tools and it makes me worried about its future.
>>>>
>>>> Is that correct?
>>>>
>>>> Regards.
>>>>
>>>>
>>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>>> igna...@bacamt.com> wrote:
>>>>
>>>>> Just curious, what and why are you waiting GWT 3? GWT is pretty
>>>>> awesome right now…
>>>>>
>>>>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:
>>>>>
>>>>>> Team,
>>>>>>   My Apologies for asking this question again.
>>>>>>
>>>>>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0
>>>>>> but still is not released? Can any one from Steering committee explain
>>>>>> whats going on or Any progress on GWT 3.0 .
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "GWT Users" 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@googlegroup
>>>>>> s.com.
>>>>>> Visit this group at https://groups.google.com/grou
>>>>>> p/google-web-toolkit.
>>>>>> For more options, visit https:/

Re: Is GWT is Dead?

[harshyadav]

Google Groups is indeed in GWT (or most parts of it, just inspecting the 
HTML structure would tell you that)
Evernote
Parts of Google Inbox
Most of AWS services
Google ADX (they created a new UI last year using GWT)
and hundreds and thousands of more (including my current projects and 
future ventures).

On Tuesday, September 6, 2016 at 6:26:14 PM UTC-4, Kirill Prazdnikov wrote:
>
> I dont think that the Groups in built by GWT 2.8. It might be some kind of 
> internal release or using a private linker. 
> For example, The Groups-JS does not have var $gwt_version. Also there are 
> some other differences in the script structure.
>
> On Tuesday, September 6, 2016 at 11:09:37 PM UTC+3, Vassilis Virvilis 
> wrote:
>>
>> However looks like google group is written in GWT 
>> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Kirill Prazdnikov]

I dont think that the Groups in built by GWT 2.8. It might be some kind of 
internal release or using a private linker. 
For example, The Groups-JS does not have var $gwt_version. Also there are 
some other differences in the script structure.

On Tuesday, September 6, 2016 at 11:09:37 PM UTC+3, Vassilis Virvilis wrote:
>
> However looks like google group is written in GWT 
> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Vassilis Virvilis]

ok then gmail being written in GWT is urban myth.

However looks like google group is written in GWT
https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ

On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi <jazzmatad...@gmail.com>
wrote:

> Gmail was created waaayyy before GWT was created.
>
> On 6 September 2016 at 21:31, Vassilis Virvilis <vasv...@gmail.com> wrote:
>
>> About 1) Isn't gmail written in GWT? I think I have read it somewhere...
>>
>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>
>> GWT doesn't look dead to me - but your questions have valid points.
>>
>>Vassilis
>>
>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.jal...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I think GWT is not dead, but its development rate is decreased. I think
>>> that last public product of Google which written in GWT was Inbox
>>> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
>>> which announced in late 2014. But AdWords
>>> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
>>> (one of main GWT applications in Google) were re-written by Dart and
>>> AngularJS (which announced in March 2016).
>>>
>>> There are some good points about GWT which mentioned in this post
>>> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html> and
>>> some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>> GWTMaterial, Angular2Boot, ...
>>>
>>> But there are some vague points about GWT:
>>>
>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>> 2. Were there any change in steering committee
>>> <http://www.gwtproject.org/steering.html> members (companies) in last
>>> two years?
>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>> started yet?
>>> 4. Why there is no official Java (GWT) version of Angular2
>>> <https://angular.io/docs/ts/latest/quickstart.html> (while there are
>>> JS, TypeScript & Dart versions)?
>>> 5. How many people in Google work in GWT team (compared to Dart &
>>> AngularJs teams)?
>>> 6. What is other companies roadmap about investment & development based
>>> on GWT (like Vaadin, Sencha, ...)?
>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>
>>> I'm developing various applications with GWT for about 8 years and I
>>> really enjoy it. It seems GWT development rate is not good enough compared
>>> to other Google or Web tools and it makes me worried about its future.
>>>
>>> Is that correct?
>>>
>>> Regards.
>>>
>>>
>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>> igna...@bacamt.com> wrote:
>>>
>>>> Just curious, what and why are you waiting GWT 3? GWT is pretty awesome
>>>> right now…
>>>>
>>>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:
>>>>
>>>>> Team,
>>>>>   My Apologies for asking this question again.
>>>>>
>>>>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0
>>>>> but still is not released? Can any one from Steering committee explain
>>>>> whats going on or Any progress on GWT 3.0 .
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "GWT Users" 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@googlegroup
>>>>> s.com.
>>>>> Visit this group at https://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 "GWT Users" 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@googlegroup
>>>> s.com.
>>>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>>>> For mo

Re: Is GWT is Dead?

[Vassilis Virvilis]

About 1) Isn't gmail written in GWT? I think I have read it somewhere...

About 7) There is GWTcon2016 http://www.gwtcon.org/

GWT doesn't look dead to me - but your questions have valid points.

   Vassilis

On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal <ali.jal...@gmail.com> wrote:

> Hi,
>
> I think GWT is not dead, but its development rate is decreased. I think
> that last public product of Google which written in GWT was Inbox
> <https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html>
> which announced in late 2014. But AdWords
> <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
> (one of main GWT applications in Google) were re-written by Dart and
> AngularJS (which announced in March 2016).
>
> There are some good points about GWT which mentioned in this post
> <http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html> and
> some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
> GWTMaterial, Angular2Boot, ...
>
> But there are some vague points about GWT:
>
> 1. Which projects in Google written based on GWT in 2015-2016?
> 2. Were there any change in steering committee
> <http://www.gwtproject.org/steering.html> members (companies) in last two
> years?
> 3. New GWT compiler (J2CL) when will be released? Is its development
> started yet?
> 4. Why there is no official Java (GWT) version of Angular2
> <https://angular.io/docs/ts/latest/quickstart.html> (while there are JS,
> TypeScript & Dart versions)?
> 5. How many people in Google work in GWT team (compared to Dart &
> AngularJs teams)?
> 6. What is other companies roadmap about investment & development based on
> GWT (like Vaadin, Sencha, ...)?
> 7. Is there any planned GWT Con or GWT Create conferences?
>
> I'm developing various applications with GWT for about 8 years and I
> really enjoy it. It seems GWT development rate is not good enough compared
> to other Google or Web tools and it makes me worried about its future.
>
> Is that correct?
>
> Regards.
>
>
> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
> igna...@bacamt.com> wrote:
>
>> Just curious, what and why are you waiting GWT 3? GWT is pretty awesome
>> right now…
>>
>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:
>>
>>> Team,
>>>   My Apologies for asking this question again.
>>>
>>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0 but
>>> still is not released? Can any one from Steering committee explain whats
>>> going on or Any progress on GWT 3.0 .
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Users" 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 https://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
>> "GWT Users" 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 https://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
> "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vassilis Virvilis

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Ali Jalal]

Hi,

I think GWT is not dead, but its development rate is decreased. I think
that last public product of Google which written in GWT was Inbox
<https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html> which
announced in late 2014. But AdWords
<http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>
(one of main GWT applications in Google) were re-written by Dart and
AngularJS (which announced in March 2016).

There are some good points about GWT which mentioned in this post
<http://blog.lteconsulting.fr/gwt/2016/2016/04/10/gwt-2016-en.html> and
some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
GWTMaterial, Angular2Boot, ...

But there are some vague points about GWT:

1. Which projects in Google written based on GWT in 2015-2016?
2. Were there any change in steering committee
<http://www.gwtproject.org/steering.html> members (companies) in last two
years?
3. New GWT compiler (J2CL) when will be released? Is its development
started yet?
4. Why there is no official Java (GWT) version of Angular2
<https://angular.io/docs/ts/latest/quickstart.html> (while there are JS,
TypeScript & Dart versions)?
5. How many people in Google work in GWT team (compared to Dart & AngularJs
teams)?
6. What is other companies roadmap about investment & development based on
GWT (like Vaadin, Sencha, ...)?
7. Is there any planned GWT Con or GWT Create conferences?

I'm developing various applications with GWT for about 8 years and I really
enjoy it. It seems GWT development rate is not good enough compared to
other Google or Web tools and it makes me worried about its future.

Is that correct?

Regards.


On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> Just curious, what and why are you waiting GWT 3? GWT is pretty awesome
> right now…
>
> On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:
>
>> Team,
>>   My Apologies for asking this question again.
>>
>> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0 but
>> still is not released? Can any one from Steering committee explain whats
>> going on or Any progress on GWT 3.0 .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Users" 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 https://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
> "GWT Users" 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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Ignacio Baca Moreno-Torres]

Just curious, what and why are you waiting GWT 3? GWT is pretty awesome
right now…

On Tue, Sep 6, 2016 at 8:39 AM Ahamed <sameen@gmail.com> wrote:

> Team,
>   My Apologies for asking this question again.
>
> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0 but
> still is not released? Can any one from Steering committee explain whats
> going on or Any progress on GWT 3.0 .
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" 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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Is GWT is Dead?

[Ahamed]

Team,
  My Apologies for asking this question again.

Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT 3.0 but 
still is not released? Can any one from Steering committee explain whats 
going on or Any progress on GWT 3.0 .   

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Are the GWT APIs dead?

[Sebastián Gurin]

Hi, I'm working on a Google's Java API for GWT that works 100% on the 
client side : 

http://code.google.com/p/gwtgapi/

example gallery with sources: http://cancerbero.freevar.com/gwtgapi/

(you must authorize the APIs in the Google APIs console, an authorize 
button appears at the bottom)

It is based on the JavaScript project 
http://code.google.com/p/google-api-javascript-client which is 100% 
GWT-wrapped (using overlay types). Also supported some Java utilities for 
easy authentication and module loading. 

Now the big task : I'm writing more Java friendly API (extending 
JavaScriptObject), some google modules are ready but there is a lot of 
work (I'm only working on those who interest me more)

I didn't announce this project here before because I wanted a better 
product before. But perhaps announce it here can be good, mainly for 
completing the mechanical big work that needs to be done, this is, writing 
the Java GWT overlay types for google APIs requests and return types from 
reading the google apis reference documents. 

Any feedback and help is most appreciated. 

On Sunday, January 20, 2013 12:38:24 PM UTC-2, Charles Youakim wrote:

 I'm looking at the project and there's nearly zero activity.  The last 
 chatter was about Maps v3, and that was 9 months ago.

 https://groups.google.com/forum/?fromgroups#!forum/GWT-Google-Apis

 Should I be worried?


-- 
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/-/HAyH4Y-CrugJ.
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.

Are the GWT APIs dead?

[Charles Youakim]

I'm looking at the project and there's nearly zero activity.  The last 
chatter was about Maps v3, and that was 9 months ago.

https://groups.google.com/forum/?fromgroups#!forum/GWT-Google-Apis

Should I be worried?

-- 
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/-/tJO1Rg7DkX8J.
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: Are the GWT APIs dead?

[Alain Ekambi]

This is opensource.
How about getting your hands dirty ? :)


2013/1/20 Charles Youakim charlie.youa...@passportparking.com

 I'm looking at the project and there's nearly zero activity.  The last
 chatter was about Maps v3, and that was 9 months ago.

 https://groups.google.com/forum/?fromgroups#!forum/GWT-Google-Apis

 Should I be worried?

 --
 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/-/tJO1Rg7DkX8J.
 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: Are the GWT APIs dead?

[Charles Youakim]

Are folks out there just wrapping js libs with JSNI and going from there? 
 It seems very plausible.  

You don't really need a GWT API's library when you can easily wrap objects. 

I'm really just wondering what others out there are doing?  Are you 
wrapping js libs such as google maps?

On Sunday, January 20, 2013 3:51:50 PM UTC-5, nino wrote:

 This is opensource.
 How about getting your hands dirty ? :)


 2013/1/20 Charles Youakim charlie...@passportparking.com javascript:

 I'm looking at the project and there's nearly zero activity.  The last 
 chatter was about Maps v3, and that was 9 months ago.

 https://groups.google.com/forum/?fromgroups#!forum/GWT-Google-Apis

 Should I be worried?
  
 -- 
 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/-/tJO1Rg7DkX8J.
 To post to this group, send email to 
 google-we...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 google-web-toolkit+unsubscr...@googlegroups.com javascript:.
 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/-/L1KlOx8jfGAJ.
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: Are the GWT APIs dead?

[Thomas Broyer]

On Monday, January 21, 2013 5:58:48 AM UTC+1, Charles Youakim wrote:

 Are folks out there just wrapping js libs with JSNI and going from there? 
  It seems very plausible.  

 You don't really need a GWT API's library when you can easily wrap 
 objects. 

 I'm really just wondering what others out there are doing?  Are you 
 wrapping js libs such as google maps?


For maps, I believe many people use 
https://github.com/branflake2267/GWT-Maps-V3-Api

-- 
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/-/W0alCGAz_FEJ.
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: [gwt-contrib] Re: GWT 2.0 dead in IE7?

[Stuart Moffatt]

@jgw,

Thanks for the rescue. I thought I was going crazy. Totally forgot about the
effects of doctype.

Nice to have: when the eclipse project wizard (or the app creator tool) is
updated to create a UiBinder-style Greeting template, it would be nice if
the doctype in the template html page was switched to standards-mode. Less
heart attacks for sleepy coders ;)

sfm


On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:

 [duplicating my last message because it failed to post to groups/gwt last
 time]


 On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:

 The problem here is that you're using RootLayoutPanel explicitly, which
 requires the use of a standards-mode doctype.

  * This widget will emonly/em work in standards mode, which requires
 that
  * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
  * declaration.

 The good news is that these days you can just throw a !DOCTYPE html
 declaration at the top of the page to get there -- no need to dig through
 the 37 different versions of [x]html doctypes. IE is particularly strange in
 quirks mode, which is why you're seeing such a large difference.

 Hope that helps,
 joel.

 On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

 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.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.




  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors


--

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-tool...@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: GWT 2.0 dead in IE7?

[adrian.hauptm...@googlemail.com]

Hi there,

exact same issue for me with SplitLayoutPanel!

public class Test implements EntryPoint {
public void onModuleLoad() {
SplitLayoutPanel p = new SplitLayoutPanel();
p.setSize(100%, 100%);
p.addWest(new Label(west), 300);
p.addEast(new Label(east), 300);
p.add(new Label(content));
RootLayoutPanel.get().add(p);   // does not work in IE 7 or 8!
}
}


We must be missing something here...
Adrian


On Dec 10, 3:36 am, Stuart stuartmoff...@gmail.com wrote:
 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 
 (seehttp://groups.google.com/group/google-web-toolkit/browse_thread/threa...)

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

         private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
         interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

         @UiField Button button;
         @UiField HTMLPanel htmlPanel;

         public void onModuleLoad() {

                 Widget w = uiBinder.createAndBindUi(this);
                 RootLayoutPanel root = RootLayoutPanel.get();
                 root.add(w);
         }

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
         xmlns:g=urn:import:com.google.gwt.user.client.ui
         ui:style
                 .important {
                         font-weight: bold;
                 }
         /ui:style
         g:HTMLPanel ui:field=htmlPanel
                 Hello,
                 g:Button styleName={style.important} 
 ui:field=buttonUser/
 g:Button
         /g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine 
 sandbox:http://uibindertestforie.latest.emcode-dev.appspot.comand tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

--

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-tool...@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: GWT 2.0 dead in IE7?

[Joel Webber]

[duplicating my last message because it failed to post to groups/gwt last
time]

On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:

 The problem here is that you're using RootLayoutPanel explicitly, which
 requires the use of a standards-mode doctype.

  * This widget will emonly/em work in standards mode, which requires
 that
  * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
  * declaration.

 The good news is that these days you can just throw a !DOCTYPE html
 declaration at the top of the page to get there -- no need to dig through
 the 37 different versions of [x]html doctypes. IE is particularly strange in
 quirks mode, which is why you're seeing such a large difference.

 Hope that helps,
 joel.

 On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

 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-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@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-tool...@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-contrib] Re: GWT 2.0 dead in IE7?

[Joel Webber]

The problem here is that you're using RootLayoutPanel explicitly, which
requires the use of a standards-mode doctype.

 * This widget will emonly/em work in standards mode, which requires
that
 * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
 * declaration.

The good news is that these days you can just throw a !DOCTYPE html
declaration at the top of the page to get there -- no need to dig through
the 37 different versions of [x]html doctypes. IE is particularly strange in
quirks mode, which is why you're seeing such a large difference.

Hope that helps,
joel.

On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

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




-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: GWT 2.0 dead in IE7?

[Joel Webber]

[duplicating my last message because it failed to post to groups/gwt last
time]

On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:

 The problem here is that you're using RootLayoutPanel explicitly, which
 requires the use of a standards-mode doctype.

  * This widget will emonly/em work in standards mode, which requires
 that
  * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
  * declaration.

 The good news is that these days you can just throw a !DOCTYPE html
 declaration at the top of the page to get there -- no need to dig through
 the 37 different versions of [x]html doctypes. IE is particularly strange in
 quirks mode, which is why you're seeing such a large difference.

 Hope that helps,
 joel.

 On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

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





-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?

[Stuart Moffatt]

@jgw,

Thanks for the rescue. I thought I was going crazy. Totally forgot about the
effects of doctype.

Nice to have: when the eclipse project wizard (or the app creator tool) is
updated to create a UiBinder-style Greeting template, it would be nice if
the doctype in the template html page was switched to standards-mode. Less
heart attacks for sleepy coders ;)

sfm


On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:

 [duplicating my last message because it failed to post to groups/gwt last
 time]


 On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:

 The problem here is that you're using RootLayoutPanel explicitly, which
 requires the use of a standards-mode doctype.

  * This widget will emonly/em work in standards mode, which requires
 that
  * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
  * declaration.

 The good news is that these days you can just throw a !DOCTYPE html
 declaration at the top of the page to get there -- no need to dig through
 the 37 different versions of [x]html doctypes. IE is particularly strange in
 quirks mode, which is why you're seeing such a large difference.

 Hope that helps,
 joel.

 On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

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




  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: GWT 2.0 dead in IE7?

[Stuart Moffatt]

Logged as issue 4331

http://code.google.com/p/google-web-toolkit/issues/detail?id=4331

On Dec 10, 9:54 am, Stuart Moffatt stuartmoff...@gmail.com wrote:
 @jgw,

 Thanks for the rescue. I thought I was going crazy. Totally forgot about the
 effects of doctype.

 Nice to have: when the eclipse project wizard (or the app creator tool) is
 updated to create a UiBinder-style Greeting template, it would be nice if
 the doctype in the template html page was switched to standards-mode. Less
 heart attacks for sleepy coders ;)

 sfm



 On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:
  [duplicating my last message because it failed to post to groups/gwt last
  time]

  On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:

  The problem here is that you're using RootLayoutPanel explicitly, which
  requires the use of a standards-mode doctype.

   * This widget will emonly/em work in standards mode, which requires
  that
   * the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
   * declaration.

  The good news is that these days you can just throw a !DOCTYPE html
  declaration at the top of the page to get there -- no need to dig through
  the 37 different versions of [x]html doctypes. IE is particularly strange 
  in
  quirks mode, which is why you're seeing such a large difference.

  Hope that helps,
  joel.

  On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com wrote:

  @bruce, @jwg, @rjrjr

  (and any other gwt'ers listening)

  I just posted about a fairly severe show-stopper for my application
  (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
  )

  I thought it was likely due to my code. So I built a dead simple
  EntryPoint using the UiBinder wizard with a few touch ups:

  import com.google.gwt.core.client.EntryPoint;
  import com.google.gwt.core.client.GWT;
  import com.google.gwt.uibinder.client.UiBinder;
  import com.google.gwt.uibinder.client.UiField;
  import com.google.gwt.user.client.ui.Button;
  import com.google.gwt.user.client.ui.HTMLPanel;
  import com.google.gwt.user.client.ui.RootLayoutPanel;
  import com.google.gwt.user.client.ui.Widget;

  public class UiBinderTestForIE implements EntryPoint {

         private static UiBinderTestForIEBinder uiBinder = GWT.create
  (UiBinderTestForIEBinder.class);
         interface UiBinderTestForIEBinder extends UiBinderWidget,
  UiBinderTestForIE {}

        �...@uifield Button button;
        �...@uifield HTMLPanel htmlPanel;

         public void onModuleLoad() {

                 Widget w = uiBinder.createAndBindUi(this);
                 RootLayoutPanel root = RootLayoutPanel.get();
                 root.add(w);
         }

  }

  And here is the ui.xml

  !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
  ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
         xmlns:g=urn:import:com.google.gwt.user.client.ui
         ui:style
                 .important {
                         font-weight: bold;
                 }
         /ui:style
         g:HTMLPanel ui:field=htmlPanel
                 Hello,
                 g:Button styleName={style.important}
  ui:field=buttonUser/
  g:Button
         /g:HTMLPanel
  /ui:UiBinder

  When I launch this in Chrome / FF, I get what I expect. When launched
  in IE7, there is nothing on the page. Yet, the console reports that
  the module has been loaded.

  At first I thought it was a problem with the developer plugin in IE,
  so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.comand tested from
  two different machines. Works in FF/Chrome on both machines. Nothing
  in IE7 on either machine.

  What's the deal?

  Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
  can't actually believe it, so someone please tell me what I am doing
  wrong.

  Stuart

  [cross-posting to gwt, gwt-contrib]

  --

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

   --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?

[Ray Ryan]

Joel, shouldn't we put an assert to that effect somewhere in
RootLayoutPanel? Perhaps even something more garrish, tied to asserts being
enabled: replace its body with text saying This panel will only work in
standards mode, set your doctype like so: !DOCTYPE html 

On Fri, Dec 11, 2009 at 2:35 AM, Stuart Moffatt stuartmoff...@gmail.comwrote:

 Logged as issue 4331

 http://code.google.com/p/google-web-toolkit/issues/detail?id=4331

 On Dec 10, 9:54 am, Stuart Moffatt stuartmoff...@gmail.com wrote:
  @jgw,
 
  Thanks for the rescue. I thought I was going crazy. Totally forgot about
 the
  effects of doctype.
 
  Nice to have: when the eclipse project wizard (or the app creator tool)
 is
  updated to create a UiBinder-style Greeting template, it would be nice if
  the doctype in the template html page was switched to standards-mode.
 Less
  heart attacks for sleepy coders ;)
 
  sfm
 
 
 
  On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:
   [duplicating my last message because it failed to post to groups/gwt
 last
   time]
 
   On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:
 
   The problem here is that you're using RootLayoutPanel explicitly,
 which
   requires the use of a standards-mode doctype.
 
* This widget will emonly/em work in standards mode, which
 requires
   that
* the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
* declaration.
 
   The good news is that these days you can just throw a !DOCTYPE html
   declaration at the top of the page to get there -- no need to dig
 through
   the 37 different versions of [x]html doctypes. IE is particularly
 strange in
   quirks mode, which is why you're seeing such a large difference.
 
   Hope that helps,
   joel.
 
   On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com
 wrote:
 
   @bruce, @jwg, @rjrjr
 
   (and any other gwt'ers listening)
 
   I just posted about a fairly severe show-stopper for my application
   (that is, the app doesn't even finish onModuleLoad() in IE7 (see
 
  
 http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
   )
 
   I thought it was likely due to my code. So I built a dead simple
   EntryPoint using the UiBinder wizard with a few touch ups:
 
   import com.google.gwt.core.client.EntryPoint;
   import com.google.gwt.core.client.GWT;
   import com.google.gwt.uibinder.client.UiBinder;
   import com.google.gwt.uibinder.client.UiField;
   import com.google.gwt.user.client.ui.Button;
   import com.google.gwt.user.client.ui.HTMLPanel;
   import com.google.gwt.user.client.ui.RootLayoutPanel;
   import com.google.gwt.user.client.ui.Widget;
 
   public class UiBinderTestForIE implements EntryPoint {
 
  private static UiBinderTestForIEBinder uiBinder = GWT.create
   (UiBinderTestForIEBinder.class);
  interface UiBinderTestForIEBinder extends UiBinderWidget,
   UiBinderTestForIE {}
 
  @UiField Button button;
  @UiField HTMLPanel htmlPanel;
 
  public void onModuleLoad() {
 
  Widget w = uiBinder.createAndBindUi(this);
  RootLayoutPanel root = RootLayoutPanel.get();
  root.add(w);
  }
 
   }
 
   And here is the ui.xml
 
   !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent
 
   ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
  xmlns:g=urn:import:com.google.gwt.user.client.ui
  ui:style
  .important {
  font-weight: bold;
  }
  /ui:style
  g:HTMLPanel ui:field=htmlPanel
  Hello,
  g:Button styleName={style.important}
   ui:field=buttonUser/
   g:Button
  /g:HTMLPanel
   /ui:UiBinder
 
   When I launch this in Chrome / FF, I get what I expect. When launched
   in IE7, there is nothing on the page. Yet, the console reports that
   the module has been loaded.
 
   At first I thought it was a problem with the developer plugin in IE,
   so I compiled it and put it up on my App Engine sandbox:
  http://uibindertestforie.latest.emcode-dev.appspot.comand tested from
   two different machines. Works in FF/Chrome on both machines. Nothing
   in IE7 on either machine.
 
   What's the deal?
 
   Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
   can't actually believe it, so someone please tell me what I am doing
   wrong.
 
   Stuart
 
   [cross-posting to gwt, gwt-contrib]
 
   --
 
   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-tool...@googlegroups.com
   .
   To unsubscribe from this group, send email to
   google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs
 cr...@googlegroups.com
   .
   For more options, visit this group at
  http://groups.google.com/group/google-web-toolkit?hl=en.
 
--
  http

Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?

[Joel Webber]

Lex's idea as well. I'll do that.

On Thu, Dec 10, 2009 at 2:39 PM, Ray Ryan rj...@google.com wrote:

 Joel, shouldn't we put an assert to that effect somewhere in
 RootLayoutPanel? Perhaps even something more garrish, tied to asserts being
 enabled: replace its body with text saying This panel will only work in
 standards mode, set your doctype like so: !DOCTYPE html 


 On Fri, Dec 11, 2009 at 2:35 AM, Stuart Moffatt 
 stuartmoff...@gmail.comwrote:

 Logged as issue 4331

 http://code.google.com/p/google-web-toolkit/issues/detail?id=4331

 On Dec 10, 9:54 am, Stuart Moffatt stuartmoff...@gmail.com wrote:
  @jgw,
 
  Thanks for the rescue. I thought I was going crazy. Totally forgot about
 the
  effects of doctype.
 
  Nice to have: when the eclipse project wizard (or the app creator tool)
 is
  updated to create a UiBinder-style Greeting template, it would be nice
 if
  the doctype in the template html page was switched to standards-mode.
 Less
  heart attacks for sleepy coders ;)
 
  sfm
 
 
 
  On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:
   [duplicating my last message because it failed to post to groups/gwt
 last
   time]
 
   On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com wrote:
 
   The problem here is that you're using RootLayoutPanel explicitly,
 which
   requires the use of a standards-mode doctype.
 
* This widget will emonly/em work in standards mode, which
 requires
   that
* the HTML page in which it is run have an explicit lt;!DOCTYPEgt;
* declaration.
 
   The good news is that these days you can just throw a !DOCTYPE html
   declaration at the top of the page to get there -- no need to dig
 through
   the 37 different versions of [x]html doctypes. IE is particularly
 strange in
   quirks mode, which is why you're seeing such a large difference.
 
   Hope that helps,
   joel.
 
   On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com
 wrote:
 
   @bruce, @jwg, @rjrjr
 
   (and any other gwt'ers listening)
 
   I just posted about a fairly severe show-stopper for my application
   (that is, the app doesn't even finish onModuleLoad() in IE7 (see
 
  
 http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
   )
 
   I thought it was likely due to my code. So I built a dead simple
   EntryPoint using the UiBinder wizard with a few touch ups:
 
   import com.google.gwt.core.client.EntryPoint;
   import com.google.gwt.core.client.GWT;
   import com.google.gwt.uibinder.client.UiBinder;
   import com.google.gwt.uibinder.client.UiField;
   import com.google.gwt.user.client.ui.Button;
   import com.google.gwt.user.client.ui.HTMLPanel;
   import com.google.gwt.user.client.ui.RootLayoutPanel;
   import com.google.gwt.user.client.ui.Widget;
 
   public class UiBinderTestForIE implements EntryPoint {
 
  private static UiBinderTestForIEBinder uiBinder = GWT.create
   (UiBinderTestForIEBinder.class);
  interface UiBinderTestForIEBinder extends UiBinderWidget,
   UiBinderTestForIE {}
 
  @UiField Button button;
  @UiField HTMLPanel htmlPanel;
 
  public void onModuleLoad() {
 
  Widget w = uiBinder.createAndBindUi(this);
  RootLayoutPanel root = RootLayoutPanel.get();
  root.add(w);
  }
 
   }
 
   And here is the ui.xml
 
   !DOCTYPE ui:UiBinder SYSTEM 
 http://dl.google.com/gwt/DTD/xhtml.ent;
   ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
  xmlns:g=urn:import:com.google.gwt.user.client.ui
  ui:style
  .important {
  font-weight: bold;
  }
  /ui:style
  g:HTMLPanel ui:field=htmlPanel
  Hello,
  g:Button styleName={style.important}
   ui:field=buttonUser/
   g:Button
  /g:HTMLPanel
   /ui:UiBinder
 
   When I launch this in Chrome / FF, I get what I expect. When
 launched
   in IE7, there is nothing on the page. Yet, the console reports that
   the module has been loaded.
 
   At first I thought it was a problem with the developer plugin in IE,
   so I compiled it and put it up on my App Engine sandbox:
  http://uibindertestforie.latest.emcode-dev.appspot.comand tested
 from
   two different machines. Works in FF/Chrome on both machines. Nothing
   in IE7 on either machine.
 
   What's the deal?
 
   Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
   can't actually believe it, so someone please tell me what I am doing
   wrong.
 
   Stuart
 
   [cross-posting to gwt, gwt-contrib]
 
   --
 
   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-tool...@googlegroups.com
   .
   To unsubscribe from this group, send email to
   google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs
 cr...@googlegroups.com

Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?

[Stuart Moffatt]

Just to be clear: Issue 4331 is not about the doctype declaration. My posts
on doctype and another (very troublesome) defect regarding IE got crossed.
Sorry for the confusion.

Stuart

On Thu, Dec 10, 2009 at 3:34 PM, Joel Webber j...@google.com wrote:

 Lex's idea as well. I'll do that.


 On Thu, Dec 10, 2009 at 2:39 PM, Ray Ryan rj...@google.com wrote:

 Joel, shouldn't we put an assert to that effect somewhere in
 RootLayoutPanel? Perhaps even something more garrish, tied to asserts being
 enabled: replace its body with text saying This panel will only work in
 standards mode, set your doctype like so: !DOCTYPE html 


 On Fri, Dec 11, 2009 at 2:35 AM, Stuart Moffatt 
 stuartmoff...@gmail.comwrote:

 Logged as issue 4331

 http://code.google.com/p/google-web-toolkit/issues/detail?id=4331

 On Dec 10, 9:54 am, Stuart Moffatt stuartmoff...@gmail.com wrote:
  @jgw,
 
  Thanks for the rescue. I thought I was going crazy. Totally forgot
 about the
  effects of doctype.
 
  Nice to have: when the eclipse project wizard (or the app creator tool)
 is
  updated to create a UiBinder-style Greeting template, it would be nice
 if
  the doctype in the template html page was switched to standards-mode.
 Less
  heart attacks for sleepy coders ;)
 
  sfm
 
 
 
  On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber j...@google.com wrote:
   [duplicating my last message because it failed to post to groups/gwt
 last
   time]
 
   On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber j...@google.com
 wrote:
 
   The problem here is that you're using RootLayoutPanel explicitly,
 which
   requires the use of a standards-mode doctype.
 
* This widget will emonly/em work in standards mode, which
 requires
   that
* the HTML page in which it is run have an explicit
 lt;!DOCTYPEgt;
* declaration.
 
   The good news is that these days you can just throw a !DOCTYPE
 html
   declaration at the top of the page to get there -- no need to dig
 through
   the 37 different versions of [x]html doctypes. IE is particularly
 strange in
   quirks mode, which is why you're seeing such a large difference.
 
   Hope that helps,
   joel.
 
   On Wed, Dec 9, 2009 at 9:36 PM, Stuart stuartmoff...@gmail.com
 wrote:
 
   @bruce, @jwg, @rjrjr
 
   (and any other gwt'ers listening)
 
   I just posted about a fairly severe show-stopper for my application
   (that is, the app doesn't even finish onModuleLoad() in IE7 (see
 
  
 http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
   )
 
   I thought it was likely due to my code. So I built a dead simple
   EntryPoint using the UiBinder wizard with a few touch ups:
 
   import com.google.gwt.core.client.EntryPoint;
   import com.google.gwt.core.client.GWT;
   import com.google.gwt.uibinder.client.UiBinder;
   import com.google.gwt.uibinder.client.UiField;
   import com.google.gwt.user.client.ui.Button;
   import com.google.gwt.user.client.ui.HTMLPanel;
   import com.google.gwt.user.client.ui.RootLayoutPanel;
   import com.google.gwt.user.client.ui.Widget;
 
   public class UiBinderTestForIE implements EntryPoint {
 
  private static UiBinderTestForIEBinder uiBinder = GWT.create
   (UiBinderTestForIEBinder.class);
  interface UiBinderTestForIEBinder extends UiBinderWidget,
   UiBinderTestForIE {}
 
  @UiField Button button;
  @UiField HTMLPanel htmlPanel;
 
  public void onModuleLoad() {
 
  Widget w = uiBinder.createAndBindUi(this);
  RootLayoutPanel root = RootLayoutPanel.get();
  root.add(w);
  }
 
   }
 
   And here is the ui.xml
 
   !DOCTYPE ui:UiBinder SYSTEM 
 http://dl.google.com/gwt/DTD/xhtml.ent;
   ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
  xmlns:g=urn:import:com.google.gwt.user.client.ui
  ui:style
  .important {
  font-weight: bold;
  }
  /ui:style
  g:HTMLPanel ui:field=htmlPanel
  Hello,
  g:Button styleName={style.important}
   ui:field=buttonUser/
   g:Button
  /g:HTMLPanel
   /ui:UiBinder
 
   When I launch this in Chrome / FF, I get what I expect. When
 launched
   in IE7, there is nothing on the page. Yet, the console reports that
   the module has been loaded.
 
   At first I thought it was a problem with the developer plugin in
 IE,
   so I compiled it and put it up on my App Engine sandbox:
  http://uibindertestforie.latest.emcode-dev.appspot.comand tested
 from
   two different machines. Works in FF/Chrome on both machines.
 Nothing
   in IE7 on either machine.
 
   What's the deal?
 
   Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
   can't actually believe it, so someone please tell me what I am
 doing
   wrong.
 
   Stuart
 
   [cross-posting to gwt, gwt-contrib]
 
   --
 
   You received this message because you are subscribed to the Google
 Groups
   Google Web Toolkit group.
   To post to this group, send

Re: GWT 2.0 dead in IE7?

[piyush sharma]

On 12/10/09, Stuart stuartmoff...@gmail.com wrote:

 @bruce, @jwg, @rjrjr

 (and any other gwt'ers listening)

 I just posted about a fairly severe show-stopper for my application
 (that is, the app doesn't even finish onModuleLoad() in IE7 (see

 http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
 )

 I thought it was likely due to my code. So I built a dead simple
 EntryPoint using the UiBinder wizard with a few touch ups:

 import com.google.gwt.core.client.EntryPoint;
 import com.google.gwt.core.client.GWT;
 import com.google.gwt.uibinder.client.UiBinder;
 import com.google.gwt.uibinder.client.UiField;
 import com.google.gwt.user.client.ui.Button;
 import com.google.gwt.user.client.ui.HTMLPanel;
 import com.google.gwt.user.client.ui.RootLayoutPanel;
 import com.google.gwt.user.client.ui.Widget;

 public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
 (UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
 UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

 }

 And here is the ui.xml

 !DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important}
 ui:field=buttonUser/
 g:Button
/g:HTMLPanel
 /ui:UiBinder

 When I launch this in Chrome / FF, I get what I expect. When launched
 in IE7, there is nothing on the page. Yet, the console reports that
 the module has been loaded.

 At first I thought it was a problem with the developer plugin in IE,
 so I compiled it and put it up on my App Engine sandbox:
 http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
 two different machines. Works in FF/Chrome on both machines. Nothing
 in IE7 on either machine.

 What's the deal?

 Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
 can't actually believe it, so someone please tell me what I am doing
 wrong.

 Stuart

 [cross-posting to gwt, gwt-contrib]

 --

 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-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@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-tool...@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-contrib] GWT 2.0 dead in IE7?

[Stuart Moffatt]

@bruce, @jwg, @rjrjr

(and any other gwt'ers listening)

I just posted about a fairly severe show-stopper for my application
(that is, the app doesn't even finish onModuleLoad() in IE7 (see
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3)

I thought it was likely due to my code. So I built a dead simple
EntryPoint using the UiBinder wizard with a few touch ups:

import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.core.client.GWT;
import com.google.gwt.uibinder.client.UiBinder;
import com.google.gwt.uibinder.client.UiField;
import com.google.gwt.user.client.ui.Button;
import com.google.gwt.user.client.ui.HTMLPanel;
import com.google.gwt.user.client.ui.RootLayoutPanel;
import com.google.gwt.user.client.ui.Widget;

public class UiBinderTestForIE implements EntryPoint {

private static UiBinderTestForIEBinder uiBinder = GWT.create
(UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinderWidget,
UiBinderTestForIE {}

@UiField Button button;
@UiField HTMLPanel htmlPanel;

public void onModuleLoad() {

Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}

}

And here is the ui.xml

!DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
ui:style
.important {
font-weight: bold;
}
/ui:style
g:HTMLPanel ui:field=htmlPanel
Hello,
g:Button styleName={style.important} ui:field=buttonUser/
g:Button
/g:HTMLPanel
/ui:UiBinder

When I launch this in Chrome / FF, I get what I expect. When launched
in IE7, there is nothing on the page. Yet, the console reports that
the module has been loaded.

At first I thought it was a problem with the developer plugin in IE,
so I compiled it and put it up on my App Engine sandbox:
http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
two different machines. Works in FF/Chrome on both machines. Nothing
in IE7 on either machine.

What's the deal?

Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
can't actually believe it, so someone please tell me what I am doing
wrong.

Stuart

[cross-posting to gwt, gwt-contrib]

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: GWT Compilation - Dead End

[Sumit Chandel]

Hi NullPointer,
Thanks for posting up about this. There are a couple of issue reports and
potential patches in the works to try to help with both problems (helping to
load large, multi-module applications asynchronously and slow compile
times), but some of them still have a way to go.

I think it would be great if you could follow-up on those issue reports to
help surface them to the team. You can find them at the link below:

Issue #620 - Better multi-module support through GWT.runAsync():
http://code.google.com/p/google-web-toolkit/issues/detail?id=620

Issue #356 - There are a few dupes of this one with useful info, just search
for compiler speed on the Issue Tracker
http://code.google.com/p/google-web-toolkit/issues/detail?id=356

Help for compilation speed is actually available in the trunk, so you can
already get an idea of how much faster your compilations can get in a
parallelized compiler.

While waiting for GWT.runAsync(), I think a solution along the lines of what
Ian and Ruquan have suggested could help in the interim. From what you
mentioned, it seems that it might be a bit of a pain to implement since you
have a lot of custom adapters, but it might be something to try until
runAsync() becomes available.

Hope that helps,
-Sumit Chandel

On Mon, Oct 6, 2008 at 5:17 AM, [EMAIL PROTECTED] 
[EMAIL PROTECTED] wrote:


 Hi Dear,

 I think my solution will help for large GWT applications, even the
 application my have more than 2000 screens.

 1. We defined a general screen rendering engine;
 2. The screen definition are defined in XML where it can be
 unmarshalled  into java object graph and then could be serialized into
 string in GWT RPC format.
 3. The screen definition could be put on the server file system or
 database, and the screen could be loaded on demand on GWT client side.
 4. The screen definition could also be put on the javascript
 dictionary, and then loaded on demand on the client side.
  screens[orderForm]=abdddkdklfdkalfjaf;alsdla;
   The String is the GWT serialized screen definition, the javascript
 dictionary is generated based on the user role, and is generated in
 the main page, for GWT we only have one page, right?
 5. Only event listener need to be added for a new screen, where the
 code lines amount is pretty small.


  The compilation time and javascript size is never a problem for
 us,and the screen could be customized on the fly.




 On 10月5日, 下午10时20分, NullPointer [EMAIL PROTECTED] wrote:
  Sorry, in the last line in the above post I meant to say 'Also the
  generated code is much like a hand-coded code and therefore
  there are no runtime rendering overheads. I hope you are clear.'.
 


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compilation - Dead End

[NullPointer]

@TrashHalo While I agree that GWT compiler can look in to
optimizations, I am neutral to the idea of allowing optimization
options to be passed on to the compiler. I believe that should be left
to the discretion of GWT team.

Now back to my question on JavaScript size; I did a search on the GWT
forum and found that no one ever has complained about the JavaScript
size. Is it because no one has built a large application that has
around 4000-5000 GWT source files?
GWT compiler should certainly look in to options of splitting this
JavaScript in to multiple javascript and lazy load JavaScript. If
optimizations of similiar kind already exist, then I should read back
the manual.

@Ian On your question on rendering on-the-fly, We had this as one of
our initial options. Allowing the user to design the screen and then
persisting this screen structure (what widgets and how they are
grouped i.e a Tab panel or a popup etc) in the database and when the
user accesses the actual screen, fetch this structure information at
runtime and render the screen by creating widgets and panels and
adding them on the fly.

Firstly, this design had its own drawbacks
#1. The cost of fetching the screen information runtime and
rendering(which takes significant amount of time to load the screen).
Particularly that i told you, we had anywhere between 500-1000 widgets
grouped under various panels, popup panels and tab panels.
#2. Inability to perform Reflection. We have cases where users can
register Custom Adapters to certain Widgets and binding adapters to
widgets at runtime is not possible, unless i write one big IF loop,
something like this.
if(adapterName.equals(com.google.DoThisAdapter)) {
return new com.google.DoThisAdapter();
} else if(adapterName.equals(com.google.DoThatAdapter)) {
return new com.google.DoThatAdapter();
} ...
...
.

This made us resort to the static generation of the UI code, because
the screen designing is just a one time process in the lifecycle of
the product we are building i.e. The first time our product is
customized for a given customer.

Also the generated code is much like a hand-coded code and therefore
there are runtime rendering overheads. I hope you are clear.

Removed thread content for brevity
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compilation - Dead End

[NullPointer]

Further to this topic, it makes me wonder on how I design a larger
application using GWT. My application has as much as 200-300
screens(each screen a composite panel contains anything more than
500-1000 widgets in different tabpanels, popups etc) and how to load
all these screens from a single menubar.

#1. Organizing all the code for 200 screens in to different GWT
modules and makig the module containing the Menubar depend on these
modules and loading the individual screens by instantiating the
respective composite panel and adding to the main panel does not help
bring down the JavaScript size. Irrespective of how you organize your
modules, there will still be one JavaScript generated for every
browser and that JavaScript will contain the code for all the classes
in all these separate modules. For an application of the size of mine,
the size of JavaScript is 15MB. Correct me if i am wrong

#2. Second option i have is to organize the code for these 200 screens
in to different modules and have different HTML page for each of these
group of screens calling the respective entrypoints. The module
containing the Menubar will not depend on these child modules but uses
a GWT FramePanel and calls the appropriate HTML with relevant
parameters and load the respective screen. But this defeats the AJAX
pattern and there will be a number of round trips to the Server to
load each separate screen.

Any help on how to tackle the JavaScript size and how to load 200-300
different screens from the same Menubar will be much appreciated.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compilation - Dead End

[Ian Bambury]

Hi,

I might well be missing something here, but if your users are designing
screens, why do you need to recompile?

If they can create them with DnD, why can't you recreate them on the fly?

Ian

http://examples.roughian.com

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compilation - Dead End

[TrashHalo]

Sorry for the double reply but I decided to file an issue for build
flags to control the optimization level to allow for faster
compilation time during development. 
http://code.google.com/p/google-web-toolkit/issues/detail?id=2944

On Oct 4, 10:24 pm, TrashHalo [EMAIL PROTECTED] wrote:
 I don't think we (GWT Developers) would care too much about long
 compilation times if we did not have to encounter them on a daily
 basis. If you have been tracking the issue tracker over the past year
 you would know that the great majority of compilation time is a result
 of each optimization pass. Last year I requested the feature to
 disable/enable optimization passes through flags passed in to the
 compiler (http://groups.google.com/group/Google-Web-Toolkit/
 browse_thread/thread/349b06c86440bd7b/4a1793fc70fb1d56?
 lnk=gstq=trashhalo#4a1793fc70fb1d56)

 Bruce responded until there are some really strong concrete reasons
 to expose fine-grained switches (other than turn them off/on), we
 err on the side of keeping things simple. I hope you would agree that
 disabling time expensive optimizations during development would be a
 concrete reason for providing developers with the option to disable
 certain optimizations. When I originally made that post I had spent
 some time digging through the compiler source code to better
 understand how the optimizations are implemented.

 Back then (and I would hope this is still the case today) each
 optimization type/pass was encapsulated into its own object. The
 compiler then passed the payload into each of these optimizer objects.
 Because of this setup adding compilation flags to skip certain
 optimizations would be trivial. These optimizations could be reenabled
 for test or production builds.

 On Oct 4, 9:49 pm, NullPointer [EMAIL PROTECTED] wrote:

  Further to this topic, it makes me wonder on how I design a larger
  application using GWT. My application has as much as 200-300
  screens(each screen a composite panel contains anything more than
  500-1000 widgets in different tabpanels, popups etc) and how to load
  all these screens from a single menubar.

  #1. Organizing all the code for 200 screens in to different GWT
  modules and makig the module containing the Menubar depend on these
  modules and loading the individual screens by instantiating the
  respective composite panel and adding to the main panel does not help
  bring down the JavaScript size. Irrespective of how you organize your
  modules, there will still be one JavaScript generated for every
  browser and that JavaScript will contain the code for all the classes
  in all these separate modules. For an application of the size of mine,
  the size of JavaScript is 15MB. Correct me if i am wrong

  #2. Second option i have is to organize the code for these 200 screens
  in to different modules and have different HTML page for each of these
  group of screens calling the respective entrypoints. The module
  containing the Menubar will not depend on these child modules but uses
  a GWT FramePanel and calls the appropriate HTML with relevant
  parameters and load the respective screen. But this defeats the AJAX
  pattern and there will be a number of round trips to the Server to
  load each separate screen.

  Any help on how to tackle the JavaScript size and how to load 200-300
  different screens from the same Menubar will be much appreciated.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compilation - Dead End

[TrashHalo]

I don't think we (GWT Developers) would care too much about long
compilation times if we did not have to encounter them on a daily
basis. If you have been tracking the issue tracker over the past year
you would know that the great majority of compilation time is a result
of each optimization pass. Last year I requested the feature to
disable/enable optimization passes through flags passed in to the
compiler (http://groups.google.com/group/Google-Web-Toolkit/
browse_thread/thread/349b06c86440bd7b/4a1793fc70fb1d56?
lnk=gstq=trashhalo#4a1793fc70fb1d56)

Bruce responded until there are some really strong concrete reasons
to expose fine-grained switches (other than turn them off/on), we
err on the side of keeping things simple. I hope you would agree that
disabling time expensive optimizations during development would be a
concrete reason for providing developers with the option to disable
certain optimizations. When I originally made that post I had spent
some time digging through the compiler source code to better
understand how the optimizations are implemented.

Back then (and I would hope this is still the case today) each
optimization type/pass was encapsulated into its own object. The
compiler then passed the payload into each of these optimizer objects.
Because of this setup adding compilation flags to skip certain
optimizations would be trivial. These optimizations could be reenabled
for test or production builds.


On Oct 4, 9:49 pm, NullPointer [EMAIL PROTECTED] wrote:
 Further to this topic, it makes me wonder on how I design a larger
 application using GWT. My application has as much as 200-300
 screens(each screen a composite panel contains anything more than
 500-1000 widgets in different tabpanels, popups etc) and how to load
 all these screens from a single menubar.

 #1. Organizing all the code for 200 screens in to different GWT
 modules and makig the module containing the Menubar depend on these
 modules and loading the individual screens by instantiating the
 respective composite panel and adding to the main panel does not help
 bring down the JavaScript size. Irrespective of how you organize your
 modules, there will still be one JavaScript generated for every
 browser and that JavaScript will contain the code for all the classes
 in all these separate modules. For an application of the size of mine,
 the size of JavaScript is 15MB. Correct me if i am wrong

 #2. Second option i have is to organize the code for these 200 screens
 in to different modules and have different HTML page for each of these
 group of screens calling the respective entrypoints. The module
 containing the Menubar will not depend on these child modules but uses
 a GWT FramePanel and calls the appropriate HTML with relevant
 parameters and load the respective screen. But this defeats the AJAX
 pattern and there will be a number of round trips to the Server to
 load each separate screen.

 Any help on how to tackle the JavaScript size and how to load 200-300
 different screens from the same Menubar will be much appreciated.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---