Re: [gwt-contrib] Re: Bad news for GWT DevMode!

2013-10-23 Thread Daniel Kurka 
Can somebody update the missing plugin page to recognize the IE11 user
agent string as IE11?
(IE11 preview is different from actual IE11)


On Tue, Oct 22, 2013 at 8:06 PM, Matthew Dempsky wrote:

> On Tue, Oct 22, 2013 at 11:03 AM, Colin Alworth wrote:
>
>> Amazingly, it still works great in the IE11 preview too! Only gotcha is
>> that the missing plugin page thinks you are running firefox, so you need to
>> manually grab the right copy of the IE plugin.
>>
>
> Haha.  We should file a bug against IE11 that they don't support FF
> plugins. ;)
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

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

[gwt-contrib] Re: Gerrit presubmit changes

2013-10-23 Thread Thomas Broyer 
You might want to add those instructions to the README file, for anyone 
willing to hack on them.

(one issue with the current code, unless you fixed it recently, is that 
it'll post Verified+1 / Verified-1 for old patchsets, in the event that you 
posted a new patchset when the new one was being built – or queued; also, I 
haven't checked, but it'd be great to cancel builds for patchsets that are 
now obsolete, either cancelling them if they're queued or just making them 
no-ops when they'll run)

On Tuesday, October 22, 2013 8:36:03 PM UTC+2, Matthew Dempsky wrote:
>
> One more update: The presubmitter tools are now open source.
>
> They're written in Go and the source code is available at 
> https://gwt.googlesource.com/buildglue/.  You can easily download and 
> build it using the go command:
>
>   mkdir buildglue
>   export GOPATH=$PWD/buildglue
>   go get gwt.googlesource.com/buildglue.git/cmd/...
>   # Git checkout is now at $GOPATH/src/gwt.googlesource.com/buildglue.git
>   # Compiled tools are now in $GOPATH/bin
>
>
> On Sun, Oct 20, 2013 at 6:57 PM, Matthew Dempsky 
> 
> > wrote:
>
>> I've made a few changes to the presubmit process this weekend that I 
>> wanted to share:
>>
>>   1. There's now an initial "fast style check" step that should give 
>> style feedback much faster (on average within about a minute).  If this 
>> fails, then the usual build/full-style check is skipped.
>>
>>   2. Style warnings are now presented inline as normal Gerrit review 
>> comments so you don't need to dig through the build log to figure out what 
>> went wrong.  E.g., see https://gwt-review.googlesource.com/#/c/5035/ for 
>> an example review.
>>
>>   3. In addition to the usual style 'errors' that the full style check 
>> warns about, the fast style check will include 'info' and 'warning' 
>> messages, but only if they came from a source line modified by the change 
>> (as identified by "git blame").
>>
>>   4. The fast style check now also includes some basic warnings for 
>> commit messages that don't follow Git commit message best 
>> practices.
>>  
>>  Currently it checks that the subject line is <=50 chars, the second line 
>> is blank, and all other lines are <=72 chars.
>>
>>   5. I've configured an issue tracker template for reporting issues with 
>> the presubmitter: 
>> https://code.google.com/p/google-web-toolkit/issues/entry?template=Presubmit%20issue
>>   
>> If you notice anything wrong or that could be improved, please feel free to 
>> submit an issue.
>>
>> Thanks
>>
>
>

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

[gwt-contrib] Re: Change in gwt[master]: Added disabled IE10 permutation

2013-10-23 Thread Jens 
I would tend to vote for option 2. 

With option 1 nearly everyone will need to disable the ie10 permutation 
anyways because not only own code must be updated but also 3rd party 
libraries must provide updated rebind rules which may take some time. So I 
think it feels better if ie10 is disabled by default and you can enable it 
once you know your app and all your 3rd party libraries are ready.

-- J.

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

Re: [gwt-contrib] Re: Gerrit presubmit changes

2013-10-23 Thread Matthew Dempsky 
On Wed, Oct 23, 2013 at 1:25 AM, Thomas Broyer  wrote:

> You might want to add those instructions to the README file, for anyone
> willing to hack on them.
>

https://gwt-review.googlesource.com/#/c/5080/

(one issue with the current code, unless you fixed it recently, is that
> it'll post Verified+1 / Verified-1 for old patchsets, in the event that you
> posted a new patchset when the new one was being built – or queued; also, I
> haven't checked, but it'd be great to cancel builds for patchsets that are
> now obsolete, either cancelling them if they're queued or just making them
> no-ops when they'll run)
>

Yep, that's certainly an issue.  The current jenkins interface is pretty
minimal, just enough to fire off additional presubmit jobs
(jenkins.go).
 I imagine it wouldn't be hard to add some additional methods for checking
what presubmit jobs are pending and cancelling a pending job.

Filed https://code.google.com/p/google-web-toolkit/issues/detail?id=8406 to
keep track of it.

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

[gwt-contrib] build of the master branch is broken ?

2013-10-23 Thread Julien Dramaix 
Hi all,

I've just synchronized my master branch with the remote one and try to 
build gwt by invoking ant but I receive the following error :

build.alldeps.jar:

compile:

-filter.props:

build:

compile:

precompile.modules:
 [java] Loading inherited module 'com.google.gwt.core.Core'
 [java]Loading inherited module 'com.google.gwt.emul.Emulation'
 [java]   Loading inherited module 'com.google.gwt.logging.LogImpl'
 [java]  [ERROR] Line 14: Unexpected exception while processing 
element 'replace-with'
 [java] java.lang.NoSuchMethodError: 
com.google.gwt.dev.cfg.ConditionAll: method ()V not found
 [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
 [java] at 
com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
 [java] at 
com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
 [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
 [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

the full compilation log can be found there 
: https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing

Does anyone have an idea ?

Thanks,

Julien

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

Re: [gwt-contrib] build of the master branch is broken ?

2013-10-23 Thread John Stalcup 
I'll take a look
On Oct 23, 2013 8:00 AM, "Julien Dramaix"  wrote:

> Hi all,
>
> I've just synchronized my master branch with the remote one and try to
> build gwt by invoking ant but I receive the following error :
>
> build.alldeps.jar:
>
> compile:
>
> -filter.props:
>
> build:
>
> compile:
>
> precompile.modules:
>  [java] Loading inherited module 'com.google.gwt.core.Core'
>  [java]Loading inherited module 'com.google.gwt.emul.Emulation'
>  [java]   Loading inherited module 'com.google.gwt.logging.LogImpl'
>  [java]  [ERROR] Line 14: Unexpected exception while
> processing element 'replace-with'
>  [java] java.lang.NoSuchMethodError:
> com.google.gwt.dev.cfg.ConditionAll: method ()V not found
>  [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
>  [java] at
> com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
>  [java] at
> com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>  [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> the full compilation log can be found there :
> https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing
>
> Does anyone have an idea ?
>
> Thanks,
>
> Julien
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

[gwt-contrib] Re: build of the master branch is broken ?

2013-10-23 Thread Julien Dramaix 
Sorry I sent this message too quickly... I reconfigured my environment this 
morning (reinstall ant and java) and I'm pretty this error occurs because 
I'm compiling with an old version of java. 

On Wednesday, October 23, 2013 5:00:21 PM UTC+2, Julien Dramaix wrote:
>
> Hi all,
>
> I've just synchronized my master branch with the remote one and try to 
> build gwt by invoking ant but I receive the following error :
>
> build.alldeps.jar:
>
> compile:
>
> -filter.props:
>
> build:
>
> compile:
>
> precompile.modules:
>  [java] Loading inherited module 'com.google.gwt.core.Core'
>  [java]Loading inherited module 'com.google.gwt.emul.Emulation'
>  [java]   Loading inherited module 'com.google.gwt.logging.LogImpl'
>  [java]  [ERROR] Line 14: Unexpected exception while 
> processing element 'replace-with'
>  [java] java.lang.NoSuchMethodError: 
> com.google.gwt.dev.cfg.ConditionAll: method ()V not found
>  [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
>  [java] at 
> com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
>  [java] at 
> com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>  [java] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> the full compilation log can be found there : 
> https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing
>
> Does anyone have an idea ?
>
> Thanks,
>
> Julien
>

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

Re: [gwt-contrib] build of the master branch is broken ?

2013-10-23 Thread Julien Dramaix 
ok John keep me inform. FYI, my environment seems to be correct (ant 1.9.2
with java 1.7) and the git history tells me that this class was modified
recently.

Thanks,

Julien


On Wed, Oct 23, 2013 at 5:02 PM, John Stalcup  wrote:

> I'll take a look
> On Oct 23, 2013 8:00 AM, "Julien Dramaix" 
> wrote:
>
>> Hi all,
>>
>> I've just synchronized my master branch with the remote one and try to
>> build gwt by invoking ant but I receive the following error :
>>
>> build.alldeps.jar:
>>
>> compile:
>>
>> -filter.props:
>>
>> build:
>>
>> compile:
>>
>> precompile.modules:
>>  [java] Loading inherited module 'com.google.gwt.core.Core'
>>  [java]Loading inherited module 'com.google.gwt.emul.Emulation'
>>  [java]   Loading inherited module
>> 'com.google.gwt.logging.LogImpl'
>>  [java]  [ERROR] Line 14: Unexpected exception while
>> processing element 'replace-with'
>>  [java] java.lang.NoSuchMethodError:
>> com.google.gwt.dev.cfg.ConditionAll: method ()V not found
>>  [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
>>  [java] at
>> com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
>>  [java] at
>> com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
>>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>  [java] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> the full compilation log can be found there :
>> https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing
>>
>> Does anyone have an idea ?
>>
>> Thanks,
>>
>> Julien
>>
>> --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/W33ekCUisa0/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

[gwt-contrib] Re: Change in gwt[master]: Added disabled IE10 permutation

2013-10-23 Thread Brian Slesinsky 
Hmm. It's a fair point. On the other hand, you don't *have* to upgrade
right away. Assuming third-party libraries want to upgrade, it might be
easier to make "works with 2.6" mean "works with a separate ie10
permutation" rather than having to support two modes for 2.6.

This doesn't scale, but if there's a specific third-party binding you're
concerned about, perhaps it's possible to write your own rebind rule to
bind it for ie10?

- Brian


On Wed, Oct 23, 2013 at 2:08 AM, Jens  wrote:

> I would tend to vote for option 2.
>
> With option 1 nearly everyone will need to disable the ie10 permutation
> anyways because not only own code must be updated but also 3rd party
> libraries must provide updated rebind rules which may take some time. So I
> think it feels better if ie10 is disabled by default and you can enable it
> once you know your app and all your 3rd party libraries are ready.
>
> -- J.
>

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

Re: [gwt-contrib] build of the master branch is broken ?

2013-10-23 Thread John Stalcup 
It appears that runtime execution is resulting from trying to use the old
zero-args constructor when it should be using the new varargs constructor.
I think it's likely that you need to recompile the class files that refer
to ConditionAll/CompoundCondition etc.

does it work for you after an "ant clean" ?


On Wed, Oct 23, 2013 at 8:13 AM, Julien Dramaix wrote:

> ok John keep me inform. FYI, my environment seems to be correct (ant 1.9.2
> with java 1.7) and the git history tells me that this class was modified
> recently.
>
> Thanks,
>
> Julien
>
>
> On Wed, Oct 23, 2013 at 5:02 PM, John Stalcup  wrote:
>
>> I'll take a look
>> On Oct 23, 2013 8:00 AM, "Julien Dramaix" 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've just synchronized my master branch with the remote one and try to
>>> build gwt by invoking ant but I receive the following error :
>>>
>>> build.alldeps.jar:
>>>
>>> compile:
>>>
>>> -filter.props:
>>>
>>> build:
>>>
>>> compile:
>>>
>>> precompile.modules:
>>>  [java] Loading inherited module 'com.google.gwt.core.Core'
>>>  [java]Loading inherited module 'com.google.gwt.emul.Emulation'
>>>  [java]   Loading inherited module
>>> 'com.google.gwt.logging.LogImpl'
>>>  [java]  [ERROR] Line 14: Unexpected exception while
>>> processing element 'replace-with'
>>>  [java] java.lang.NoSuchMethodError:
>>> com.google.gwt.dev.cfg.ConditionAll: method ()V not found
>>>  [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
>>>  [java] at
>>> com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
>>>  [java] at
>>> com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
>>>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>>  [java] at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>
>>> the full compilation log can be found there :
>>> https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing
>>>
>>> Does anyone have an idea ?
>>>
>>> Thanks,
>>>
>>> Julien
>>>
>>> --
>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>  --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "GWT Contributors" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-web-toolkit-contributors/W33ekCUisa0/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

Re: [gwt-contrib] build of the master branch is broken ?

2013-10-23 Thread Julien Dramaix 
"ant clean" has solved the problem !

Thanks,

Julien


On Wed, Oct 23, 2013 at 6:15 PM, John Stalcup  wrote:

> It appears that runtime execution is resulting from trying to use the old
> zero-args constructor when it should be using the new varargs constructor.
> I think it's likely that you need to recompile the class files that refer
> to ConditionAll/CompoundCondition etc.
>
> does it work for you after an "ant clean" ?
>
>
> On Wed, Oct 23, 2013 at 8:13 AM, Julien Dramaix 
> wrote:
>
>> ok John keep me inform. FYI, my environment seems to be correct (ant
>> 1.9.2 with java 1.7) and the git history tells me that this class was
>> modified recently.
>>
>> Thanks,
>>
>> Julien
>>
>>
>> On Wed, Oct 23, 2013 at 5:02 PM, John Stalcup  wrote:
>>
>>> I'll take a look
>>> On Oct 23, 2013 8:00 AM, "Julien Dramaix" 
>>> wrote:
>>>
 Hi all,

 I've just synchronized my master branch with the remote one and try to
 build gwt by invoking ant but I receive the following error :

 build.alldeps.jar:

 compile:

 -filter.props:

 build:

 compile:

 precompile.modules:
  [java] Loading inherited module 'com.google.gwt.core.Core'
  [java]Loading inherited module 'com.google.gwt.emul.Emulation'
  [java]   Loading inherited module
 'com.google.gwt.logging.LogImpl'
  [java]  [ERROR] Line 14: Unexpected exception while
 processing element 'replace-with'
  [java] java.lang.NoSuchMethodError:
 com.google.gwt.dev.cfg.ConditionAll: method ()V not found
  [java] at com.google.gwt.dev.cfg.Rule.(Rule.java:29)
  [java] at
 com.google.gwt.dev.cfg.RuleReplaceWith.(RuleReplaceWith.java:31)
  [java] at
 com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__replace_with_begin(ModuleDefSchema.java:570)
  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
 Method)
  [java] at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 the full compilation log can be found there :
 https://docs.google.com/file/d/0BwVGJUurq6uVZ1N0MXJLaFVnRFk/edit?usp=sharing

 Does anyone have an idea ?

 Thanks,

 Julien

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 You received this message because you are subscribed to the Google
 Groups "GWT Contributors" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.

>>>  --
>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "GWT Contributors" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/google-web-toolkit-contributors/W33ekCUisa0/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/W33ekCUisa0/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

[gwt-contrib] Re: Change in gwt[master]: Added disabled IE10 permutation

2013-10-23 Thread Jens 

>
> Hmm. It's a fair point. On the other hand, you don't *have* to upgrade 
> right away.
>

Hehe sure, but its hard to resist Java7, @GwtIncompatible support and 
compiler/code splitting bug fixes ;-) 

But maybe I misunderstood Matthew's post? I was under the impression that 
with either solution 1 or 2 I could upgrade right away to 2.6 without 
problems. In order to stay on the safe side when upgrading to 2.6 the only 
thing I need to care about is to make sure that IE10 permutation is 
disabled (which means I put myself in the same situation as with GWT 2.5.1 
which does not know IE 10).
So as a developer I will update to 2.6 right away, disable IE 10 
permutation (or don't disable it if its disabled by default) and benefit 
from GWT 2.6 bug fixes and features. Why should I wait? After I have done 
that the dev team can continue with their current work and a single guy may 
starts looking around for rebind rules in app code and figures out the 
situation with 3rd party libraries used in that app. 

The "disabled by default until everything is proved to work" way seems just 
more natural to me (and possibly everyone) for GWT 2.6. In GWT 3.0 it's 
then enabled by default.

Or is one solution more complicated than the other and I don't get it? I 
thought its just a matter of style how to fill the user.agent property 
correctly and what will be written into the release notes.


This doesn't scale, but if there's a specific third-party binding you're 
> concerned about, perhaps it's possible to write your own rebind rule to 
> bind it for ie10?
>

Personally I had nothing specific in mind as I only use libraries providing 
infrastructure code. But I would guess any library that somehow provides 
HTML 5 features, widgets, or just need to hack DomImpl classes are probably 
good candidates. Of course its possible to provide own rebind rules but 
maybe you also need to provide different implementations. In that case its 
probably more likely to wait for the library to update and disable IE10 in 
the mean time.


-- J.

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