Re: [gwt-contrib] Re: Jetty upgrade broke HtmlUnit for window.onerror

['Daniel Kurka' via GWT Contributors]

I am not aware of anything specific we have done within Google, we never
imported the jetty upgrade. I think you just go ahead for open source and
make it work there. We do not care that much for htmlunit anymore within
Google.

On Tue, Oct 10, 2017 at 10:28 AM Thomas Broyer  wrote:

>
>
> On Tuesday, October 10, 2017 at 6:08:05 PM UTC+2, Colin Alworth wrote:
>>
>> Patch is accepted and merged into upstream HtmlUnit, see
>> https://sourceforge.net/p/htmlunit/bugs/1924/ for more detail.
>>
>> Daniel, when you can take a look at Thomas's question, we can get this
>> change made to open source GWT as you requested.
>>
>
> Here's the workaround for HtmlUnit
> https://gwt-review.googlesource.com/c/gwt/+/19680
> The only problem left is
> https://github.com/gwtproject/gwt/blob/a3df04c0f5469bdcf49bdd564467255951ef6559/user/super/com/google/gwt/junit/translatable/com/google/gwt/junit/client/impl/GWTRunner.java#L209-L215
> which doesn't play nicely with
> https://github.com/gwtproject/gwt/blob/a3df04c0f5469bdcf49bdd564467255951ef6559/user/src/com/google/gwt/core/client/impl/Impl.java#L273-L277
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/245093f8-c1c1-4e71-9291-0b9e3af66eb9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiohp1oqMvBYUFJPfx44pawqmpgC2G9CRwZUrz3mcmswfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Jetty upgrade broke HtmlUnit for window.onerror

['Daniel Kurka' via GWT Contributors]

Hi all,

I spend a considerable amount of time on getting our changes for
window.onerror launched in open source:
https://gwt-review.googlesource.com/#/c/gwt/+/18880/

This causes some tests to fail in html unit:
http://build.gwtproject.org/job/gwt/972/testReport/

Note: these tests are already failing but not reported failing with the
newer version of HTML unit. As soon as we are starting to trap
window.onerror in tests we actually catch the exception and thus fail those
6 test cases.

Things I have tried:

   - Place @DoNotRun on the tests, does not work for the JUnit tests since
   they require all methods to run
   - Downgrade HtmlUnit in open source, fails with a noclass def for
   WebSocket out of Jetty
   - Upgrade HmltUnit to latest (2.27), fails to start the testing shell in
   open source


Trapping window.onerror the default in open source GWT is important and the
right way forward, we simply do not have the bandwith to do it right now. A
simple way of making it happen would be to roll back the jetty upgrade. We
are not going to invest further into this for OS, but would rather see
somebody else pick this up. Any takers?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujir8N8Bs4MKsGeeVpd3uqT5JxQbduUDNEiVZN6zm2zVT2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.1 release

[Daniel Kurka]

There is some reasoning behind us not broadly announcing elemental2 and the
jsinteorp generator:
They are both still beta software in the sense that we know there are
existing problems, but we already want feedback on them.
There are still no guarantees on APIs / compat but if you are brave and
want to be part of evolving them and turning them into a finished and
polished product, you can do that.

We will announce them broadly once we consider them ready for general use
and have a compatibility guarantee in place.

On Wed, Jun 7, 2017 at 11:48 AM Vassilis Virvilis  wrote:

> Ah yes that explains it. It was j2cl that I remembered.
>
> Thanks for the clarification.
>
> Vassilis
>
> On Wed, Jun 7, 2017 at 9:40 PM, Colin Alworth  wrote:
>
>> I think you may be misremembering - the jars were released to maven as
>> experimental last summer, then as beta in April, and only after that were
>> they on github.
>>
>> J2CL is not expected to be dropped until it is "ready", but as with
>> elemental2, this isn't going to mean "bugfree" but more like "complete
>> enough to be reviewed and used".
>>
>> On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:
>>>
>>> Looks like they are also here in source form
>>>
>>> https://github.com/google/elemental2
>>> https://github.com/google/jsinterop-generator
>>>
>>> I thought google didn't want to release them before they were "ready".
>>> So either they changed their mind, or they feel it is ready or I don't
>>> remember correctly :-)
>>>
>>>  Vassilis
>>>
>>> On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth  wrote:
>>>
 The groupId has changed - using the mvnrepository site, try
 https://mvnrepository.com/artifact/com.google.elemental2 to see all of
 the jars now available.


 On Wednesday, June 7, 2017 at 11:14:33 AM UTC-5, Bruno Salmon wrote:
>
>
>
>> Additionally, this supports the recent beta release of jsinterop.base
>> and elemental2, available from Maven Central.
>>
>>
>>
> Where can we find that elemental2  beta release (I can see only the
> June 2016 version on that page
> 
> )?
>
> Thanks for all your amazing work.
>
 --
>> 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.
>

-- 
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: [gwt-contrib] Re: JsInterop & collections

['Daniel Kurka' via GWT Contributors]

In general we consider JSNI deprecated and it will not be present in the
new J2CL transpiler.

JsInterop (together with Jsinterop base) is powerful enough to do all
things you were doing in JS.

public class Helper {
  @JsMethod(name = "Array.prototype.push.apply", namespace=JsPackage.GLOBAL)
  static void apply(Object that, Object value);
}


On Wed, May 10, 2017 at 1:22 PM Marcin Okraszewski <okr...@gmail.com> wrote:

> Looks better indeed. Are there also some other reasons not to use JSNI?
> Eg. performance, or it is going to be removed in future?
>
> How would I call  Array.prototype.push.apply(arrayList, value); via
> JsInterop? Or if I wanted to add a function to an existing object?
>
> Thank you,
> Marcin
>
>
> On Wednesday, 10 May 2017 20:02:46 UTC+2, Daniel Kurka wrote:
>
>> First of all do not use JSNI going forward.
>>
>> Use elemental2 (or define your own JSON.parse):
>>
>> Without elemental2:
>> @JsType(isNative=true, namespace = JsPackage.GLOBAL);
>> public class JSON {
>>   public static Object parse(String s, Reviver r);
>> }
>>
>> @JsFunction
>> public interface Reviver {
>>   public Object run(String key, Object value);
>> }
>>
>> // usage:
>> MyObject o = (MyObject) JSON.parse(s, (key, value) -> {
>>   // whatever change you need to do
>>   return value;
>> });
>>
>> -Daniel
>>
>> On Wed, May 10, 2017 at 9:53 AM <sup...@bpilotglobal.com> wrote:
>>
>>>
>>> I am still new to GWT (so this code is probably naive), but I
>>> implemented this JSON parse wrapper which performs "transparent" conversion
>>> of JS arrays to java.util.List and using replacer/reviver functions:
>>>
>>> https://github.com/bpilot/jclosure/blob/master/src/main/java/ailabs/jclosure/client/encoding/json/JsonParser.java
>>>
>>> Could this be made more general?
>>>
>>>
>>> On Wednesday, May 10, 2017 at 11:40:53 AM UTC-4, Marcin Okraszewski
>>> wrote:
>>>>
>>>> I've done something that I think is so far the closest to what I want
>>>> to achieve - the same object behaving as List in Java and as array in JS.
>>>> Actually it can be seen in Java as either list or array - both work :-)
>>>>
>>>> First I declare JsArray:
>>>>
>>>> @JsType(isNative=true, name="Array", namespace=JsPackage.GLOBAL)
>>>> public class JsArray {
>>>>   // JS method declarations here, but can be also empty
>>>> }
>>>>
>>>>
>>>> Then extend create a List that extends the JsArray
>>>>
>>>> @JsType
>>>> public class JsArrayList extends JsArray implements List {
>>>>   // List implementation here
>>>> }
>>>>
>>>>
>>>> Now, parse JSON and replace arrays with instances of JsArrayList.
>>>>
>>>> private static native  T parse(String json) /*-{
>>>> return JSON.parse(json, function(key, value) {
>>>> if (Array.isArray(value)) {
>>>> var arrayList = new @interop.client.JsArrayList::new();
>>>> Array.prototype.push.apply(arrayList, value);
>>>> value = arrayList;
>>>> }
>>>> return value;
>>>> });
>>>> }-*/;
>>>>
>>>> Now, if the JSON includes any array, you will be able to use in Java as
>>>> List.
>>>>
>>>> Problems so far:
>>>>
>>>>1. All elements of the array need to be copied. I was tempted to
>>>>just change __proto__ with the one from JsArrayList, but that is said to
>>>>affect performance. I could also add methods from JsArrayList to the
>>>>instance, not sure if that is better from performance standpoint.
>>>>2. The extended array is not recognized as an array in JS (although
>>>>it behaves as array). Array.isArray() returns false, same for instanceof
>>>>Array. I guess, adding functions to array instance would solve it.
>>>>3. While parsing metadata are missing, what actual type should that
>>>>be. Switching arrays to list is a decision without context. But when we
>>>>want to treat an object as map, then it would need to be known somehow. 
>>>> It
>>>>can be naming convention of fields, but it is not perfect; could not
>>>>supported nested collections. Some meta provided from the interface 
>>>> that is
>>>>being cased, would be gr

Re: [gwt-contrib] Re: JsInterop & collections

['Daniel Kurka' via GWT Contributors]

First of all do not use JSNI going forward.

Use elemental2 (or define your own JSON.parse):

Without elemental2:
@JsType(isNative=true, namespace = JsPackage.GLOBAL);
public class JSON {
  public static Object parse(String s, Reviver r);
}

@JsFunction
public interface Reviver {
  public Object run(String key, Object value);
}

// usage:
MyObject o = (MyObject) JSON.parse(s, (key, value) -> {
  // whatever change you need to do
  return value;
});

-Daniel

On Wed, May 10, 2017 at 9:53 AM  wrote:

>
> I am still new to GWT (so this code is probably naive), but I implemented
> this JSON parse wrapper which performs "transparent" conversion of JS
> arrays to java.util.List and using replacer/reviver functions:
>
> https://github.com/bpilot/jclosure/blob/master/src/main/java/ailabs/jclosure/client/encoding/json/JsonParser.java
>
> Could this be made more general?
>
>
> On Wednesday, May 10, 2017 at 11:40:53 AM UTC-4, Marcin Okraszewski wrote:
>>
>> I've done something that I think is so far the closest to what I want to
>> achieve - the same object behaving as List in Java and as array in JS.
>> Actually it can be seen in Java as either list or array - both work :-)
>>
>> First I declare JsArray:
>>
>> @JsType(isNative=true, name="Array", namespace=JsPackage.GLOBAL)
>> public class JsArray {
>>   // JS method declarations here, but can be also empty
>> }
>>
>>
>> Then extend create a List that extends the JsArray
>>
>> @JsType
>> public class JsArrayList extends JsArray implements List {
>>   // List implementation here
>> }
>>
>>
>> Now, parse JSON and replace arrays with instances of JsArrayList.
>>
>> private static native  T parse(String json) /*-{
>> return JSON.parse(json, function(key, value) {
>> if (Array.isArray(value)) {
>> var arrayList = new @interop.client.JsArrayList::new();
>> Array.prototype.push.apply(arrayList, value);
>> value = arrayList;
>> }
>> return value;
>> });
>> }-*/;
>>
>> Now, if the JSON includes any array, you will be able to use in Java as
>> List.
>>
>> Problems so far:
>>
>>1. All elements of the array need to be copied. I was tempted to just
>>change __proto__ with the one from JsArrayList, but that is said to affect
>>performance. I could also add methods from JsArrayList to the instance, 
>> not
>>sure if that is better from performance standpoint.
>>2. The extended array is not recognized as an array in JS (although
>>it behaves as array). Array.isArray() returns false, same for instanceof
>>Array. I guess, adding functions to array instance would solve it.
>>3. While parsing metadata are missing, what actual type should that
>>be. Switching arrays to list is a decision without context. But when we
>>want to treat an object as map, then it would need to be known somehow. It
>>can be naming convention of fields, but it is not perfect; could not
>>supported nested collections. Some meta provided from the interface that 
>> is
>>being cased, would be great.
>>
>> Do you have any thoughts on that maybe?
>>
>> Thank you,
>> Marcin
>>
>>
>> On Wednesday, 10 May 2017 01:19:58 UTC+2, Ray Cromwell wrote:
>>>
>>> I think it would be better to use a JsArrayListAdapter in order to
>>> prevent making copies all over the place, and also making mutations
>>> write-through on both sides e.g.
>>>
>>> public class JsArrayListAdapter extends AbstractList {
>>>public JsArrayListAdapter(ArrayLike blah) {
>>>   this.array = blah;
>>>   }
>>>
>>>   // implement List methods to delegate to Array methods
>>> }
>>>
>>> To keep referential integrity, you need to use an expando or ES6 Symbol
>>> property to hide a backreference.
>>>
>>> That is, JsArrayListAdapter.wrap(nativeJsArray) ==
>>> JsArrayListAdapter.wrap(nativeJsArray2) IFF nativeJsArray == nativeJsArray2.
>>>
>>> This technique is less error prone IMHO if you are going to have mutable
>>> objects. If you're using immutables, then making copies is superior.
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 9, 2017 at 3:24 PM 'Goktug Gokdogan' via GWT Contributors <
>>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
 Yes, theoretically you should be able to use the second parameter on
 Json.parse Json.stringify for conversion back and forth between java
 collections and js primitives. In this model, your javascript code needs to
 use Java collection APIs.

 > java.util.Arrays.asList() should be enough

 keep in mind that Arrays.asList won't let you go out of bounds.



 > I believe it was in plans with @JsConvert


 We are not working on @JsConvert right now. JsConvert is just
 convenience and you can mimic it:


   @JsType(isNative=true)
   interface MyType {
  @JsConvert(ListConverter.class)
  List getMyArray()
  void setMyArray(@JsConvert(ListConverter.class) List array)
   }

 is roughly equivalent to:

   

Re: Compilation of a large GWT application?

[Daniel Kurka]

There is a whitelist / blacklist to control that.

On Mon, Apr 10, 2017 at 12:30 PM Kirill Prazdnikov <pkir...@gmail.com>
wrote:

> As far as I know this will add lots of GWT internal stuff which I not
> going to export. Right ?
>
> понедельник, 10 апреля 2017 г., 21:57:33 UTC+3 пользователь Daniel Kurka
> написал:
>
> If you compile your gwt app with -generateJsInteropExports any @JsType is
> accessible in global scope:
>
>
> --
> 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: Compilation of a large GWT application?

[Daniel Kurka]

If you compile your gwt app with -generateJsInteropExports any @JsType is
accessible in global scope:

Exporting app:

package foo;

@JsType
public Bar {
  public Baz baz = new Baz();
}

Consuming JS:
new Bar().baz.baz1();

Consuming gwt app ( No need for -generateJsInteropExports):

@JsType(isNative = true, name = Bar, namespace = "foo")
public class Bar {
  Baz baz;
}



On Mon, Apr 10, 2017 at 11:45 AM Kirill Prazdnikov 
wrote:

> You can also use DOM Elememts as an interop types.
>
> --
> 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: [gwt-contrib] Re: PROPOSAL: a devserver to replace devmode

['Daniel Kurka' via GWT Contributors]

I am seeing a lot of arguments pop up about GWT RPC, but I think it should
not be considered for this discussion at all. In my mind GWT 2.8 will be
the last release that has GWT RPC and people should start migrating. I
think its perfectly fine do design a replacement to devmode without GWT RPC
support.

On Mon, Oct 24, 2016 at 4:18 PM Jens  wrote:

> Well it is just what I would ask for in order to replace local apache /
> nginx on developer machines with GWT devserver. It's not a problem to
> simply continue using a dedicated proxy either with CodeServer or a "no-op"
> devserver.
>
> Basically our setup is more a less the result of two decisions: Not
> serving static content from servlet containers (instead it's severed by
> load balancer/proxy) and using GWT-RPC. We need to be in control of which
> app version a customer gets served, even before logging in, and that
> backend requests will be redirected to a matching server app version
> (because of GWT-RPC policy files and rolling updates). Thats why our
> production mapping is https://app.example.com// =>
> /_/ for backend requests and the load
> balancer does the mapping using URL rewriting.
>
> During development we just have a single app so the rewriting is a lot
> simpler but it still exists. Given that our server code sets cookies for
> the production domain only (I guess some paranoid security decision), the
> cookie domain needs to be rewritten during development to a local ip /
> localhost.
>
> Given that static content is served by the load balancer / proxy itself,
> all caching headers (*.nocache.*, *.cache.*) are configured outside the
> servlet container. For consistency cache headers for dynamic host page are
> also configured outside the servlet container. So we don't have any
> ServletFilter doing it.
>
>
>
> Hey, this is a currently just a prototype coded over the week-end ;-)
> I'd personally prefer not writing anything to the webapp, but as
> acknowledged in the OP we could have a -launcherDir option for
> serialization policies and possibly public resources
>
> (but then why not just use CodeServer with -launcherDir directly? one
> difference could be that devserver would never overwrite a file for
> example…)
>
>
> Well I could also ask: Why not just having a single solution that simply
> works? Personally I don't like having different "entry points" for
> development. IMHO its more straight forward (especially for beginners) to
> just have CodeServer or just have devserver, but not both (even with
> different behavior for stub.nocache.js !).
>
> Adding gwt.codeserver.host and renaming -launcherDir to
> -publicResourcesDir would be fine I guess.
>
>
>
> Next there are people embedding the module.nocache.js file directly into
> their host page (like me ;-) basically our host page is a servlet) and that
> should work also during development.
>
>
> I can't think of any other way to make it work (I did that too in one app)
> than having a way to switch from inlined *.nocache.js to external
> *.nocache.js on your server. There's absolutely no risk shipping that in
> production (it's only a network optimisation to avoid one HTTP request) so
> it looks like an acceptable compromise to me.
>
>
> Well devserver could special case host page loading ("/" or a configurable
> host page url) and inspect the result of the backend server to decide
> wether or not some inline *.nocache.js file needs to be replaced. To keep
> it simply I would require special enclosing start / end comments in the
> dynamic host page to make it compatible with devserver. Then the content in
> between these comments will be replaced with the stub.nocache.js.
>
>
>
>
> …or you could just continue using CodeServer with -launcherDir.
>
>
> Single solution preferred ;-)
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/361aafb5-d40d-433c-a6ba-6209069e5550%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirgPjFnGzPGKKp5zUB497mZko%2BTzKMsAAbYOSaLBRJNTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 released

[Daniel Kurka]

Hi Alex,

thanks for your non negative way of approaching this. The docs on
gwtproject.org are open source and anybody is welcome to change them on
github:

It's as simple as clicking edit on the page:
https://github.com/gwtproject/gwt-site

If you feel something is outdated simply propose a patch. These docs are
not being maintained by the GWT team at Google and we rely on open source
contributions to update them.

-Daniel



On Fri, Oct 21, 2016 at 10:16 PM Alex W <alexwhite3...@gmail.com> wrote:

> The GWT team couldn't even be bothered to delete the out of date docs on
> gwtproject.org for the release? For shame. I'm not being negative; this
> is a team that  needs more criticism, both internal and external.
>
>
> On Saturday, October 22, 2016 at 5:21:41 AM UTC+10, Daniel Kurka wrote:
>
> Hi all,
>
> I am very happy to announce GWT 2.8.0 on behalf of the GWT steering
> committee and the GWT team at Google.
>
> You can download the release from http://www.gwtproject.org/download.html
> or from maven central.
>
> The release notes can be found at
> http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0
>
> Daniel,
> on behalf of the GWT team
>
> --
> 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: [gwt-contrib] Re: 2.8 (final) is released very silent!?

['Daniel Kurka' via GWT Contributors]

I just sent the announcement to gwt-users that its now final, the reason
you could see the tag is that I pushed this as part of our release process.

The reason the tag is 17 days old is that its identical with that commit
(we have not changed GWT), traditionally we just turn the RC into the final
release.

On Fri, Oct 21, 2016 at 9:24 PM Lars  wrote:

> Make sense ... good to have the 2.8 ready now! :-)
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/f69d2d0e-4e52-405e-bade-396f361120b2%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiopCO67eCQcxwJECq0zVPoWBbJSPj8Uzf19bj85eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT 2.8.0 released

['Daniel Kurka' via GWT Users]

Hi all,

I am very happy to announce GWT 2.8.0 on behalf of the GWT steering 
committee and the GWT team at Google.

You can download the release from http://www.gwtproject.org/download.html 
or from maven central.

The release notes can be found at 
http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0

Daniel,
on behalf of the GWT team

-- 
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: Extending native JsTypes from Java with GWT 2.8.0-rc2

[Daniel Kurka]

If you file a bug please include a simple repro case. In general this seems
to be working fine (and is used withing google). So there must be something
specific about our particular case.

On Wed, Sep 21, 2016 at 9:43 AM Thomas Broyer  wrote:

> It should be possible, from spec:
> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#heading=h.aaedpeo8ehl8
>
> Can you file a bug in the issue tracker?
> https://github.com/gwtproject/gwt/issues
>
>
> On Wednesday, September 21, 2016 at 9:38:16 AM UTC+2, Nándor Előd Fekete
> wrote:
>
> Hi everyone!
>
> Are we supposed to be able to extend native (browser) JsTypes from Java?
> Specifically, having the following declaration (from Elemental2):
>
> @JsType(isNative = true, namespace = JsPackage.GLOBAL)
> public class HTMLDivElement extends HTMLElement {...}
>
> and the extending type
>
> public class DummyElement extends HTMLDivElement {...}
>
> I'm getting TypeError: Illegal invocation from the compiled js code when
> it tries to define the class (com.google.gwt.lang.Runtime.copyObjectProperties
> (Runtime.java:104)), while copying native properties from the extends js
> type's prototype. The property in this case is 'align' but it happens on
> other browser native properties too.
>
> Thanks for the help!
>
> All the best,
> Nandi.
>
> --
> 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: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

['Daniel Kurka' via GWT Contributors]

This is what recompile on reload is for, you can simply always load:

http://[sdmhost]:[sdmport]/recompile-requester/[module]

On Tue, Sep 13, 2016 at 5:53 PM JonL  wrote:

> I've had to do this when working on a sdm compiled application in a web
> wrapper on ios, instead of a proxy, I wrote a custom nocache.js that
> replaces the one generated by sdm and adds a url parameter to tell it the
> remote server to connect to where the codeserver is running, allowing me to
> debug the application running directly on the ipad correctly.
>
> Here is a gist of a sligtly modified version of the nocache.js replacing
> the module name with "module_name":
>
> https://gist.github.com/jonl-percsolutions-com/403ec9ba1bf50a6abcb0db852b171d0c
>
> So I just run my gwt-compile, replace the nocache.js and then create the
> war for deployment.   The when accessing the url, provide the url paramter "
> remote_server=http://ip:port;.
>
> Not sure if this will be what you need 100% but should work instead of
> setting up a proxy or clobbering the codeserver api.
>
>
> On Monday, September 12, 2016 at 12:24:54 PM UTC-7, Brandon Donnelson
> wrote:
>
> Proxying wasn't an option for developers because of the I.T. security
> protocols. Besides it feels a bit overcomplicated to have to set up a
> channel back to the code server. I think it would be easier to clobber the
> codeserver api with a workaround and setting the hosteName and hand that to
> the developers. I'm contemplating on forking the code server for GWT 2.7
> users to provide a workaround for the hostName through the program
> arguments.
>
> On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer  wrote:
>
> How about proxying through a local server that would intercept the
> nocache.js and route everything else to your external server? This is
> basically how webpack devserver and browserSync work in the JS land.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> *Brandon Donnelson*
> GXT Support Engineer
>  
> 
> 
> 
> [image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9]
> 
> *Join me at SenchaCon 2016!*
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/274f1c7b-8267-4164-8d11-ab3e64dd9721%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujio-C04RR1v%2BPbf0AA5QcQp8S4ts%3DEbn7SkgT2ENheYc8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

['Daniel Kurka' via GWT Contributors]

+Goktug Gokdogan  +Roberto Lublinerman
  Should we be holding RC3, I guess so right?

On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:

>
> Can you file an issue and ping Daniel (by mail or hangout) to delay the
> RC3 a bit? (if not already too late, as it's 4pm cest)
>
>
> Done.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/6386bb88-f488-4144-b830-99ddb387b677%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirOwMPQTKzDuJtmtF0hF2bXVr%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

['Daniel Kurka' via GWT Contributors]

This is a last call for patches, anything that is not in until tomorrow
(and is not important enough to hold the release) will not get in.

Is there already a patch in review for this?



On Thu, Sep 8, 2016 at 5:40 PM Kay-Uwe Janssen <kujans...@gmail.com> wrote:

> Is there a plan to fix the ValdiationTool (issue mentioned here:
> https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/lue7vRkkxU8
> ) for default and static methods in proxy interfaces? or is it already
> fixed?
>
> if one it should be documented as known issue with
> the @SkipInterfaceValidation workaround mentioned.
>
>
> Am Donnerstag, 8. September 2016 16:27:36 UTC+2 schrieb Daniel Kurka:
>
> Hi all,
>
> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with
> any outstanding reviews that you want to see included.
>
> -Daniel
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a949505-2cc9-42b1-9a01-b8c71ed18bf6%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a949505-2cc9-42b1-9a01-b8c71ed18bf6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirqBM692yDn9Ptt8PD0v1LR_9%3DKxEmQHg1r9R4Mh5fsGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Last call for 2.8.0-RC3

['Daniel Kurka' via GWT Contributors]

Hi all,

I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with
any outstanding reviews that you want to see included.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqFjhAVQF5Ke%2BxH0Ch-XLrAzMNSWQXoGwN-4H1Y6oMO1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: CalenderUtil Date Math BUG - GWT 2.8 RC2

[Daniel Kurka]

Does this code do the same thing in 2.7?

On Wed, Aug 31, 2016 at 11:41 PM Paul Robinson  wrote:

> You don't say what part of this you think is a bug. I presume it's the
> fact that Aug 31 plus one month is Oct 1. If so, this is not a bug.
>
> Adding one month should do literally that, so you get September 31. But
> there are only 30 days in September, so this automatically becomes October
> 1.
>
> Paul
>
> --
> 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: [gwt-contrib] Re: A possible JsInterop issue in GWT 2.8 RC2

['Daniel Kurka' via GWT Contributors]

Jens is spot on. We want people to explicitly use -generateJsInteropExports
if they rely on exporting since it has a hit on code size.

On Mon, Aug 22, 2016 at 12:56 PM Thomas Broyer  wrote:

> FWIW, I believe this is
> https://github.com/gwtproject/gwt/commit/ca8ad7bc140bc23b237620c41d755ef787bd97b1
> (i.e. on-purpose)
>
>
> On Friday, August 19, 2016 at 9:38:32 PM UTC+2, Jens wrote:
>>
>> @JsType with isNative = false (the default) are probably treated as
>> normal classes now if you do not use -generateJsInteropExports as compiler
>> parameter. I guess it works again if you use the compiler parameter?
>>
>> -- J.
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/c901940b-5b21-4717-b9d7-58a471eaa357%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqJgO%3DEGgTYpxJ5vx80vUN03p9hGsm%3D-HABO3Xe%2BODxHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT 2.8.0 RC2 is here!

['Daniel Kurka' via GWT Users]

Hi all,

I just build the GWT 2.8.0 RC2 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble and file 
bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC 
2
 will 
be made available shortly after this notice, in the mean time you can take 
a look at the github repository 

.

Daniel,
on behalf of the GWT team

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

[gwt-contrib] GWT 2.8.0 RC2 is here!

['Daniel Kurka' via GWT Contributors]

Hi all,

I just build the GWT 2.8.0 RC2 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble and file 
bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC 
2
 will 
be made available shortly after this notice, in the mean time you can take 
a look at the github repository 

.

Daniel,
on behalf of the GWT team



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/af652b4a-7e1c-4c33-8b75-5c12033908ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 - MultiModule Setup and SDM recompilation

[Daniel Kurka]

Even at Google for really large projects recompile times do not exceed
15seconds. So something is wrong in your setup since we only do recompile
changed files after the first compile.

Are you giving enough ram to SDM?
Are you really only changing a few files (or is something else updating
timestamp on these files)?


On Thu, Aug 11, 2016 at 1:08 AM Lars  wrote:

> Try to use 2.8 snapshot for SDM and the stable 2.7 release for production,
> because 2.8 has more SDM optimizations to speed up the development cycle!
>
> --
> 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.

[gwt-contrib] Last call for GWT 2.8.0 RC2

['Daniel Kurka' via GWT Contributors]

Hi all,

I think we have all patches in place for putting out an RC2.
If you feel strongly that something should make RC2 please raise this on
this thread. I will be cutting RC2 tomorrow PST time.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqqHDBK2uNZL1jFhR9Adv1srrRmwTsh%2BJ5EeU%3DcaMeLkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

2.8.0 RC1 is here!

['Daniel Kurka' via GWT Users]

Hi all,

I just build the GWT 2.8.0 RC1 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble. You can 
either reply to this thread on gwt-contrib 

 or file bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC1 

 
will be made available shortly after this notice, in the mean time you can 
take a look at the github repository 

.

Daniel,
on behalf of the GWT team

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

[gwt-contrib] GWT 2.8.0 RC1 is here!

['Daniel Kurka' via GWT Contributors]

Hi all,

I just build the GWT 2.8.0 RC1 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble and file 
bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC1 

 will 
be made available shortly after this notice, in the mean time you can take 
a look at the github repository 

.

Daniel,
on behalf of the GWT team

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/3448c7da-f600-48a6-90c4-08172f841283%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8 RC1 Help with testing

['Daniel Kurka' via GWT Contributors]

submitting thomas two fixes and then recutting.

On Thu, Jul 21, 2016 at 12:57 PM Brandon Donnelson 
wrote:

> Where's the link to the GWT 2.8.0-rc1.zip?
>
>
> On Thursday, July 21, 2016 at 7:22:11 AM UTC-7, Thomas Broyer wrote:
>>
>>
>>
>> On Thursday, July 21, 2016 at 4:11:09 PM UTC+2, Michael Joyner wrote:
>>>
>>> Can it be tagged and pulled via jitpack.io ?
>>>
>>
>> Ha ha, jitpack wouldn't know how to build and deploy it:
>> https://jitpack.io/docs/BUILDING/
>> …and the RC1 tag can still "move" if we find bugs during the smoke tests
>> (it **would** move, as I found small issues, e.g.
>> https://gwt-review.googlesource.com/15445)
>>
>> Ideally, you should use the gwt-2.8.0-rc1.zip provided by Daniel as input
>> to the maven/push-gwt.sh script from the GWT repo (select 2.8.0-rc1 and
>> 1.0.0 for gwt and jsinterop versions respectively)
>> Currently, 2.8.0-SNAPSHOT are the same as 2.8.0-rc1, so you could also
>> use that (but if you're planning on doing formal DOA/smoke tests before the
>> RC1 release, you should use the maven/push-gwt.sh script)
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/80338352-9133-4404-ad51-8147b01431d7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirqzV-%3DKrfRwL-WF80dcsYunQUszEYqsQtAT7K99hfQcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8 RC1 Help with testing

['Daniel Kurka' via GWT Contributors]

Hi all,

we have build the preliminary GWT 2.8.0-rc1 version and now need help with
DOA testing (making sure its not dead on arrival).

We are currently missing testers for:

Linux / Chrome
Windows 7 / IE8/IE9
Windows 7 / IE 10
Windows 7 / IE 11

If you are interested in spending ~1h in testing the new GWT release,
please reach out to me.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipOWx590QLZs0OKED12%2BW5jKmNsnY1zQw0XshxyY5yM6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT RPC in GWT 3.0+

[Daniel Kurka]

I summed up what I think about GWT RPC and it's future here:
http://blog.daniel-kurka.de/2016/07/gwt-rpcs-future.html

On Thu, Jul 14, 2016 at 12:01 AM JonL <j...@percsolutions.com> wrote:

> While I agree that it could theoretically work with annotations,
> annotations require access to code, so for things you have no control over,
> you either would need to implement custom serialization anyways, or use the
> GWT serialization.
>
> I personally think there are optimizations to be had in the serialization
> policy generator that would prevent that whole classpath rescan issue, but
> I haven't had a chance to look into the code.
>
> If we were to use annotations, I think it would be better to use
> annotations on the RPC mechanism.
>
> On Wednesday, July 13, 2016 at 9:23:19 AM UTC-7, Thomas Broyer wrote:
>
>>
>>
>> On Wednesday, July 13, 2016 at 5:53:20 PM UTC+2, Paul Robinson wrote:
>>
>
>>> On 13 Jul 2016 9:17 a.m., "Kay Pac" <kmjs...@fastmail.fm> wrote:
>>> >
>>> > Will the gwt serialization mechanism used in GWT-RPC remain? GWT
>>> object serialization has been plugged into the atmosphere (realtime
>>> communication/websockets) GWT extension. It would be useful to know if we
>>> should migrate away from the GWT serialization and towards JSON.
>>>
>>> It's the serialisation that's the problem, so it will be gone in 3.0.
>>> JSON is a good choice. (I'm moving that way)
>>>
>>
>> The actual problem is not serialization per se, it is that the RPC
>> generator scans the whole classpath for subclasses of transferred classes
>> to generate their specific ser/deser code (taking into account their
>> CustomFieldSerializer if one exists).
>> RPC (thus probably Atmosphere) could be made to work (as annotation
>> processors) if they use another mechanism to determine what can be
>> transferred (e.g. annotations similar to RequestFactory's @ExtraTypes).
>> I believe Daniel Kurka said something along those lines a year ago when
>> first talking about those changes. The logical next question is: is there
>> anyone willing to make those changes and continue to maintain GWT-RPC? The
>> answer seemed to be (have been?) "at least that won't be Google", and this
>> is why people start to "panic". That does not mean RPC will be gone (that
>> doesn't mean it'll still be there either).
>> But let's concentrate on 2.8 for now.
>>
> --
> 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: [gwt-contrib] Re: GWT 2.8 rc1 work items

['Daniel Kurka' via GWT Contributors]

I went through the issue tracker and curated the 2.8 mile stone.

Currently we have 22 open issues:
https://github.com/gwtproject/gwt/milestones/2.8

I assigned all unassigned issues and asked clarifying questions, *please go
through your assigned issues and respond to those questions*.
If you feel that you have been wrongly assigned, please assign me back
stating so. I'll try to make sure that the right person will start working
on this.

As for volunteers (to speed up 2.8), please go through the list and see if
you want to help (just because something is assigned does not mean its
getting worked on right now). *Come and ping me about work you want to do!*

*As for adding more work to the 2.8 milestone:*
At this state we want to ship, so anything that is not a critical bug fix
(or is very trivial) will probably not get included. For the work that Jens
mentioned, I'd say if these reviews make it before we cut RC1 they can go
in otherwise I will hold them until after we have shipped 2.8.0.
Also keep in mind that we need a green build before cutting RC1 in open
source (and this only runs daily), so we should not be merging lots of
patches at the last minute.

-Daniel

On Sun, Jun 12, 2016 at 8:28 PM Thomas Broyer <t.bro...@gmail.com> wrote:

>
>
> On Wednesday, June 8, 2016 at 11:06:26 AM UTC+2, Daniel Kurka wrote:
>
>> Hi all,
>>
>> in the last steering committee meeting we agreed that making the next
>> version of Guava work (which contains a lot of Java8 usage) was the goal
>> for RC1.
>>
>> We have gotten significantly closer to this now and I am happy to report
>> that as of now we pass all of Guavas tests.
>> However there are a few work items left to do:
>>
>>  - Make sure we actually run all of the java8 tests in the open source
>> build
>>  - Go through the github issue tracker and look for things missing for
>> the 2.8 milestone
>>  - Discuss the fate of the Jettty upgrades (Google was not able to garden
>> these in yet, so the are not really verified).
>>  - Anything else I might have missed?
>>
>> Do you guys have anything else to add to the list?
>>
>
> I'd like to include https://gwt-review.googlesource.com/15161 in RC1 so
> we have time to test it and possibly revert it or fix it before GA.
>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ec6380bc-29ce-43c4-9b84-951ecc2e35fd%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/ec6380bc-29ce-43c4-9b84-951ecc2e35fd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujir-WOKaKhKe0yEYF%2Bc83oeC1rrD5-pWGgwEiavWSqr0Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8 rc1 work items

['Daniel Kurka' via GWT Contributors]

Hi all,

in the last steering committee meeting we agreed that making the next
version of Guava work (which contains a lot of Java8 usage) was the goal
for RC1.

We have gotten significantly closer to this now and I am happy to report
that as of now we pass all of Guavas tests.
However there are a few work items left to do:

 - Make sure we actually run all of the java8 tests in the open source build
 - Go through the github issue tracker and look for things missing for the
2.8 milestone
 - Discuss the fate of the Jettty upgrades (Google was not able to garden
these in yet, so the are not really verified).
 - Anything else I might have missed?

Do you guys have anything else to add to the list?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirYTA%2BhqRtLW6YyqYkg_Uv8yTZ_CjRqvEE%3DG3u25aa4-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Generator and Linker maintenance and changes

['Daniel Kurka' via GWT Contributors]

Hi all,

thanks for Colin for writing this up.
To me this discussion is not so much about the particular feature
(enhancing generators), but rather about us making smart choices.
We are already struggling to get 2.8 out the door (and making sure it will
work with the next version of Guava). So I'd rather be lighten the work
load and remove things that do not need to be done
I also feel that further enhancing generators dilutes the message we have
been giving for the past year: *Do not use generators anymore, use APTs.*

I am also worried about possible problems that we will uncover once we
allow these things to go into generators.
With the exception of GWT RPC all generators should be easily portable to
an APT. I would love to see work being put into that direction rather than
updating a system we are all not happy with.

-Daniel


On Tue, May 3, 2016 at 11:59 AM Jens  wrote:

>
>>
>>- add new features to existing generators / linkers
>>
>>
> I think to some extend some new features should also be fine if they are
> related to Java 8. For example I could see GWT-RPC being improved to better
> support lambda/method references in the future.
>
> -- J.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/1898a4b0-3eff-4e53-8aba-19e1851a646f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirzBbybuFZM9h9MLFxVLyameG4A5GE0xh2rnxtkq%3D4fow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: RAM memory continously increasing while using GWT Application in IE Browser

[Daniel Kurka]

I vaguely remember fixing a bug around IE10 and tables in GWT. So if that
code is using a HtmlTable or FlexTable I suggest upgrading to GWT 2.7 at
least.

On Sun, May 1, 2016 at 11:51 AM thamarai kannan 
wrote:

> Hi Velusamy sir,
>
> sorry, I can not share the code. Is there any other way to find the
> root cause and fix.
>
>
>
> On Friday, April 29, 2016 at 7:23:30 PM UTC+5:30, Velusamy Velu wrote:
>
>> Thamarai Kannan:
>>
>> Any reason you chose GWT 2.5.1 instead of the latest version?  As
>> Gilberto responded it would be easier to pinpoint the problem if you could
>> share your code, unless you are restricted.
>>
>> On Monday, February 15, 2016 at 5:05:18 AM UTC-5, thamarai kannan wrote:
>>>
>>> Hi, I am using GWT Application. for this application I am using IE10.
>>> While lading another screen or reloading same page my RAM Memory increasing
>>> continously. Approximately each load 5MB RAM memory consuming. Anyone help
>>> me to free this memory space at the time of loading.
>>>
>> --
> 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: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

['Daniel Kurka' via GWT Contributors]

With j2cl we do a javac compile up front and thus those basic problems are
gone.

On Wed, Apr 27, 2016 at 4:22 PM Colin Alworth  wrote:

> Agreed - validating supersource is tricky. I've heard of some good options
> lately that change how the project interacts with them (like compiling to
> .class file and leveraging javac to get the errors), but I don't presently
> have any best practices to suggest in general, except tests for each module
> so that you see the failure on a module-by-module basis rather than having
> to disassemble the entire project as it compiles, and using -strict to
> catch uncompilable sources very early.
>
> On Wed, Apr 27, 2016 at 9:12 AM David  wrote:
>
>> Yes the org.w3c stuff was my own, it was defined in the html5 module you
>> see in the classpath.
>> I hope that this was a border case and not typical what happens if you
>> have super sources with import statements that cannot be resolved ?
>> Because in that case the compiler should give a better error message.
>>
>> On Wed, 27 Apr 2016 at 15:50, Colin Alworth  wrote:
>>
>>> Thanks. Can you confirm that org.w3c.dom is your own code, and not part
>>> of GWT, so it was just out of date? I don't see a jar with that name on
>>> your classpath, and neither of the two EntityReference.java files in GWT
>>> live in that package or appear have jsinterop annotations.
>>>
>>>
>>> On Wednesday, April 27, 2016 at 8:46:13 AM UTC-5, stuckagain wrote:
>>>
 Colin,

 The stacktrace was is my initial post.

 Anyway: I managed to find the root cause and solution.

 The super source java file is using JsInterop to map org.w3c.dom API's.
 It had annotations like this:
 @JsType(isNative=true, namespace=JsNamespace.GLOBAL).

 However, in the snapshot this JsNamespace no longer exists and is now
 replaced with JsPackage.GLOBAL.
 After changing those references the compilation now succeeds.

 The old sources were like this:
 package org.w3c.dom;
 import com.google.gwt.core.client.js.JsNamespace;;
 import jsinterop.annotations.JsType;
  @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
 public interface EntityReference extends Node {
 }
 I changed it to this:
 package org.w3c.dom;
 import jsinterop.annotations.JsPackage;
 import jsinterop.annotations.JsType;
  @JsType(isNative=true,namespace=JsPackage.GLOBAL)
 public interface EntityReference extends Node {
 }


 On Wed, 27 Apr 2016 at 15:32, Colin Alworth  wrote:

>>> Can you share the stack trace, the file it is attempting to read, and
> your classpath? It does sound like it might be a bug, but without the
> ability to reproduce, it is difficult to say more. One case where it might
> not be a bug despite its behavior: where it is reusing gwt-unitCache or 
> the
> like from an older version of gwt.
>
> On Wed, Apr 27, 2016 at 8:23 AM David  wrote:
>
 I managed to get this to run in a Debugger, from within the maven
>> invocation.
>> The exception is thrown on a super source file in one of my gwt-lib
>> maven artifacts.
>> It is trying to parse a .java file as a class file and this throws
>> the reported exception.
>>
>> This sounds like a bug to me!?
>>
>> On Wed, 27 Apr 2016 at 14:41, David  wrote:
>>
> It was working fine with GWT 2.8.0-beta1 using the exact same pom
>>> files. When I point to GWT-2.8.0-SNAPSHOT I get this error.
>>> So the only thing that changed is the version of GWT moving from
>>> beta1 to SNAPSHOT.
>>>
>>> I am using logLevel ALL but it looks like the 2.8 compiler does not
>>> really use logging. Besides a few INFO and WARNING statements nothing is
>>> logged
>>>
>>> This is the path that is being used.
>>>
>>> [DEBUG]   (s) projectArtifactMap =
>>> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
>>> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
>>> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
>>> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
>>> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
>>> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
>>> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
>>> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
>>> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
>>> 

Re: [gwt-contrib] Re: Rules for managing issues on GitHub

['Daniel Kurka' via GWT Contributors]

Nice work Thomas, really appreciated!

On Thu, Apr 14, 2016 at 4:11 PM Thomas Broyer  wrote:

> FWIW, I started doing some of the things I highlighted in the document:
>
>- created GitHub milestones and replaced the Milestone-* labels with
>assignments to the corresponding milestone, for all releases back to 2.1.0
>(older release still to be migrated). When there was labels for RCs, I
>merged them all into the final release; that was only affecting old
>releases for which we don't need to keep such level of details.
>- assigned all FixedNotReleased issues to the 2.8 milestone, closed
>them, and deleted the label.
>- deleted all ReviewBy-* labels.
>
>
> On Monday, March 14, 2016 at 1:19:23 AM UTC+1, Thomas Broyer wrote:
>
>> Hi all,
>>
>> Here's a document a wrote (months ago actually) about the differences
>> between Google Code Hosting and GitHub wrt their respective issue trackers.
>>
>>
>> https://docs.google.com/document/d/1yJva4UWQ7XO-gGtFm4ykXt0tubn9j1nncWPPz57IH9M/edit
>>
>> We discussed it briefly at our last Steering Committee meeting last
>> Wednesday and, as no one had objections, we decided that we'd share it here
>> and seek feedback for a week before setting (some of) those rules in stone.
>> I propose short-term goals of:
>>
>>- deleting old labels (e.g. ReviewBy-* labels)
>>- using the Review-Pending label and adding links to the reviews in
>>comments
>>- using milestones and closing issues when resolved (rather than
>>using a FixedNotReleased label)
>>
>> We can sort out other details (assignment, etc.) later, but your feedback
>> is welcome.
>>
>> I'd also like to align Category-* labels with the "modules" from
>> https://docs.google.com/document/d/1vyncxfuujIJ3L-PBLNM68tfeXRFZ4qDdnWEodblmvRg/edit
>>
>> Thanks in advance.
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/010b67c4-84e9-413d-ad60-9989741adbb4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqj_iJpD149dw%2Bh6FTaCh5wDqvDccqKADYPDvo0jC-c-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

About production issue: Are you sure about this? It's less likely to happen 
in production since many clinit calls will have been stripped by the 
compiler, but its probably still going to happen.

About development: Is there actually a global try catch in your code or is 
this even something else? I am not really familiar with the old GWT linkers 
anymore and how they outputted code.

On Wednesday, April 6, 2016 at 4:47:45 PM UTC+2, TazmanianD wrote:
>
> Thanks so much for the response! You say "all modern versions of GWT". I 
> don't suppose you can be more specific? The 2.8 version hasn't been 
> released yet and we can't upgrade to pre-release versions. We can probably 
> give the beta version a try just to see if it does fix our problem. Is this 
> problem fixed in 2.7? We've been waiting for 2.8 before undertaking the 
> upgrade but it sounds like we need to jump to 2.7 now.
>
> Fortunately for us, this isn't (apparently) a production issue for us yet 
> so we're not in an emergency mode but I gather others may not be so lucky. 
> I posted a reply to a question in the Chrome forum where someone was using 
> GWT 1.6 and upgrading may be even harder for this. I don't suppose you have 
> any other advice for anyone else who may stumble across this and not have 
> an immediate path to upgrade?
>

-- 
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: GWT no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

Hi,

Chrome 49 enabled lots of ES6 features, 
see: http://v8project.blogspot.de/2016/01/v8-release-49.html

Part of this is the so called sloppy function hosting.

A simple example:


ES5 (old semantics)

ES2015 (new semantics)

Code

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // overwrites behavior

foo(); // no-op

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // does not overwrite

foo();

Output

hello

hello

hello


The problem here is the presence of the try catch block and that semantics 
have changed here.
We investigated this a few months back and all modern versions of GWT 
should not be impacted.

So my first recommendation would be to upgrade to GWT 2.8-beta1 and see if 
the issue still exists for you.
 


On Tuesday, April 5, 2016 at 9:38:28 PM UTC+2, TazmanianD wrote:
>
> I'm duplicating a comment I made in the Chrome group but I thought I 
> should cross-post it here as well. We're using GWT 2.5.0 and we're 
> suddenly experiencing massive errors as well although fortunately for us, 
> they only seem to be affecting our development env and not production.
>
> In our case, what I've discovered is that the static initializers for 
> *some* classes are being executed repeatedly. This is fatal for enums as 
> the enum values are recreated each time and they're supposed to be 
> singletons. The result is that EnumMaps for those enums don't work at all. 
> In debugging the code, I found that when the static initializer function 
> reassigns itself to the null function, this works in the function but when 
> the function returns, the function pointer is reset back to where it was 
> originally pointing. This means that next time the initializer is executed, 
> instead of it being a no-op, it runs again. I almost wonder if there's some 
> sort of scope confusion and the function assignment is assigning to the 
> wrong or duplicate function.
>
> And another thing I'll note is that we have soft-permutations enabled in 
> our dev env and when we disable those and generate separate permutations, 
> the problem goes away. I don't see how that can explain what I saw in my 
> debugger but I thought it was worth mentioning.
>
> Unfortunately my attempts at reducing the problem to a simple case have 
> totally failed as when I delete too much, the problem seems to disappear. 
> This unfortunately makes my report here not terribly useful but maybe 
> others can chime in if their seeing the same thing.
>
> But let me try to summarize with some pseudo-code (a simple example like 
> this does *not* exhibit the problem):
>
>
> class MyEnum {
>   static {
> Window.alert("Static Initializer");
>   }
>
>   public void foo() {...}
> }
>
>
> MyEnum instance = new MyEnum();
> instance.foo();
>
> -- When this code is run the alert "Static Initializer" is displayed twice 
> (or more if you have additional usages)
>
> --- Get's compiled into (approximately):
>
> var instance = $clinit$MyEnum(), new MyEnum();
> $clinit$MyEnum(), instance.foo();
>
> function $clinit$MyEnum() {
>   $clinit$MyEnum() = nullFunction; // Disables the static initializer so 
> it doesn't run again
>   $wnd.alert("Static Initializer");
> }
>
> -- What I see in the Chrome debugger is that when $clinit$MyEnum is 
> assigned to the nullFunction, the watch immediately reflects this. However 
> the moment you step back out of the function, the value of "$clinit$MyEnum" 
> returns to the original function.
>

-- 
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: [gwt-contrib] Re: Compiler failing with java 7

['Daniel Kurka' via GWT Contributors]

We have seen issues internally where some code would be a compile error in
Java8 but not in Java7 (especially around type checking). This setup will
leave users vulnerable to this since their code will compile in their IDE,
but will fail GWT compile.

On Thu, Feb 18, 2016 at 8:57 AM Manuel Carrasco Moñino 
wrote:

> I follow, but I have a couple of thoughts
>
> - Is it actually useful from the user perspective to use a sourceLevel=1.7
> if he has to manually provide a compatible gwt-jre-emulation?
> IMO, he might want that everything works out-of-the-boxy. Right now, gwt
> emul classes in the 2.8-snapshot make fail sourceLevel=1.7 though, so I
> don't see any reason to deliver gwt-2.8.0 with a non working flag.
>
> - IMHO, for real users having to code in 1.7, it's not a problem to set
> javac.source=1.7 and have gwtc.sourceLevel=default=1.8. In this case the
> javac compiler will validate his source code and gwtc compiler does not
> need to do the validation, it simply works without raising any error when
> processing its internal jre-emul classes.
>
> So, since gwtc can be run with a sdk7 (even with gwt java8 sources), there
> should not be any problem compiling gwt projects written in java7 and
> compiled with sdk7, and the user does not bother about the sourceLevel flag.
>
>
>
> On Wed, Feb 17, 2016 at 9:13 PM, 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> I think you didn't understand what I said. Let me try to clarify:
>>
>> "For any reason, if community wants to run the GWT 2.8 SDK in Java 7
>> source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it
>> by supplying *a java7 compatible JRE emulation* without any compiler/SDK
>> changes *(but just setting the gwtc sourcelevel 7)*. That's why I didn't
>> originally remove Java7 option from the SourceLevel flag.
>> By removing the flag (which seems submitted now), the community will not
>> have that option *(i.e. they need also supply a modified compiler
>> together with the emulation)*."
>>
>> This may never happen but keeping the flag was cheap so I kept it.
>>
>> On Tue, Feb 16, 2016 at 11:35 PM, Manuel Carrasco Moñino <
>> man...@apache.org> wrote:
>>
>>> Removing the 1.7 flag does not make the compiler fail when using a java7
>>> sdk.
>>> Now the compiler always thinks that source code is sourced-level 1.8 so
>>> it does not fail when looking at java8 emul classes.
>>>
>>> You can still have the java.source property set to 1.7 when compiling
>>> your project and javac will validate that your code is java7 compliant,
>>> because javac process your client code.
>>>
>>> In summary javac and gwtc could use at the same time different source
>>> languages, but we always need to force gwtc to use 1.8 since new java8 api
>>> emul code.
>>>
>>>
>>> On Wed, Feb 17, 2016 at 2:32 AM, 'Goktug Gokdogan' via GWT Contributors
>>>  wrote:
>>>
 To remind the backlog of this:

 GWT 2.8 decided to support only Java8 source level (see related threads
 from last year) as the emulation will include Java 8 APIs which cannot be
 compiled in Java7 mode.

 However, GWT compiler itself is intended to be runnable in a Java 7
 JVM. This should enable slow-to-upgrade enterprises business to keep their
 legacy dev environments.
 For any reason, if community wants to run the GWT 2.8 SDK in Java 7
 source level, they can theoretically do it by supplying a java7 compatible
 JRE emulation without any compiler/SDK changes. That's why I didn't
 originally remove Java7 option from the SourceLevel flag.
 By removing the flag (which seems submitted now), the community will
 not have that option.

 (It is not import from Google side; just wanted to let you know if the
 community cares about it.)

 On Mon, Feb 15, 2016 at 5:12 AM, Thomas Broyer 
 wrote:

>
>
> On Monday, February 15, 2016 at 11:39:02 AM UTC+1, Thomas Broyer wrote:
>>
>>
>>
>> On Monday, February 15, 2016 at 10:06:47 AM UTC+1, Manuel Carrasco
>> Moñino wrote:
>>>
>>> Thomas, I want to experiment with this, pls, could you give me some
>>> advise what are the classes I have to look at?
>>>
>>
>> https://gwt-review.googlesource.com/14353
>> (currently running the testsuite locally)
>>
>
> Tests pass \o/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a96d8bde-37f5-4bdd-92f2-7fda3492cc94%40googlegroups.com
> 

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

['Daniel Kurka' via GWT Contributors]

Hi Michael,

you are probably missing adding all required source roots to the class
pathso that the compiler can find the .java .files.

If you go to your Run Configuration under Classpath, hit adavanced and add
all required folders

At least you should add:

dev/core/super/
user/src/
user/super/
user/test/
user/test-super/

Hope that helps,
Daniel




On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou 
wrote:

> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I
> want to run in Eclipse.
> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
> When I run the test as a JUnit test, I get:
>
> com.google.gwt.junit.JUnitFatalLaunchException: The test class
> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module
> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was
> seen
> at
> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>
> This seems to happen in any GWTTestCase I tried to run.
>
> I also see: Could not find the GWT compiler jarfile. Serialization errors
> might occur when accessing the persistent unit cache.
> from the Eclipse Console.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/d09b3d03-9111-4109-a735-e33b5c0630a3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipHqbc7jLOp77vH2w2go1wGH8_khSXSgLchSV0OwSFi6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

['Daniel Kurka' via GWT Contributors]

If you want to see the console output use a browser to do so, simply pass
this in your args:

-Dgwt.args='-runStyle Manual -style PRETTY -setProperty
compiler.stackMode=native -port 5454'

Once the test is compiled it will print a url that you can paste into any
browser and run the test there. This will also allow you to do debugging
directly in that browser


On Fri, Feb 12, 2016 at 7:42 PM Michael Zhou <zhoumotongxue...@gmail.com>
wrote:

> Hi Daniel,
>
> Is there a way to print / log stuff / debug when running a GWTTestCase in
> Eclipse? System.out.println() or breakpoints aren't working for me.
>
> Michael
>
> On Friday, February 12, 2016 at 7:47:38 AM UTC-5, Daniel Kurka wrote:
>
>> Hi Michael,
>>
>> you are probably missing adding all required source roots to the class
>> pathso that the compiler can find the .java .files.
>>
>> If you go to your Run Configuration under Classpath, hit adavanced and
>> add all required folders
>>
>> At least you should add:
>>
>> dev/core/super/
>> user/src/
>> user/super/
>> user/test/
>> user/test-super/
>>
>> Hope that helps,
>> Daniel
>>
>>
>>
>>
>> On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou <zhoumoto...@gmail.com>
>> wrote:
>>
>>> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I
>>> want to run in Eclipse.
>>> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
>>> When I run the test as a JUnit test, I get:
>>>
>>> com.google.gwt.junit.JUnitFatalLaunchException: The test class
>>> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module
>>> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was
>>> seen
>>> at
>>> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
>>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
>>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
>>> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
>>> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
>>> at junit.framework.TestCase.runBare(TestCase.java:134)
>>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>>> at junit.framework.TestResult.run(TestResult.java:113)
>>> at junit.framework.TestCase.run(TestCase.java:124)
>>> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
>>> at junit.framework.TestSuite.runTest(TestSuite.java:243)
>>> at junit.framework.TestSuite.run(TestSuite.java:238)
>>> at
>>> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>>>
>>> This seems to happen in any GWTTestCase I tried to run.
>>>
>>> I also see: Could not find the GWT compiler jarfile. Serialization
>>> errors might occur when accessing the persistent unit cache.
>>> from the Eclipse Console.
>>>
>>> --
>>> 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
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/d09b3d03-9111-4109-a735-e33b5c0630a3%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/d09b3d03-9111-4109-a735-e33b5c0630a3%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscrib

[gwt-contrib] GWT 2.8.0-beta1 available for testing

[Daniel Kurka]

Hi all,

we just finished testing for GWT 2.8.0-beta1. You can either download it 
from goo.gl/62SeR5 or from maven central.

Release notes can be found here 
.

Please start testing and let us know about any issues you encounter by 
either discussion here or filing bugs on github 
.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/2daed4d2-41df-44e9-b00e-25d1cec0e8c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Help testing the GWT 2.8 release

['Daniel Kurka' via GWT Contributors]

Hi all,

the GWT team needs help testing the GWT 2.8.1-beta1 release. As always,
before we publicize the release we are doing a bunch of DOA (dead on
arrival tests) before we open the release to the broader community.

Platforms that need testing:

   - Chrome (Linux or mac),
   - Window IE11,
   - Windows IE8
   - Window IE9
   - OSX safari
   - Firefox (Linux or mac)

We should have either chrome on mac and firefox on linux or the other way
around.

If you are interested in helping to test the release send me an email and
I'll share details with you!

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip5CCLiBTiZUVK%2BKkpRyZ1FWo3fj1x0N6Qe5ra1hP5UpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with GWT 2.5.1 + FF 40

[Daniel Kurka]

This has been fixed in GWT 2.7.0. We refactored the history implementation 
to not special case Firefox in this particular way. Just updating to GWT 
2.7 will fix this issue for you.

If that is not possible here is the main patch to make history work:
https://gwt-review.googlesource.com/#/c/5356/



On Friday, October 2, 2015 at 10:12:10 AM UTC+2, André wrote:
>
> Hello GWT users!
>
> We still use GWT 2.5.1 and can't update it quickly.
>
> Firefox v41 was released last week and came with this seemingly minor 
> modification 
> 
>  
> that makes our app unusable. Looks like this isn't compatible with GWT's 
> history implementation 
> 
> .
>
> Am I on the right track in that this is the root of our problem? Is it 
> possible to override the settings in History.gwt.xml 
> 
>  in 
> our own App.gwt.xml (preferrably in a way that it works across all FF 
> versions)?
>
> Thanks a lot in advance!
>
> André
>

-- 
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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] I think the 2.7.0 GWT release was compiled on Daniel Kurka's machine !

['Daniel Kurka' via GWT Contributors]

It's not my desktop machine, but you are right I did the final compilation
of the release. I thought we had already killed of gwttars anyway.

On Thu, Jul 2, 2015, 11:21 AM Arnaud TOURNIER ltea...@gmail.com wrote:

 Hi Daniel,

 I had a closer look to the thing. The paths mentionning your home account
 in google are stored in all the gwtar files in the gwt-user-2.7.0 artifact

 Does that really mean that the offical gwt releases are built on your
 desktop machine ?

 Thanks
 Arnaud

 Le mer. 1 juil. 2015 à 18:42, Arnaud TOURNIER ltea...@gmail.com a
 écrit :

 It's a project of one of my customers which is on gwt 2.6 and needs to
 migrate to 2.7.

 In the cours of doing that, i got this errors...

 If you need, i can investigate a bit more, but seems to be coming from
 those [ERROR] java.lang.String cannot be resolved to a class...

 Thanks
 ARnaud

 Le mer. 1 juil. 2015 à 18:20, 'Daniel Kurka' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com a écrit :

 Hi Arnaud,

 how are you producing these?

 -Daniel

 On Wed, Jul 1, 2015 at 9:06 AM Arnaud TOURNIER ltea...@gmail.com
 wrote:

 Just dumping a bit of errors i get for a project :

 Tracing compile failure path for type 'java.lang.Object'
 [INFO]   [ERROR] Errors in 'file:
 */usr/local/google/home/dankurka/gwt/user/super/co*
 m/google/gwt/emul/java/lang/Object.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/src/com/google/gwt/core/client/JavaScriptObject.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/super/com/google/gwt/emul/java/lang/Throwable.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/super/com/google/gwt/emul/java/lang/Class.java'

 There's no bug, nor problem on GWT side. I just found funny to get
 those kind of paths in a release artifact !!

 Thanks

 Arnaud

 --

 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.


 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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/SyRZzSQeDWg/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqP2rwYW9e2eqDUxL8qUA-5VKaGFbGi4bPS_-sNbGN3HA%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqP2rwYW9e2eqDUxL8qUA-5VKaGFbGi4bPS_-sNbGN3HA%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDncCZn1u3Pg%3DH%2B7AqZ0p%3Dcw5KADTmZx%2B3E2qeDEyttoCkQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDncCZn1u3Pg%3DH%2B7AqZ0p%3Dcw5KADTmZx%2B3E2qeDEyttoCkQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipFQmcmy0e_8QpR07r0BtTYnQ8aeX9Xu9RXiSGMsPLd4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] I think the 2.7.0 GWT release was compiled on Daniel Kurka's machine !

['Daniel Kurka' via GWT Contributors]

Hi Arnaud,

how are you producing these?

-Daniel

On Wed, Jul 1, 2015 at 9:06 AM Arnaud TOURNIER ltea...@gmail.com wrote:

 Just dumping a bit of errors i get for a project :

 Tracing compile failure path for type 'java.lang.Object'
 [INFO]   [ERROR] Errors in 'file:
 */usr/local/google/home/dankurka/gwt/user/super/co*
 m/google/gwt/emul/java/lang/Object.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/src/com/google/gwt/core/client/JavaScriptObject.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/super/com/google/gwt/emul/java/lang/Throwable.java'
 [INFO]  [ERROR] java.lang.String cannot be resolved to a type
 [INFO]   [ERROR] Errors in 'file:/usr/local/google/home/*dankurka*
 /gwt/user/super/com/google/gwt/emul/java/lang/Class.java'

 There's no bug, nor problem on GWT side. I just found funny to get those
 kind of paths in a release artifact !!

 Thanks

 Arnaud

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqP2rwYW9e2eqDUxL8qUA-5VKaGFbGi4bPS_-sNbGN3HA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 3 Build System

['Daniel Kurka' via GWT Contributors]

As a side note: We had a discussion to make j2cl be able to compile itself
to JavaScript. If that is actually done you can easily integrate with all
kinds of JavaScript build tools.

On Thu, Jun 18, 2015 at 1:16 PM Arnaud TOURNIER ltea...@gmail.com wrote:

 Hi everyone,

 I've been watching an reflecting upon the gwt meetup you had few weeks
 ago. And one of my concern is about a decent build system that gwt should
 be based upon. As for now, Bazel is not ready for Windows, and also it
 needs to be installed, configured and so on, which can be cumbersome and
 repulsive.

 So i came up with an idea, i'm sure you did have it already but in any
 case, i will submit it here :

 First, there a fact : GWT is moving towards the Web ecosystem, by being
 much easily and naturally integrated with the javascript world (and more to
 the point : ES6). This means that web projects will be mixes of javascript,
 java code, colsure, clojure, coffee and so on.

 So to follow this philosophy, i propose not to go to the Bazel direction
 but more to the Web direction which would mean using a build system like
 gulp or grunt.

 Did you examine such build tools when you reviewed decent ones ?

 And i've been trying gulp for a few weeks now, and i can tell :

  - it's very *fast*
  - it's *task based* (a bit like bazel), so conceptually it fits with the
 GWT requirements,
  - it can *watch files* for changes out-of-the-box
  - it is *modular*, and not a framework, more a set of available tools
 to build things.
  - it is able to launch any process, so of course it *can launch javac*
  - it is a *standard *in the web development world
  - since it is javascript, we could even *write gwt's gulp build tasks
 with gwt* ! (i think that it cannot be done straightforwardly with bazel)

 I think that this can prevent Java developpers from quitting GWT and it
 can also bring more pure Web developpers to GWT...
 It is also more consistent with the philosophy that GWT is embracing right
 now (IMHO)
 And it will also be more natural when needing to integrate a bit of Java
 code in a classic Web project.

 What do you think ?

 Thanks

 Arnaud

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/97962d74-18a5-4b27-8a05-ff8c6a4d55b8%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/97962d74-18a5-4b27-8a05-ff8c6a4d55b8%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip1cAtWqcBfBo6hEuB3Y%2BD3CLoE3MYtuzoisf7AQzt8Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 3 Build System

['Daniel Kurka' via GWT Contributors]

One other thing: It won't matter which system we use to build the new
compiler.

Google internal we always use our own build system and since its very close
to bazel it should work fine with bazel. If you want some kind of other
integration with other build systems you can easily build them since the
compiler will just be a taken the same arguments as javac anyway.

On Thu, Jun 18, 2015 at 2:04 PM Thomas Broyer t.bro...@gmail.com wrote:

 Gradle 2.5 will come with continuous build too (watch files, recompile
 incrementally on change -- and run tests I suppose, or restart running
 app); similar to what SBT has had for years now (but indescribably
 sluggish).

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/e005cdf7-9963-4fa7-8b7a-ee47a72e9ed9%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqrrQ99N0sNey%2Bh%3D1GG-v02vgC8AwOi%3Dp8-8ePp0VO-AA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Stop calling it GWT 3.0

['Daniel Kurka' via GWT Contributors]

Hi all,

thanks for sharing your views in this discussion.

Let me add a little background:

Currently we the GWT team have decided to work on a new fast transpiler
from Java to Closure (our internal enhanced version of JavaScript). This
makes sense for a lot of reasons that I won't go into detail on, but here
are a few:

- Our cross platform applications really want a faster and better
integration with closure.
- GWT and closure share a lot of work (optimizations) and this is a good
way to not reinvent the wheel constantly

So at some point we will open source this new compiler which will have some
compatibility with the old compiler, but it will not support everything
that GWT used to support.
It is not up to Google to decide if this should be GWT 3.0, but it is up to
the steering committee to decide (this is what the steering committee is
for).
However this new compiler works out, Google has tons of GWT applications
that would need to move from GWT 2.8 to whatever this new effort is, so
coming up with a common feature set and a migration plan is on our work
list, but we will focus on that once we actually have a new compiler.

However we already know that applications that only use a certain feature
set (which might grow, as people put in more work), should be fine on both
compilers (we should discuss this after the 2.8 release). We only talked
about this so early in the process to give the community the ability to
provide feedback on our efforts, but don't panic, nothing is set in stone
and we (the steering committee) need your input on this.

-Daniel



On Sun, Jun 14, 2015 at 4:51 PM Alain Ekambi jazzmatad...@gmail.com wrote:

 Also think of people who use GWT for non web based project.
 We use GWT  for example to create native mobile apps with Titanium. And
 our customers love the  UI Binder support.

 Dropping UI Binder means we wont be able to support new version of GWT.

 Such a bad move.

 On 14 June 2015 at 16:22, Travis Schmidt travis.schm...@gmail.com wrote:

 I have the same concerns as the last comment.  We are a java shop and use
 enterprise java for our back-end.  We have been using GWT for the last 9
 years to write thin front ends for our applications.  Basically GWT RPC and
 UiBinder are 99% of the code we deploy.  If I need to replace those with
 Polymer, Angular and some JSON XHR, then I don't see much need to use GWT
 going forward.  Am I mistaken or just misunderstanding something?

 On Sun, Jun 14, 2015 at 4:31 AM David david.no...@gmail.com wrote:

 I'm excited that you guys are planning a radical change (really). I hope
 it becomes more clear on what we should be using to future proof our apps.
 I hope we will get some usable preview of Singular (if that is really
 going to be a replacement).

 Somehow I am not totally concerned that we will need some major
 rewrites, it will be hard sell to management and it might mean that we need
 to look to different directions as well.

 But I am afraid that if GWT is no longer offering a complete solution
 like it does now (including a UI library, RPC support, i18n, UI binding,
 ... etc) that a lot of the advantage will be lost for me.

 As for naming, well it seems that non of the three letters still apply
 to the direction GWT is about to take.
 1) no longer in Google hands (or so they clame)
 2) Web not the main concern since the cross compiler is more to share
 code between web/android/ios apps.
 3) Toolkit ... it sounds more like a transpiler to me. Everything that
 made it a tooltip will be scrapped.




 On Sun, Jun 14, 2015 at 8:22 AM, Matic Petek maticpe...@gmail.com
 wrote:

 Hi,
  I'm also frustrated about which technologies to use on new GWT
 projects (see
 https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/_QSayBAmeX8
 ).
 But when it comes about the name, GWT should stay. The basic idea
 around GWT is writing code in Java which is then recompile (or whatever you
 call it / do it) into JavaScript. And this idea will stick with new GWT 3.0
 (it was also very clearly emphasis is one of the talks), so the name should
 stay.
 Regards,
   Matic


 On Saturday, June 13, 2015 at 11:03:08 AM UTC+2, Paul Robinson wrote:

 The GWT Meetup 2015 videos are very interesting.


 I can see why the proposals for GWT 3.0 have been made. However, we
 should be clear about the fact that GWT 3.0 is not just going to break a
 few little things that can easily be fixed, but break things to the point
 that it's a completely different product and there will be lots of GWT
 applications that will never be ported to the new system.


 It will be confusing to all GWT users to continue to use the name GWT
 3.0. It would be much better to use a new name for the new system and 
 treat
 it as what it is: a new idea about how Java can be used to build modern 
 web
 applications.


 The situation we have now is that GWT will end at 2.8 and a new thing,
 that is currently vapourware, will be coming that people are expected to
 use. There's 

Re: [gwt-contrib] A new library to integrate GWT with any CSS Framework

['Daniel Kurka' via GWT Contributors]

Hi Arnaud,

great work!

Have you considered using a APT generator instead of hooking into the
old GWT Generator API?

-Daniel

On Wed, Apr 1, 2015 at 11:08 AM, Arnaud TOURNIER ltea...@gmail.com wrote:
 Hello Everyone,

 I come up here to let you know about a library i build, aiming at
 integrating efficiently any CSS framework with GWT.

 This allows your application to type-safely use Sass, Less, Susy, GSS,
 vanilla css or any other.

 From the developper point of view, it works almost the same way as
 CssResource which is the default in GWT.

 Link : http://www.lteconsulting.fr/hexacss/

 Benefits :

  - you can use any css framework and not only GSS (especially Sass and Less
 have a very good variable and mixin systems)
  - you can bind multiple CSS files to one GWT application. This allows you
 to theme your application in a very effective way
  - you can then switch your application theme dynamically without reloading
 the application
  - there is still optimization happening : non used CSS classes will be
 pruned. Also there is name obfuscation, for reducing CSS file size
  - the API is very similar to CssResource so you don't have much to learn to
 use it.

 The product page is here : http://www.lteconsulting.fr/hexacss/
 The product page tells you how to use it, how to build it. It has three use
 case demos.
 The project is hosted on github : https://www.github.com/ltearno/hexa.tools

 Of course, it is open source and will stay so !

 Stay tuned, because i have other announcements to make soon

 Please tell me if you find the idea interesting and if it might help you. I
 also very much welcome anyone wishing to contribute to this project !

 Thanks

 Arnaud Tournier
 www.lteconsulting.fr
 twitter : @ltearno

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d3e08dc9-c6ee-4648-9234-eb8dee137745%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirghXxptfJ3KkSbhgfwPhb4GP_ss3ep%2BG47vpSofq2fyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] How to include changesets to an existing gerrit review?

['Daniel Kurka' via GWT Contributors]

You make the changes in your local git client and amend the commit: 'git
commit --amend'

Then you just push to gerrit: 'git push origin HEAD:refs/for/master' and
this will update the review.

On Mon, Mar 9, 2015 at 3:49 PM, Juan Pablo Gardella 
gardellajuanpa...@gmail.com wrote:

 Hi all,

 I've started a gerrit review and I have to add to add some improvements
 due some review observations. How I can include the changes in the same
 gerrit review?

 Thanks

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFsfGwo0sk_h2S9nTPwNUs6GQsd14Fk0n8uog04bBkwf4dQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFsfGwo0sk_h2S9nTPwNUs6GQsd14Fk0n8uog04bBkwf4dQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipqsX8temc_0%2B0MQj2kgppCJE2n67AhFv32tR2P_jeSZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] com.google.gwt.dev.SourceSaver cannot be compiled with java6

['Daniel Kurka' via GWT Contributors]

Yes the readme needs to be updated. Trunk does not support java6 anymore.
Mind sending a patch?

On Mon, Mar 2, 2015 at 3:38 PM, Juan Pablo Gardella 
gardellajuanpa...@gmail.com wrote:

 Hi team,

 I've just imported gwt-dev in Eclipse and I saw there is only one class
 that doesn't compile: *com.google.gwt.dev.SourceSaver*:


 line 213:try (InputStream resourceAsStream =
 Resources.asByteSource(resource).openStream();
  OutputStream out = dest.openForWrite(destPrefix + path);) {
   ByteStreams.copy(resourceAsStream, out);
  }

 If I change to the compiler compliance to 1.7 it works. Should the
 eclipse/README.txt be updated?

 eclipse/README.txt:
  Compiler settings 
 Window-Preferences-Java-Compiler
 Set the compiler compliance level to 1.6.

 Juan

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse3mu9hURYFcPGeFP5uCWgf-c1SM2DzEFSSVXs6m86qUg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse3mu9hURYFcPGeFP5uCWgf-c1SM2DzEFSSVXs6m86qUg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiociaeGBxnQA1DSXi9_Jot8Z4hNeF--iadUcY1mz6O5UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8: Turn GSS on by default

['Daniel Kurka' via GWT Contributors]

I agree with Goktug on this one. We can remove it from trunk right after we
created the 2.8 release branch, depending on how other things come together
(Java8, JSInterop v1) this should be in ~2 months. I think we are fine
letting the old code sit for that while.

I would suggest that we switch the default in trunk to gss and turn auto
conversion off to get the upgrade message.

-Daniel

On Mon, Feb 23, 2015 at 11:20 PM, 'Goktug Gokdogan' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 If we remove old css completely, that means we will force auto-conversion
 by the time of upgrade to 2.8. That will the make the upgrade
 unnecessarily harder (vs. upgrading 2.8 and choosing the time to the
 conversion if necessary). Besides, if they haven't upgraded and using
 auto-conversion, that is still not forcing migration, just leaves them with
 not-as-well-tested support of old css.
 Given that this is not buying as much, following the original plan to
 provide a clean transition version looks better to me at the moment. We
 can remove it all together after the 2.8 release.

 On Mon, Feb 23, 2015 at 10:18 AM, Jens jens.nehlme...@gmail.com wrote:

 I started migration today on a 300 KLOC project and all CSS files had
 been converted without any major issue using the Css2Gss tool. The only
 exotic issue I had was a NullPointerException for *.css files that do not
 have any content:
 https://code.google.com/p/google-web-toolkit/issues/detail?id=9131

 After conversion I was a bit annoyed updating all the @Source annotations
 still pointing to *.css files. You can't blindly run a global string
 replace of .css - .gss so this took some time.
 Also I did not add any gss=true attributes to UiBinder files because we
 simply have a lot of them and I don't want to do that work. I assume that
 this attribute is not needed anymore anyways once the GssResourceGenerator
 is enabled by default for UiBinder ui:style elements.

 Currently we run the app with CssResource.enableGss = true and 
 CssResource.conversionMode
 = strict and do not have any issues. Overall it took less than an hour
 to achieve that state.


 So I think I would prefer the second option (delete the property and make
 GSS the default everywhere) but it would be nice if GWT would prefer a
 matching *.gss file for any *.css file referenced in @Source annotations
 (may the css file exist or not on disk) and print a warning in which
 ClientBundles that occurred. That way people could execute the Css2Gss tool
 and can start using 2.8. Deleting css files and cleaning up @Source
 annotations can then be done afterwards in smaller steps.


 -- J.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/8efa270c-e7fa-4337-9e46-60d25e393e05%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/8efa270c-e7fa-4337-9e46-60d25e393e05%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA04acEEqBEP5LRO0qfdxGnXFS6GJEOtuEVAwYjv%3DZUr3w%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA04acEEqBEP5LRO0qfdxGnXFS6GJEOtuEVAwYjv%3DZUr3w%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipPPXb%3DoZ6bqKZypjYZXC5E8uOTin%3DjWWC7EFdgZ1xDoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Javascript Exceptions in SDM about classes not being defined

['Daniel Kurka' via GWT Contributors]

This looks like the same compiler bug we are currently investigating, for
now you can clear your SDM cache (button on its page) and you should be
able to continue.

On Tue, Feb 10, 2015 at 7:16 AM, Ali Akhtar ali.rac...@gmail.com wrote:

 I'm using 2.8.0-SNAPSHOT, from
 https://github.com/manolo/gwt-snapshot/raw/master/

 When I try to invoke the following method:

public ClerkD setEvents(HasValue?... fields)
 {
 for (HasValue? f : fields)
 {
 f.addValueChangeHandler( e - validate() );
 }
 return this;
 }

 I get the following exception:

 com.google.gwt.core.client.JavaScriptException: (ReferenceError) :
 Lcom_google_gwt_user_client_ui_HasValue_2_classLit_0_g$ is not defined

 Any ideas what's going on here? The code compiles, I have the classes on
 classpath, but I still see that exception.

 In fact, lately I've been getting a lot of these 'xxx_classLit_0_g$ not
 defined' exceptions in SDM. E.g:

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

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

 It seems that using any random class in GWT can cause that exception to
 come up. Which doesn't make sense as I'm writing valid code that compiles.

 Am I doing something wrong, or is this a bug in the compiler?

 Would greatly appreciate if any light can be shed on this.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/83b0b1f8-f8a7-4997-8426-62804e286adf%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/83b0b1f8-f8a7-4997-8426-62804e286adf%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirarjkVZiL-KXu735kWtSuiRQdMiQFVaWVwXgq75_AB5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] What constitutes an acceptable emulated String.format implementation?

['Daniel Kurka' via GWT Contributors]

Hi Benjamin,

thanks for reaching out to us. Answers are inline.

On Sat, Feb 7, 2015 at 5:31 AM, Benjamin DeLillo bpd9...@gmail.com wrote:

 For an implementation to be accepted would it have to conform to the entire 
 Java Formater spec? 
 http://docs.oracle.com/javase/7/docs/api/java/util/Formatter.html

 I think supporting the entire java spec is impossible since we do not have
Locale working (for codesize reasons). So we would need to discuss what a
good subset would be



 Would an implementation lacking the Date/Time conversions be acceptable?

 Would an implementation that wraps sprintf.js be acceptable (if the licensing 
 is compatible)? https://github.com/alexei/sprintf.js

 I briefly skimmed the lib and it seems huge, so I am inclined to say no.
In general you have to think about that any application will have the hit
of that method in their app as soon as they call String.format one time in
their code base.



 What about a minimal positional substitution implementation and nothing more?


Right now any code that relies on String.format will not compile in GWT and
thus give the author a clear indication of having a problem. Once we
support a subset this compile error might be gone, but we will be
introducing runtime errors for not supported features rather than compile
time errors.

One could try to deal with these (and this is bad from the compiler
perspective), by looking at the parameters of String.format and only allow
statically resolvable arguments for the format String that are supported by
the emulation, but this is a very tight coupling of compiler and lib that
we do not want in the compiler.

So if we want to do a minimal support of String.format these are the kinds
of problems we need to discuss.



  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/bc6afdc0-eb87-4815-b076-6db912f8f94c%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/bc6afdc0-eb87-4815-b076-6db912f8f94c%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujir_g5%2BZhbDbF_CnbHdKyfKAYomz9%2B9x3asZvu0O7vGQKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Where do I find my password for gerrit?

['Daniel Kurka' via GWT Contributors]

Here is how you do it:

1. Go to http://gwt-review.googlesource.com
2. Upper left corner press on the arrow right of our login name
3. Press preferences
4. Press HTTP Password
5. Press Obtain password

-Daniel

On Mon, Feb 9, 2015 at 2:47 PM, Richard Wallis rdwal...@gmail.com wrote:

 Thanks for the help.

 I've contributed before, so everything is setup.  I just need the password
 (Is this not possible?).

 It's a bit too much to ask Windows users to install cygwin, I'll setup a
 vm if it's not possible to get a password.

 Julien, I've read through the slides and they seem to have the same info
 as the contribution guide.

 On Mon, Feb 9, 2015 at 3:18 PM, Julien Dramaix julien.dram...@gmail.com
 wrote:

 Richard,

 You could find interesting information on how to contribute by reading
 the documents we've written for the contributor workshop at gwtcreate
 this year:
 Preparation step for the workshop: http://goo.gl/F4pk0V
 Workshop slides:
 https://docs.google.com/presentation/d/11W6b4JCKB3N1-EuaGRORyLkSNOJuW47Q8ArMs4NjkQg/pub?start=falseloop=falsedelayms=3

 Julien

 On Mon Feb 09 2015 at 1:59:31 PM Richard Wallis rdwal...@gmail.com
 wrote:

 Hi, trying to submit a patch and I can't authenticate.

 I go to https://gwt.googlesource.com

 I click generate password and I get instructions on how to generate a
 cookie on a Unix system.  I'm on Windows.

 I have signed the contributor agreement. Can I submit my patch via
 github?

 --
 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
 .
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/c3b6c72f-ccea-
 4d5a-afa1-5146d23b39e7%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c3b6c72f-ccea-4d5a-afa1-5146d23b39e7%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5A0QKy86AweYGvoVSRCibKsbfKSneiCmPgX5tGeCosag%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5A0QKy86AweYGvoVSRCibKsbfKSneiCmPgX5tGeCosag%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVjCJJtNDO1eDa-0BaRaz%2B0%2B4xQ3UBv2%3DE6Sp5EGdCkgMQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVjCJJtNDO1eDa-0BaRaz%2B0%2B4xQ3UBv2%3DE6Sp5EGdCkgMQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujioMGcq_JeY4N1Okav0qXuDzFyFoR1otekc%3DspPott94VA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Singular (Angular for crossplatform) talk at GWT.create

[Daniel Kurka]

Hi all,

here is me talking about Singular at GWT.create: 
http://gwtcreate.com/videos/index.html#singular

-Daniel

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

Re: [gwt-contrib] Compile error with latest gwt (from trunk)

['Daniel Kurka' via GWT Contributors]

Are you sure that there is not another version of GWT somewhere in the
classpath?

On Tue, Feb 3, 2015 at 12:09 PM, Stefano Pulze stefano.pulz...@gmail.com
wrote:

 Hi folks,

 Today I've updated and build latest gwt from trunk.
 I've tried to compile my project but the compilar said:

 Caused by: java.lang.NoSuchMethodError: com.google.gwt.dev.jjs.ast.
 JThisRef.getClassType()Lcom/google/gwt/dev/jjs/ast/JClassType;
  at com.google.gwt.dev.jjs.impl.CloneExpressionVisitor.visit(
 CloneExpressionVisitor.java:317)
  at com.google.gwt.dev.jjs.ast.JThisRef.traverse(JThisRef.java:48)
  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
  ... 54 more
   [ERROR] at Enum.java(109): this
  com.google.gwt.dev.jjs.ast.JThisRef
   [ERROR] at Object.java(79): this$static
  com.google.gwt.dev.jjs.ast.JParameterRef
   [ERROR] at Object.java(79): Impl.getHashCode(this$static)
  com.google.gwt.dev.jjs.ast.JMethodCall
   [ERROR] at Enum.java(109): Object.$hashCode(this)
  com.google.gwt.dev.jjs.ast.JMethodCall
   [ERROR] at Enum.java(109): return Object.$hashCode(this)
  com.google.gwt.dev.jjs.ast.JReturnStatement
   [ERROR] at Enum.java(108): {
   return Object.$hashCode(this);
 }
  com.google.gwt.dev.jjs.ast.JBlock
   [ERROR] at Enum.java(108): {
   return Object.$hashCode(this);
 }
  com.google.gwt.dev.jjs.ast.JMethodBody
   [ERROR] at Enum.java(108): public final int hashCode();
  com.google.gwt.dev.jjs.ast.JMethod


 Is my fault?
 The same project with gwt 2.7.0 work fine.

 Thanks in advanced

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ead534db-45c4-4f7f-af21-5642b440d95b%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ead534db-45c4-4f7f-af21-5642b440d95b%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiq17QMXJFgceFMi0eFUQDTBhdzC49G4Qh%2BR_6wvOeBgfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

['Daniel Kurka' via GWT Contributors]

Hi Luca,

we are intentionally not deploying right now, but we will eventually sort
this out. I am sorry but we do not have an ETA for that.

-Daniel

On Sun, Feb 1, 2015 at 9:20 PM, luca.masini luca.mas...@gmail.com wrote:

 Can someone take the time to fix the problem with the CI system that
 prevent the jar to be created and uploaded ?

 Thank you.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/0ddc1e55-2f2b-4a36-b5a0-ce089c4420d9%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/0ddc1e55-2f2b-4a36-b5a0-ce089c4420d9%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrj6sJR60YFGVMMGDtYVYuaNF45aWU8mcfpWzAGbQAtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Build server is down

['Daniel Kurka' via GWT Contributors]

This is a known thing and we can't change that for a short period of time.

On Sat, Jan 24, 2015 at 12:56 AM, Thomas Broyer t.bro...@gmail.com wrote:

 Update: it's not down (as it built this night), just unreachable.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/a0eec484-ad99-49fa-a81b-3a10520c62d3%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirZZFhRd7OT8TZWRFcGD2kru79TDc5U2M1Pkq-WtmEQ0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Generators vs java annotation processing

['Daniel Kurka' via GWT Contributors]

I will be presenting something around that at GWT.create -
 http://gwtcreate.com/#agenda-us_room1_event9
http://gwtcreate.com/#agenda-us_room1_event9

On Wed, Jan 21, 2015 at 3:20 PM, Thomas Broyer t.bro...@gmail.com wrote:

 GWT itself won't run annotation processors (yet), but if your IDE runs
 them automatically on file save then it should work just as well as GWT
 generators.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10371fb-5d57-4a26-8c1b-74a4d726e4e9%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujioGi6Z_ogZTHSjEEPa1AQrA9_2%2BnSFfph%2BCF964vzF9Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Incremental Scheduler can be about 10% faster

['Daniel Kurka' via GWT Contributors]

I think we do not want to make any assumptions about runtime of any tasks
since this would not work well with task that have variable runtime.

If you need to do heavy calculations since browser APIs have evolved a lot
you should be using web workers anyway.

On Wed, Jan 14, 2015 at 11:57 AM, Richard Wallis rdwal...@gmail.com wrote:

 At the moment, incremental scheduler runs a repeating task in a while loop
 that checks if its duration has exceeded 16ms and then returns control to
 the browser.

 If you assume that an incrementally scheduled task will tend to run in
 about the same time as it did before then you can get about a 10% speed up
 by counting the number of times the task ran during the last duration loop
 and then running the task that many times at the start (and skipping the
 duration check).

 On chrome a task that calculated the fibonacci sequence managed to
 calculate about 45 numbers in a second with the current scheduler and
 about 50 numbers in the same time with my new one below.

 And a realworld task that parses xml dropped from taking about 50 seconds
 each run to 42 seconds.

 Of course if the incrementally scheduled task tends to take a longer and
 longer time to complete on each run the oprimization might cause issues so
 maybe we need to create a new kind of task scheduler specifically for tasks
 that tend to complete their runs in a similar timeframe.

 I'm looking for critiscim of the code below, (and maybe someone to take
 ownership of this and do a PR to gerrit on my behalf)

 In SchedulerImpl replace the current runRepeatingTasks method with this:
 (lastLoopCount is a private int field);

   /**
* Execute a list of Tasks that hold RepeatingCommands.
*
* @return A replacement array that is possibly a shorter copy of
 codetasks/code
*/
   private JsArrayTask runRepeatingTasks(JsArrayTask tasks) {
 assert tasks != null : tasks;

 int length = tasks.length();
 if (length == 0) {
   return null;
 }

 boolean canceledSomeTasks = false;

 Duration duration = createDuration();
 int loopCount = 0;
 outer: while (duration.elapsedMillis()  TIME_SLICE) {

 if (length == 1) {
 while (lastLoopCount--  0 ) {
  if (!tasks.get(0).executeRepeating()) {
   tasks.set(0, null);
   canceledSomeTasks = true;
   break outer;
  }
  loopCount += 1;
 }
 }
   boolean executedSomeTask = false;
   for (int i = 0; i  length; i++) {
 assert tasks.length() == length : Working array length changed 
 + tasks.length() +  != 
 + length;
 Task t = tasks.get(i);
 if (t == null) {
   continue;
 }
 executedSomeTask = true;

 assert t.isRepeating() : Found a non-repeating Task;

 if (!t.executeRepeating()) {
   tasks.set(i, null);
   canceledSomeTasks = true;
 }
 loopCount += 1;
   }
   if (!executedSomeTask) {
 // no work left to do, break to avoid busy waiting until
 TIME_SLICE is reached
 break;
   }
 }
 if (length == 1) {
 lastLoopCount = loopCount;
 }

 if (canceledSomeTasks) {
 lastLoopCount = 0;
   JsArrayTask newTasks = createQueue();
   // Remove tombstones
   for (int i = 0; i  length; i++) {
 if (tasks.get(i) != null) {
   newTasks.push(tasks.get(i));
 }
   }
   assert newTasks.length()  length;
   return newTasks.length() == 0 ? null : newTasks;
 } else {
   return tasks;
 }
   }

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/80297aa7-c49a-4e3b-b70a-554bfaef52f0%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/80297aa7-c49a-4e3b-b70a-554bfaef52f0%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipuOFMxCnLjdM_FER4n3-eAHPEWUQGf3AZENR_ezq255A%40mail.gmail.com.
For more options, visit 

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

['Daniel Kurka' via GWT Contributors]

I am really curious why this is not working for you in the first place.

Since the code we added to SDM should always scope you down to one
permutation. Are you still using bookmarklets? (These do not deal with this
properly and should not be used anymore).

On Thu, Dec 4, 2014 at 3:43 PM, Rob Walker piste.shred...@googlemail.com
wrote:

 OK - I know I'm being exceptionally dumb here, but won't that also limit a
 production build to that 1 permutation?


 On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote:

  The mappings file only reports what was going on in the compile phase,
 so modifying it has no effect.

 You have to set specific values for your properties in the module.xml
 files:
 e.g.
 
 set-property name=user.agent value=safari/
 

 SDM picks this change up I believe without restart. However to see the
 change in the mappings file too, you have to clean and recompile (i.e.
 start your devserver).



 On 04/12/14 15:02, Rob Walker wrote:


 I'm seeing this file in the artefacts generated by the SDM compile in the
 temp dir. Isn't editing this file only going to apply to the current
 invocation though?

 Presumably next time around it's going to get a different temp dir, and
 this fill will get recreated again.

 Have to confess - I don't fully follow what this file does though, and
 why we need to manually edit it

 On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote:

  @thomas

 thank you, that helped me to reduce the permutations to one.

 For the record, compilation-mappings.txt contained multiple cache.js
 file entries, now it only contains one
 
 FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js

 Devmode:devmode.js
 
 ...and now sdm works.

 And it's fast :-)


 On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote:

 Hi,

  Is there a way to see which properties cause the permutations?
 (I'm using GWT 2.7.0)


  When compiling your project, you should have
 a compilation-mappings.txt file generated next to the *.nocache.js.


   --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqzLC%3D7bfeqfC3KWL2U%2Bxd_WJTZE8_Jzck4oRxgQh4Twg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT 2.7.0 is here

[Daniel Kurka]

Today we are excited to announce the GWT 2.7.0 release.  Thanks to everyone 
who contributed to this release, especially our non-Google open source 
contributors.

One major feature of this release is a new super fast compilation path in 
Super Dev mode that replaces the old dev mode.
For a run-down of all changes since GWT 2.6.1, read the release notes 
http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0.

The release is available for download here 
http://www.gwtproject.org/download.html or on maven central.

If you find any issues with this release, please file a bug in our issue 
tracker.

Daniel,
on behalf of the GWT team at Google

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

Re: [gwt-contrib] SDM memory footprint

['Daniel Kurka' via GWT Contributors]

Hi Nicolas,

Having no-op recompiles taking ~30s is very uncommon, even on our large
projects this never exceeds 1s. Right now there is not much you can do to
trim down memory usage for SDM. It really needs this amount of memory. Also
keep in mind that SDM slows down a lot if it comes close to the memory
limit. Some internal apps saw huge speed improvements for doubling their
RAM used.

The easiest solution on your part is getting more memory for your machines,
since all engineering (like splitting up into multiple modules) comes with
extra complexity (we do not handle recompile on reload for multiple modules
right now if I am correct).

We will eventually work on memory consumption, since some internal apps
need up to 10 GB to work in SDM, but this work is not high priority and
will unlikely land any time soon. I would strongly recommend getting more
physical memory otherwise you will not have a productive working
environment.

-Daniel


On Sun, Nov 16, 2014 at 11:23 AM, Nicolas Morel nmr.mo...@gmail.com wrote:

 Hi,

 I'm currently trying to migrate a big project at work from GWT 2.5.1 to
 2.7.0 to test the new SDM.

 Even if the recompile took 1-2 min on 2.5.1, the SDM was working with
 -Xmx 1200m. It is already a lot of memory but was manageable.

 Now with 2.7.0-rc1, I have to increase it to -Xmx 1800m to avoid an OOM.
 Besides some bugs (https://github.com/ArcBees/GWTP/issues/614 or
 https://code.google.com/p/google-web-toolkit/issues/detail?id=4479), the
 incremental recompilation without modification works but it is still slow
 (~ 30 sec).
 The memory needed is too much for my machine, I keep swapping to a very
 slow disk :( And since we all have the same crappy laptop at work, the
 problem will be present for everyone working on this project.

 I guess the bump in memory is needed for the incremental compile to work
 correctly but what are the best ways to reduce it ?

 The project is not modular with a clean separation between client and
 server. So the SDM has all the libraries of the server in the classpath.
 If we split the client from server and reduce the classpath, can we expect
 a decrease in memory usage ? Or classes not used by the GWT module have no
 impact ?

 One of our RPC services uses Serializable so it generates a lot of code.
 Can it have an impact on memory usage too ?

 If that doesn't work, our only solution left is to divide in multiple GWT
 module and make something like turducken
 http://fr.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams
  ?



  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4224704c-fc8c-493c-8f7a-b8c93357503e%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4224704c-fc8c-493c-8f7a-b8c93357503e%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipJhY8q1SNrL5%2BYB-2JLv9wWnTBe_jABgYDxofxkw2iVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run any GWTTestCase

['Daniel Kurka' via GWT Contributors]

On the run rght now, but john merged a patch in that area yesterday, can
you try reverting that one?

On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com
wrote:

 I've updated my master branch (of the GWT-core project) the with the
 remote and now I'm not able to run any GWT test cases included in the
 project. I receive first this error:


 java.lang.NoSuchFieldError: VOID
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239)
 at
 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286)
 at
 org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99)
 at
 com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384)
 at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470)
 at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499)
 at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 Then each test case fails with:
 java.lang.NullPointerException
 at
 com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 I'm sure something is wrong locally but I don't see what. Any hint ?

 Julien

 --
 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
 javascript:_e(%7B%7D,'cvml','google-web-toolkit-contributors%2bunsubscr...@googlegroups.com');
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D66%3DKJkw6JW%3D4Lyk%2BPNkD6z_PMyqQp2zW%3D9ggVTjoVDrA%40mail.gmail.com
 

Re: [gwt-contrib] Not able to run any GWTTestCase

['Daniel Kurka' via GWT Contributors]

Deleted all unit caches?
On Nov 14, 2014 1:10 PM, Julien Dramaix julien.dram...@gmail.com wrote:

 I have this problem for several days in fact. It's why I think the problem
 is on my side.

 On Fri Nov 14 2014 at 1:05:30 PM 'Daniel Kurka' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 On the run rght now, but john merged a patch in that area yesterday, can
 you try reverting that one?

 On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com
 wrote:

 I've updated my master branch (of the GWT-core project) the with the
 remote and now I'm not able to run any GWT test cases included in the
 project. I receive first this error:


 java.lang.NoSuchFieldError: VOID
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239)
 at
 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286)
 at
 org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99)
 at
 com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384)
 at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470)
 at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499)
 at
 com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at
 com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 Then each test case fails with:
 java.lang.NullPointerException
 at
 com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at
 com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 I'm sure something is wrong locally but I don't see what. Any hint ?

 Julien

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

Re: [gwt-contrib] SDM in 2.7.0-rc1 doesn't support inclusion in 3rd party sites

['Daniel Kurka' via GWT Contributors]

Can you take a look at this and let me know if this helps you out?

https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap

On Mon, Nov 3, 2014 at 11:45 AM, Tal Shani tsh...@gmail.com wrote:

 Hi,

 I am writing a GWT generated JS script that is hosted by several sites.
 2.7.0 introduced a breaking change in the code server.
 Until 2.7.0, I could test my code using a bookmarklet that injects the
 script into any site referring to SDM URLs,
 Now this is not possible anymore,
 I have opened an issue:
 https://code.google.com/p/google-web-toolkit/issues/detail?id=8970
 And also tested the suggested solution by compiling my own gwt-dev and
 codeserver.

 Is there any objections to the suggested flow? or better suggestions?

 (sadly it will take time for me to do the whole cla process)

 Tal

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/dba4f2de-9579-49db-8e42-9cdd1472867c%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/dba4f2de-9579-49db-8e42-9cdd1472867c%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqN-FDMaRZKY8Kj%2BY2rc4nZ9%2BGaZc2ZtUW1J-H-vp7KdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available

['Daniel Kurka' via GWT Contributors]

You are comparing apples and oranges here. SDM compiles are not optimized,
thus much bigger. If you want to compare performance you will need to do an
optimized compile.

The SDM setup in my blog post is now outdated, here is how you use SDM with
Phonegap in 2.7:
https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap

-Daniel


On Fri, Oct 31, 2014 at 8:01 AM, confile michael.gorsk...@googlemail.com
wrote:

 I use iOS7 and Super dev mode as described by Daniel here
 http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html. I
 use -strict -XjsInteropMode JS and output style detailed to compile the
 code for the PhoneGap container.



 Am Freitag, 31. Oktober 2014 01:02:58 UTC+1 schrieb Ray Cromwell:

 I am not aware of any changes in 2.7 that should effect performance
 loading images. Are you running on iOS7 or iOS8? Daniel would probably
 be best able to help you. Are you talking about SuperDevMode loading
 performance, or fully optimized compile loading performance?



 On Thu, Oct 30, 2014 at 2:27 PM, confile
 michael@googlemail.com wrote:
  I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to GWT
  2.7beta. Here are my experience. I feel that loading of data especially
  images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on an
  iPhone 5. Due to the delay in loading the app feels slow and scrolling
 does
  not work smouth.
 
  Michael
 
 
 
  Am Donnerstag, 30. Oktober 2014 16:37:38 UTC+1 schrieb Jens:
 
  Turning off precompile in incremental mode.
  Super Dev Mode starting up
 workDir:
  /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp

 
 
  Does this mean anything? Is it a problem if precompile is turned off
 or
  does it mean that incremental compile is not working?
 
 
  That's fine. Precompilation is turned off intentionally as it can
  sometimes cause SDM to not detect just a single permutation.
 
  -- J.
 
  --
  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.
  To view this discussion on the web visit
  https://groups.google.com/d/msgid/google-web-toolkit-
 contributors/9574bc95-abd7-4c08-bf6d-58f20c2fa6f3%40googlegroups.com.
 
  For more options, visit https://groups.google.com/d/optout.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/91c19564-b5ae-41d6-a23b-903f24296a7d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/91c19564-b5ae-41d6-a23b-903f24296a7d%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip3Y15SsrRC5owSqA_f7aF6uEnT1FVXvTpdUXigMeMzCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available

['Daniel Kurka' via GWT Contributors]

Are you comparing prod compiles or SDM compiles?

On Fri, Oct 31, 2014 at 10:22 AM, confile michael.gorsk...@googlemail.com
wrote:

 Hi Daniel,

 this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is
 what I did. Super dev mode is working. I get a recompile after reload that
 is working.

 In my app I have a long list with images. When I scroll down the app
 freezes when the scrolling reaches a point where new images have to be
 loaded from the server. The loading feels very slow it took more than 10
 seconds. During this time the app is completely blocked. I compared the
 same app running in the same environment except that i switched to GWT
 2.6.1. In GWT 2.6.1 it runs so mouth no blocking while scrolling. I am not
 sure what changed in GWT 2.7 that causes this effect, but I suppose that
 other people might have similar problems too. By the way I use the latest
 version of MGWT and GWT-PhoneGap.

 Michael


 Am Freitag, 31. Oktober 2014 09:06:11 UTC+1 schrieb Daniel Kurka:

 You are comparing apples and oranges here. SDM compiles are not
 optimized, thus much bigger. If you want to compare performance you will
 need to do an optimized compile.

 The SDM setup in my blog post is now outdated, here is how you use SDM
 with Phonegap in 2.7: https://github.com/mgwt/
 mgwt/wiki/SuperDevMode-with-PhoneGap

 -Daniel


 On Fri, Oct 31, 2014 at 8:01 AM, confile michael@googlemail.com
 wrote:

 I use iOS7 and Super dev mode as described by Daniel here
 http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html. I
 use -strict -XjsInteropMode JS and output style detailed to compile the
 code for the PhoneGap container.



 Am Freitag, 31. Oktober 2014 01:02:58 UTC+1 schrieb Ray Cromwell:

 I am not aware of any changes in 2.7 that should effect performance
 loading images. Are you running on iOS7 or iOS8? Daniel would probably
 be best able to help you. Are you talking about SuperDevMode loading
 performance, or fully optimized compile loading performance?



 On Thu, Oct 30, 2014 at 2:27 PM, confile
 michael@googlemail.com wrote:
  I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to
 GWT
  2.7beta. Here are my experience. I feel that loading of data
 especially
  images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on
 an
  iPhone 5. Due to the delay in loading the app feels slow and
 scrolling does
  not work smouth.
 
  Michael
 
 
 
  Am Donnerstag, 30. Oktober 2014 16:37:38 UTC+1 schrieb Jens:
 
  Turning off precompile in incremental mode.
  Super Dev Mode starting up
 workDir:
  /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-
 7573159147938212004.tmp
 
 
  Does this mean anything? Is it a problem if precompile is turned
 off or
  does it mean that incremental compile is not working?
 
 
  That's fine. Precompilation is turned off intentionally as it can
  sometimes cause SDM to not detect just a single permutation.
 
  -- J.
 
  --
  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.

  To view this discussion on the web visit
  https://groups.google.com/d/msgid/google-web-toolkit-contrib
 utors/9574bc95-abd7-4c08-bf6d-58f20c2fa6f3%40googlegroups.com.
 
  For more options, visit https://groups.google.com/d/optout.

  --
 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
 .
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/91c19564-b5ae-
 41d6-a23b-903f24296a7d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/91c19564-b5ae-41d6-a23b-903f24296a7d%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c7a4b31e-a355-4f13-9fe1-a4b3a6077a18%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c7a4b31e-a355-4f13-9fe1-a4b3a6077a18%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available

['Daniel Kurka' via GWT Contributors]

prod = production = optimized.

SDM in incremental code does not do any optimizations. Normal GWT compiles
optimize a lot.

On Fri, Oct 31, 2014 at 10:36 AM, confile michael.gorsk...@googlemail.com
wrote:

 @Daniel Sorry for my stupid question but what is the difference? How do I
 do prod compiles or SDM compiles?



 Am Freitag, 31. Oktober 2014 10:32:39 UTC+1 schrieb Daniel Kurka:

 Are you comparing prod compiles or SDM compiles?

 On Fri, Oct 31, 2014 at 10:22 AM, confile michael@googlemail.com
 wrote:

 Hi Daniel,

 this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is
 what I did. Super dev mode is working. I get a recompile after reload that
 is working.

 In my app I have a long list with images. When I scroll down the app
 freezes when the scrolling reaches a point where new images have to be
 loaded from the server. The loading feels very slow it took more than 10
 seconds. During this time the app is completely blocked. I compared the
 same app running in the same environment except that i switched to GWT
 2.6.1. In GWT 2.6.1 it runs so mouth no blocking while scrolling. I am not
 sure what changed in GWT 2.7 that causes this effect, but I suppose that
 other people might have similar problems too. By the way I use the latest
 version of MGWT and GWT-PhoneGap.

 Michael


 Am Freitag, 31. Oktober 2014 09:06:11 UTC+1 schrieb Daniel Kurka:

 You are comparing apples and oranges here. SDM compiles are not
 optimized, thus much bigger. If you want to compare performance you will
 need to do an optimized compile.

 The SDM setup in my blog post is now outdated, here is how you use SDM
 with Phonegap in 2.7: https://github.com/mgwt/m
 gwt/wiki/SuperDevMode-with-PhoneGap

 -Daniel


 On Fri, Oct 31, 2014 at 8:01 AM, confile michael@googlemail.com
 wrote:

 I use iOS7 and Super dev mode as described by Daniel here
 http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html. I
 use -strict -XjsInteropMode JS and output style detailed to compile the
 code for the PhoneGap container.



 Am Freitag, 31. Oktober 2014 01:02:58 UTC+1 schrieb Ray Cromwell:

 I am not aware of any changes in 2.7 that should effect performance
 loading images. Are you running on iOS7 or iOS8? Daniel would
 probably
 be best able to help you. Are you talking about SuperDevMode loading
 performance, or fully optimized compile loading performance?



 On Thu, Oct 30, 2014 at 2:27 PM, confile
 michael@googlemail.com wrote:
  I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to
 GWT
  2.7beta. Here are my experience. I feel that loading of data
 especially
  images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on
 an
  iPhone 5. Due to the delay in loading the app feels slow and
 scrolling does
  not work smouth.
 
  Michael
 
 
 
  Am Donnerstag, 30. Oktober 2014 16:37:38 UTC+1 schrieb Jens:
 
  Turning off precompile in incremental mode.
  Super Dev Mode starting up
 workDir:
  /var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-
 7573159147938212004.tmp
 
 
  Does this mean anything? Is it a problem if precompile is turned
 off or
  does it mean that incremental compile is not working?
 
 
  That's fine. Precompilation is turned off intentionally as it can
  sometimes cause SDM to not detect just a single permutation.
 
  -- J.
 
  --
  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+unsubscribe@
 googlegroups.com.
  To view this discussion on the web visit
  https://groups.google.com/d/msgid/google-web-toolkit-contrib
 utors/9574bc95-abd7-4c08-bf6d-58f20c2fa6f3%40googlegroups.com.
 
  For more options, visit https://groups.google.com/d/optout.

  --
 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+unsubscribe@
 googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/91c19564-b5ae-41d6-a23b-
 903f24296a7d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/91c19564-b5ae-41d6-a23b-903f24296a7d%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

  --
 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
 .
 To view this discussion on the web visit https://groups.google.com/d

Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working

['Daniel Kurka' via GWT Contributors]

I added a tracking item for updating SDM docs before 2.7.0

On Fri, Oct 31, 2014 at 8:00 AM, Matic Petek maticpe...@gmail.com wrote:

 Jens,
   Thank you. Now it's working. SDM documentation should really be updated
 - http://www.gwtproject.org/articles/superdevmode.html
 Regards,
   Matic

 On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote:

 Instead of -workDir you should use -launcherDir which contains all public
 resources (from your public folders) as well as the generated nocache.js
 file. -workDir is just for temporary files for each recompile.

 If you use DevMode class instead of CodeServer then the DevMode class
 configures -launcherDir to the same value as DevMode -war.


 -- J.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4ed14921-e5b5-49e8-9426-ebb22a967b21%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/4ed14921-e5b5-49e8-9426-ebb22a967b21%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipdrM%2BA1KPm6vrmzVYpU-XnJRCdBQE2b9MkZw3KA_5kKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7.0 RC1 available

[Daniel Kurka]

There is no need to start the codeserver directly anymore, its now started 
by default when you launch the old dev mode.
And you do not need to use the bookmarklets in that mode anymore. It just 
recompiles automatically.

See: https://www.youtube.com/watch?v=qpCSbj36O44


On Thursday, October 30, 2014 7:29:47 PM UTC+1, Matt Wallis wrote:

 On 30/10/2014 16:38, Matt Wallis wrote: 
  
  However, if I add a new source file, it is not found by incremental 
  compilation. 
 Update: Now I can't repeat this, having added another new source file. 


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

Re: [gwt-contrib] Cell widgets and GSS

['Daniel Kurka' via GWT Contributors]

I think we should not provide these files as of yet. If someone wants to
make the transition right now they can easily use the converter with these
files and convert them to gss themselves.
I think we want to make that transition once GSS is default (or about to be
default) inside of Google as a testing ground.

-Daniel

On Thu, Oct 30, 2014 at 3:51 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

 If GSS was the default, we would have shipped only .gss files.
 What I want is to provide the .gss files for people using GSS and want to
 override some style class of cell widgets. We have this case at Arcbees
 where css guys want to use their existing mixins to style CellTable.



 On Wed Oct 29 2014 at 6:49:46 PM 'Goktug Gokdogan' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 The original idea to make the GSS default was to ship .gss files next to
 .css files and let the generator automatically use the file with the gss
 extension.
 We can probably ship the gss files but I think it is optional at this
 point.

 On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix julien.dram...@gmail.com
  wrote:

 Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm
 wondering if we shouldn't provide GSS files for all existing CssResource
 interfaces present in GWT. The idea is to keep the associated .css files
 and use them by default but also to provide GSS files in order that people
 can use GSS to style their widgets.

 Let take the cell widgets (CelTable, CellList...) as example. If you
 want to override default style, you do something like:

 public interface TableResources extends CellTable.Resources {
 interface Style extends CellTable.Style {
 }

 @Override
 @Source({ CellTable.Style.DEFAULT_CSS, css/table.css})
 Style cellTableStyle();
 }

 In this case, it's impossible to use GSS because you cannot mix .css and
 .gss files on the same resource. So the only mean to use GSS is to first
 convert manually the default css file to gss and include it in your
 application or start from scratch.

 So I would like that GWT provides these gss files that user can use in
 their @Source annotations in order to override the default style.

 What do you guys think ?


 Julien

 --
 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
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6To8pLn%3D0EmgLRQdByrx_m0-CURafkr7FhZRMwxGXbqg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3wT52nZHx-9BZ3PcgjXAXMaPQZLdD4gJcnb%2BJpAsOxhw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7vYxNejFdDC1jZnDHe-ft6xjsrP39jT%2Bf0zCnpgxVsxQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipc1i4hYFt%3D8Oan%3DfFDjspvFk6uYbOuYk-YJXC4Ce3R6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT 2.7.0 RC1 available

['Daniel Kurka' via Google Web Toolkit]

Hi all,

I just build the GWT 2.7.0 RC1 and pushed it to maven central. The complete
SDK is also available from here http://goo.gl/npqEUR.

Please start testing and let us know if you run into any trouble. You can
either reply to this thread on gwt-contrib
https://groups.google.com/forum/#!forum/google-web-toolkit-contributors
 or file a bug https://code.google.com/p/google-web-toolkit/issues/entry.

We are planing to release this as GWT 2.7.0 if we do not here about any
serious issues within the next two weeks. The release notes
http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1 for
RC1 will be made available shortly after this notice, in the mean time you
can take a look at the review for the release notes
https://gwt-review.googlesource.com/#/c/10031/.

Daniel,
on behalf of the GWT team

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

[gwt-contrib] GWT 2.7.0-RC1 is available

['Daniel Kurka' via GWT Contributors]

Hi all,

I just build the GWT 2.7.0 RC1 and pushed it to maven central. The complete
SDK is also available from here http://goo.gl/npqEUR.

Please start testing and let us know if you run into any trouble. You can
either reply to this thread on gwt-contrib
https://groups.google.com/forum/#!forum/google-web-toolkit-contributors or
file a bug https://code.google.com/p/google-web-toolkit/issues/entry.

We are planing to release this as GWT 2.7.0 if we do not here about any
serious issues within the next two weeks. The release notes
http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1 for
RC1 will be made available shortly after this notice, in the mean time you
can take a look at the review for the release notes
https://gwt-review.googlesource.com/#/c/10031/.

Daniel,
on behalf of the GWT team

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujioAdKOHQv1nx4%2BSN7Ajj0paortL2ANDzuf_7YAwKzxzOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7.0-RC1 Smoke testing update

['Daniel Kurka' via GWT Contributors]

Hi all,

the smoke testing for the release showed up a couple of problems, some of
them need to be fixed before we put RC1 out others can wait until the final
release.



   - Dev mode test do not work: issue 8967
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8967
   - Smoke tests fail with GPE since gwt-codeserver.jar is missing on the
   classpath. We need to either modify GPE or put codeserver classes into
   gwt-dev
   - GWT designer crashes: see screenshot
   https://drive.google.com/file/d/0B-K8EZ6jAAQrVzdweDhiTE5iQlU/view
   - JSON Sample does not work since the yahoo search returns a 404

Can somebody please take a look at updating the JSON Sample to use a
different service for the actual search?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiptX2h5qZ7DJg0XiZqbAGMfJJX_m8jT4%2BVDA9z1%3DeEF1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

['Daniel Kurka' via GWT Contributors]

Hi all,

right now GWT builds with RC1 are failing in Eclipse with GPE since the
gwt-codeserver.jar is not on the build path. The next GPE release (with
changes that fix this) is still a long way out. In order to not be blocking
on this I propose we fold gwt-codeserver.jar into gwt-dev.jar.

This way people do not have to deal with the extra complexity of adding yet
another entry into the classpath and all the old tools just work.

If I do not hear any objections as of today, I go ahead and change the OS
build (I could need some help here). So please speak up.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqxC1b4UCn-N-FNRSLkaUzSUJF%3DEgJKXWE3A30Mh9OFkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

['Daniel Kurka' via GWT Contributors]

I think moving sources right now is too risky and too much work we should
just merge the jars in dist.

On Tue, Oct 28, 2014 at 8:02 PM, Thomas Broyer t.bro...@gmail.com wrote:

 Fine for me.

 Do you intend to move the sources or just merge the JARs during
 dist-dev/dist?

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/2649c79a-bc32-472e-9410-81401fe73de1%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiq25ZHfMsk4cDrnGNE54Wfhvv%2BNEB0YSSZenxyNEv-5Jw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Help with testing GWT 2.7 RC1

['Daniel Kurka' via GWT Contributors]

Hi all,

we are looking for help with testing GWT 2.7 RC1.

We are in need of people testing the release on these platforms (others are
already covered):

- Windows 7/8, IE10
- some Windows, IE8

Please reach out to me directly if you want to get involved.

-Daniel


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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqAKZrx1swV29wA7xC9O9x%3DU3pgBqL7owhyHF%3DcA%3Dx%3DVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['Daniel Kurka' via GWT Contributors]

Hi Jeremie,

what do you mean by 15s reload? Does the compiler take 15s to detect that
you do not have a change? (this would be bad).

-Daniel

On Tue, Oct 21, 2014 at 10:44 AM, Jérémie Gottero jeremiegott...@gmail.com
wrote:

 It works like a charm, thanks. I still have ~15sec of compilation to
 reload the page even when nothing has changed, but I guess it would be
 faster with a ssd drive.


 Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :

 With GWT 2.7 you do not need any bookmarklet stuff anymore. You can just
 bring it up through the old dev mode integration in eclipse, see:

 https://www.youtube.com/watch?v=qpCSbj36O44

 PS: You do not need the -superDevMode anymore its now default.

 On Mon, Oct 20, 2014 at 3:38 PM, Jérémie Gottero jeremie...@gmail.com
 wrote:

 Hello,
 I have tried GWT 2.7 beta today, and first of all you guys made an
 awesome job to reduce compile time (x4/5 faster on my 500k LoC project).
 There is however a CodeServer behavior that I don't understand: why the
 precompile flag is always turned off in incremental mode?

 if (incremental  !noPrecompile) {
   System.out.println(Turning off precompile in incremental mode.);
   noPrecompile = true;
 }

 In my dev env, I never use the DevMode On/Off bookmarklets: I always
 load js files from the CodeServer url, and I wrote a small GWT utility
 class to display a recompile button which is embedded in my app UI (it
 does the same thing as the bookmarklet, ie calling
 codeserverurl/recompile). It's easier to use for others devs: no need to
 explain them the bookmarklet stuff, they just have to launch the
 CodeServer. With 2.7 I can't use this trick anymore: I need the bookmarklet
 to do a first compilation to be able to load my app. Is there a reason to
 prevent precompilation in incremental mode?

 Regards,
 Jeremie

 --
 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
 .
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/46bc27ce-d8a3-
 40ad-9629-b2c6d3bfe961%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/46bc27ce-d8a3-40ad-9629-b2c6d3bfe961%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/de430b92-1afd-4843-8b24-83b33ae3179c%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/de430b92-1afd-4843-8b24-83b33ae3179c%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirhXgbCvzMVVptKir204o_fRxYGMdGPu2tdffvkC6Sh%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['Daniel Kurka' via GWT Contributors]

These times are incredible slow. The worst I have seen was around 700ms for
a huge chunk of code. Normally these times are around ~100ms.

Something is seriously wrong. Lets try a couple of things:

1. Up the ram of SDM to see if this makes any difference.
2. Are there any other things running on your system that make it slow
(lots of other disk IO, other heavy cpu tasks?)
3. How much source code are we talking here (LOC, files)?

-Daniel

On Tue, Oct 21, 2014 at 11:23 AM, Jérémie Gottero jeremiegott...@gmail.com
wrote:

 Yes, that was 15sec to detect that nothing has changed. But after some
 tries, I actually got better times (~3sec). See logs below, I got 12sec at
 first then 3sec. I suspect that my app server load somehow impacts compile
 time. Should definitely be a problem on my side.

 GET /recompile/adminfront
Job com.exalead.mercury.admin.ui.AdminFront_1_0
   starting job: com.exalead.mercury.admin.ui.AdminFront_1_0
   Compiling module com.exalead.mercury.admin.ui.AdminFront
  Ignored 22 units with compilation errors in first pass.
 Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
 errors.
  Unification traversed 148143 fields and methods and 10734 types.
 10695 are considered part of the current module and 10695 had all of their
 fields and methods traversed.
  Compiling 1 permutation
 Compiling permutation 0...
 Linking per-type JS with 10679 new types.
prelink JS size = 30989214
prelink sourcemap = 30989214 bytes and 708768 lines
postlink JS size = 30934781
postlink sourcemap = 30934781 bytes and 707368 lines
 Source Maps Enabled
  Compile of permutations succeeded
  Compilation succeeded -- 43,734s
   Linking into
 D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\war\adminfront;
 Writing extras to
 D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-2\extras\adminfront
  Link succeeded
  Linking succeeded -- 5,735s
 *  52,810s total -- Compile completed*
 GET /recompile/adminfront
Job com.exalead.mercury.admin.ui.AdminFront_1_1
   starting job: com.exalead.mercury.admin.ui.AdminFront_1_1
   skipped compile because no input files have changed
 *  12,201s total -- Compile completed*
 GET /recompile/adminfront
Job com.exalead.mercury.admin.ui.AdminFront_1_2
   starting job: com.exalead.mercury.admin.ui.AdminFront_1_2
   skipped compile because no input files have changed
 *  2,807s total -- Compile completed*
 [...]
 GET /recompile/adminfront
Job com.exalead.mercury.admin.ui.AdminFront_1_5
   starting job: com.exalead.mercury.admin.ui.AdminFront_1_5
   Compiling module com.exalead.mercury.admin.ui.AdminFront
  Ignored 22 units with compilation errors in first pass.
 Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
 errors.
  Unification traversed 585 fields and methods and 460 types. 9 are
 considered part of the current module and 9 had all of their fields and
 methods traversed.
  Compiling 1 permutation
 Compiling permutation 0...
 Linking per-type JS with 9 new types.
prelink JS size = 13769
prelink sourcemap = 13769 bytes and 338 lines
postlink JS size = 30934783
postlink sourcemap = 30934783 bytes and 707368 lines
 Source Maps Enabled
  Compile of permutations succeeded
  Compilation succeeded -- 3,147s
   Linking into
 D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\war\adminfront;
 Writing extras to
 D:\ng\src\jgottero\svn\mercury\mercury-adminui\trunk\tmp\com.exalead.mercury.admin.ui.AdminFront\compile-7\extras\adminfront
  Link succeeded
  Linking succeeded -- 1,753s
 *  8,204s total -- Compile completed*
 GET /recompile/adminfront
Job com.exalead.mercury.admin.ui.AdminFront_1_6
   starting job: com.exalead.mercury.admin.ui.AdminFront_1_6
   skipped compile because no input files have changed
 *  2,782s total -- Compile completed*

 Jeremie

 Le mardi 21 octobre 2014 10:48:54 UTC+2, Daniel Kurka a écrit :

 Hi Jeremie,

 what do you mean by 15s reload? Does the compiler take 15s to detect that
 you do not have a change? (this would be bad).

 -Daniel

 On Tue, Oct 21, 2014 at 10:44 AM, Jérémie Gottero jeremie...@gmail.com
 wrote:

 It works like a charm, thanks. I still have ~15sec of compilation to
 reload the page even when nothing has changed, but I guess it would be
 faster with a ssd drive.


 Le lundi 20 octobre 2014 16:51:19 UTC+2, Daniel Kurka a écrit :

 With GWT 2.7 you do not need any bookmarklet stuff anymore. You can
 just bring it up through the old dev mode

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

['Daniel Kurka' via GWT Contributors]

You can not create a JSO using new in Java. If this has worked with GWT
2.6.1 it is just a bug and should not have worked in the first place.

-Daniel

On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes janthe...@gmail.com wrote:

 Hello guys,

 we're in the process of trying out GWT 2.7 in our massive application.
 Currently we get an error during compile for one module. It worked with
 GWT 2.6.1.
 Any ideas on this one? I'm not sure but the problem might be that we can't
 create a JSO using new ..Jso().
 But the big question is why did this work in GWT 2.6.1?

 [ERROR] Errors in
 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java'

   [ERROR] Line 38: Rebind result
 'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot
 be a JSO


 Cheers,

 Jan

 Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka:

 Hi all,

 since we are adding major features to GWT, we decided to change our
 release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven
 central and our file storage http://goo.gl/pr7km3.
 We are doing this beta to get external feedback on incremental
 compilation and GSS.

 Incremental compilation is now default with GWT 2.7 and replaces,
 together with Super dev mode, the regular old dev mode. Inside of Google we
 are already using it for a while now and most of the issues should have
 already been dealt with, however we also want to make sure that external
 users that might have slightly different use cases will have a working
 2.7.0 release.

 So please start testing with beta1 and give us lots of feedback on the 
 contributor
 list
 https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors
 or on the issue tracker
 https://code.google.com/p/google-web-toolkit/issues/list. Please keep
 in mind that we did not do any release testing on beta1, so there might be
 issues that you do not expect from a release candidate.

 Our current plan is to wait until the end of next week for any feedback.
 If we do not find any serious external issues we will start the testing
 process for an actual release candidate.

 -Daniel

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirA57TxELe3AbjSX5Ui%3DzteH%2B2_got4%3DwrywHAYGRxQcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

['Daniel Kurka' via GWT Contributors]

With GWT 2.7 you do not need any bookmarklet stuff anymore. You can just
bring it up through the old dev mode integration in eclipse, see:

https://www.youtube.com/watch?v=qpCSbj36O44

PS: You do not need the -superDevMode anymore its now default.

On Mon, Oct 20, 2014 at 3:38 PM, Jérémie Gottero jeremiegott...@gmail.com
wrote:

 Hello,
 I have tried GWT 2.7 beta today, and first of all you guys made an awesome
 job to reduce compile time (x4/5 faster on my 500k LoC project).
 There is however a CodeServer behavior that I don't understand: why the
 precompile flag is always turned off in incremental mode?

 if (incremental  !noPrecompile) {
   System.out.println(Turning off precompile in incremental mode.);
   noPrecompile = true;
 }

 In my dev env, I never use the DevMode On/Off bookmarklets: I always load
 js files from the CodeServer url, and I wrote a small GWT utility class to
 display a recompile button which is embedded in my app UI (it does the
 same thing as the bookmarklet, ie calling codeserverurl/recompile). It's
 easier to use for others devs: no need to explain them the bookmarklet
 stuff, they just have to launch the CodeServer. With 2.7 I can't use this
 trick anymore: I need the bookmarklet to do a first compilation to be able
 to load my app. Is there a reason to prevent precompilation in incremental
 mode?

 Regards,
 Jeremie

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/46bc27ce-d8a3-40ad-9629-b2c6d3bfe961%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/46bc27ce-d8a3-40ad-9629-b2c6d3bfe961%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiquq13TMWDQdwjgvgA5%3DmkGOxigZLeoiBRdXPNZAdNtiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: odd super dev mode times

['Daniel Kurka' via GWT Contributors]

Stephen can you verify that this solved your problem and if so cherry pick
it to the branch and add me as a reviewer?

On Mon, Oct 20, 2014 at 10:02 PM, 'John Stalcup' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I think it's in master now
 (commit 14f27064497f1171907d0ecbe01a4d2991a7a855)

 On Sun, Oct 19, 2014 at 7:51 PM, Stephen Haberman 
 stephen.haber...@gmail.com wrote:


  depends on how many files are modified [+ invalidations]

 Yeah, sorry, I should have mentioned I've only been changing one file,
 just adding/removing a character in a string.

  John detected that behavior in the persistent unit cache and has a
  fix for it.

 Great! I'll try it out when it hits master.

 - Stephen

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141019215142.6e6e53f1%40sh9
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ-j4KGj%3DG-sSda%2Bei9M3X%2BDx4%2BzZGW2joogbjoRkSe-Sg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ-j4KGj%3DG-sSda%2Bei9M3X%2BDx4%2BzZGW2joogbjoRkSe-Sg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujir3f3Vch5ER6QGD6Ji9XWQdSToecoUaTH2gDkWZFO9W8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: odd super dev mode times

['Daniel Kurka' via GWT Contributors]

I think that CL is only on master. Thats why I said try master and if it
works send me a cherry pick for the CL :)

On Tue, Oct 21, 2014 at 12:26 AM, Stephen Haberman 
stephen.haber...@gmail.com wrote:


  However, right, it didn't actually make it into 2.7-beta1.

 Crap. Eclipse was lying to me, and had a 2.6.x source jar hooked up to
 gwt-dev-2.7-beta1.jar (don't ask) when I pulled up PersisentUnitCache
 in my project to check for the change.

 So: a) 2.7-beta1 does have John's 14f2706 fix, and b) even trying with
 a locally built snapshot of release/2.7, the behavior is still
 happening.

 I'll spend quality time with the debugger tonight and try and see
 what's going on. (But if a CL were to magically hit master before then,
 I would not mind that either.)

 - Stephen

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141020172605.0c3895aa%40sh9
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqnW8wQXFND7f%3Dqkop1Ehgj2C7PwZymYsBhVPPMDK6NHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7.0 beta1

['Daniel Kurka' via GWT Contributors]

Hi all,

since we are adding major features to GWT, we decided to change our release
process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our
file storage http://goo.gl/pr7km3.
We are doing this beta to get external feedback on incremental compilation
and GSS.

Incremental compilation is now default with GWT 2.7 and replaces, together
with Super dev mode, the regular old dev mode. Inside of Google we are
already using it for a while now and most of the issues should have already
been dealt with, however we also want to make sure that external users that
might have slightly different use cases will have a working 2.7.0 release.

So please start testing with beta1 and give us lots of feedback on the
contributor
list
https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors
or on the issue tracker
https://code.google.com/p/google-web-toolkit/issues/list. Please keep in
mind that we did not do any release testing on beta1, so there might be
issues that you do not expect from a release candidate.

Our current plan is to wait until the end of next week for any feedback. If
we do not find any serious external issues we will start the testing
process for an actual release candidate.

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiraD7n4CS17O9YYhVt8BsJ4QFV83Z9qvAQDGpeyPxh2NA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Maven release process broken

['Daniel Kurka' via GWT Contributors]

Hi all,

apparently sonatype now verifies that all jar files have a sources.jar
associated with them. Our build does not do that for gwt-servlet.jar.

To be able to push out beta1 I settled on a nasty hack, see:
https://gwt-review.googlesource.com/#/c/9774/

I think we need to change the way the gwt-servlet.jar is build / we push
jars to maven.

@Thomas, @Manolo can you guys take a look?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirZ64hyKNNur1sk%2BR7QsGW0QYYWRM1ro9z9PcOQDXUjqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Java6 compatibility broken due to UiBinder change for GSS

['Daniel Kurka' via GWT Contributors]

Hi all,

currently GWT does not build with Java6 (not even the release build: ant
elemental dist), because of this change:
https://gwt-review.googlesource.com/#/c/9620/

@Colin, @Arthur can you guys take a look together with Julien?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirju_SpP5kMJ4QG79skraX-xq9jynOB6JWHaCWeDqBenw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Change packaging for GSS

['Daniel Kurka' via GWT Contributors]

Hi all,

apparently we ended up packaging gss into gwt-dev instead of gwt-user:
https://gwt-review.googlesource.com/#/c/9803/

@Thomas, @Julien can you guys look into providing a patch that moves this
into gwt-user?

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipLY9ydhxTG0__D0vVojSpuCGQAmLb1aD-rPOBz1Me62A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

['Daniel Kurka' via GWT Contributors]

)

 at
 com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)

 at com.google.gwt.dev.Compiler.main(Compiler.java:125)

 On Saturday, October 18, 2014 10:54:40 AM UTC-7, Daniel Kurka wrote:

 Hi all,

 since we are adding major features to GWT, we decided to change our
 release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven
 central and our file storage http://goo.gl/pr7km3.
 We are doing this beta to get external feedback on incremental
 compilation and GSS.

 Incremental compilation is now default with GWT 2.7 and replaces,
 together with Super dev mode, the regular old dev mode. Inside of Google we
 are already using it for a while now and most of the issues should have
 already been dealt with, however we also want to make sure that external
 users that might have slightly different use cases will have a working
 2.7.0 release.

 So please start testing with beta1 and give us lots of feedback on the 
 contributor
 list
 https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors
 or on the issue tracker
 https://code.google.com/p/google-web-toolkit/issues/list. Please keep
 in mind that we did not do any release testing on beta1, so there might be
 issues that you do not expect from a release candidate.

 Our current plan is to wait until the end of next week for any feedback.
 If we do not find any serious external issues we will start the testing
 process for an actual release candidate.

 -Daniel

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/880dfdec-4884-4f51-905b-b3672e0e01c6%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/880dfdec-4884-4f51-905b-b3672e0e01c6%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujioZZYP6PfZShVs42zQHmao8QKBToutJDqSAhdL1HqnmkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Maven release process broken

['Daniel Kurka' via GWT Contributors]

oops was still a draft, now its okay.

On Sat, Oct 18, 2014 at 8:34 PM, Brandon Donnelson branflake2...@gmail.com
wrote:

 The patch link provided is bad.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/5697ce4d-4250-4e06-81ad-90dbef174407%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/5697ce4d-4250-4e06-81ad-90dbef174407%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiopftORJAKD6%3DKavz29%2BuXpguW9im5hvUwq2Aj8HJgWeA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Authentication issues

['Daniel Kurka' via GWT Contributors]

Did you sign the CLA on the gerrit web interface?

-Daniel

On Fri, Oct 17, 2014 at 9:31 PM, Scott Morgan sc...@adligo.com wrote:

 Hi,

 Ok I had issues with the ~/.netrc file, which never authenticated me.
 So I removed it to get command line user/password dialogs which did this;

 (Replaced my username as X)
 [gwt@localhost trunk]$ git push origin HEAD:refs/for/master
 Username for 'https://gwt.googlesource.com': X
 Password for 'https://x...@gwt.googlesource.com':
 fatal: remote error:  A Contributor Agreement must be completed before
 uploading.

 However I have signed a A Contributor Agreement and it was accepted, can
 someone at google fix this?

 I also tried my email as the user name, but it failed earlier in the
 authentication process.

 I have also emailed this to the person who accepted the agreement.

 Cheers,
 Scott

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d6d649c9-a19b-4c77-bbcd-dcdac18e7ceb%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d6d649c9-a19b-4c77-bbcd-dcdac18e7ceb%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqzciLOKix8oobiBTn%3D%3DFde4i0fO7hsp8ddGUHn6DA2xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GssParserException

['Daniel Kurka' via GWT Contributors]

Did you update your svn tools dir?

On Mon, Oct 13, 2014 at 8:51 AM, Stefano Pulze stefano.pulz...@gmail.com
wrote:

 Hi,

 I've a problem with GssParserException when try compile from GWT trunk
 version.
 I've download latest GWT trunk versione from the web and start to
 compiling with ant buildonly but the compiler says


 https://lh4.googleusercontent.com/-gwxn7hoHFaM/VDt1p-VleII/A00/BdQcGpLECXc/s1600/11.PNG
 Have I wrong something?
 Thanks :)

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c8619542-f837-413a-bd3a-ff1879a20615%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c8619542-f837-413a-bd3a-ff1879a20615%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujio1Z5xrP_KJJ%2BUNw3c%3DShA7-8TXWtx%2B56%2B2Srv9qg4FNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7 remaining actions - Invitation to view

['Daniel Kurka (via Google Sheets)' via GWT Contributors]

I've shared an item with you:

GWT 2.7 remaining actions
https://docs.google.com/spreadsheets/d/17enrlrtsmdJTX7nTumJJwCyJkas8kF8TddvbWH7-Ebw/edit?usp=sharing

It's not an attachment -- it's stored online. To open this item, just click  
the link above.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/089e0160b674086d2a050524a771%40google.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

[Daniel Kurka]

We are making steady progress towards GWT 2.7. At this point we are not 
accepting any new patches, but we still have a list of issues that we would 
like to include in the upcoming release. This is no guarantee that all of 
them are going to make it but we are trying our best. Also we are holding 
off committing any risky patches to master until we have cut the GWT 2.7 
release branch. I'll ping back GWT contributors once we have done that. 
Please do not commit any patches that do not need to go in.


   - Issue 8762 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8762: 
   Migration to android.json from org.json not being complete (Current patch). 
   Deploy a com.google.gwt.org.json version based of android that the GWT SDK 
   can depend on and update the pom of the SDK to use it. Include a warning in 
   the release notes about small the very small incompatibilities between the 
   two.
   - Issue 8613 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8613: 
   Bug fix for ValuePicker
   - Issue 8619 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8619: 
   Super dev mode can fail to start on windows if previous dirs are still 
   locked. SDM will skip deletion of dirs on windows if it fails and emit a 
   warning. (skybrian)
   - Issue 8716 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8716: 
   Package names can collide with class names on case insensitive file system. 
   John will come up with a fix for GWT 2.7 if it is not to hard to do 
   (stalcup).
   - Issue 8938 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=8938: 
   GWT RPC base url is not set correctly for all cases in SDM recompiles. 
   dankurka will update the implementation to include a full computeScriptBase 
   implementation.
   - GWT RPC policy files should be written to -launcherDir so that the 
   normal server can use them easily (skybrian)
   - verify sample apps are actually compiling in SDM (since it is now 
   default) (dankurka)
   - remove generation of SDM targets in samples since it is now default 
   (skybrian)
   - John found two small issues in incremental. These need to be fixed for 
   GWT 2.7 (stalcup  rluble)
   - Exception links in the chrome dev tools are not clickable (goktug)
   - Issue 4236 
   https://code.google.com/p/google-web-toolkit/issues/detail?id=4236: 
   NavigatableMap: We would like to include this in GWT 2.7, but it needs more 
   testing. Ask Andrei to copy all apache testcases and make them work, then 
   we include it in GWT 2.7 (goktug)
   - Removing IE6 references in the code base (niloc)


-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/82aff1f3-92ba-491c-ac10-20ab2fa3610f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

['Daniel Kurka' via GWT Contributors]

I think this call is up to the elemental maintainers (manolo  thomas), if
it breaks any tests I will roll it back since we need a green build to be
able to branch.

-Daniel

On Thu, Oct 9, 2014 at 6:57 PM, 'Brian Slesinsky' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I think this is okay as long as it doesn't cause tests to fail. Elemental
 is quite separate from everything else so it seems low risk. Daniel?


 On Thu, Oct 9, 2014 at 8:57 AM, Leif Åstrand legi...@gmail.com wrote:

 Lots of Elemental patches have been merged in the last few days, but we
 do still have a short list that would be nice to get included.

 https://gwt-review.googlesource.com/#/c/9098/
 https://gwt-review.googlesource.com/#/c/9099/
 https://gwt-review.googlesource.com/#/c/9095/

 The code appears to be in good shape, so it only remains for someone with
 appropriate authority to decide whether the changes are wanted.

 On Thursday, 9 October 2014 16:25:37 UTC+3, Daniel Kurka wrote:

 We are making steady progress towards GWT 2.7. At this point we are not
 accepting any new patches, but we still have a list of issues that we would
 like to include in the upcoming release. This is no guarantee that all of
 them are going to make it but we are trying our best. Also we are holding
 off committing any risky patches to master until we have cut the GWT 2.7
 release branch. I'll ping back GWT contributors once we have done that.
 Please do not commit any patches that do not need to go in.


- Issue 8762
https://code.google.com/p/google-web-toolkit/issues/detail?id=8762:
Migration to android.json from org.json not being complete (Current 
 patch).
Deploy a com.google.gwt.org.json version based of android that the GWT 
 SDK
can depend on and update the pom of the SDK to use it. Include a warning 
 in
the release notes about small the very small incompatibilities between 
 the
two.
- Issue 8613
https://code.google.com/p/google-web-toolkit/issues/detail?id=8613:
Bug fix for ValuePicker
- Issue 8619
https://code.google.com/p/google-web-toolkit/issues/detail?id=8619:
Super dev mode can fail to start on windows if previous dirs are still
locked. SDM will skip deletion of dirs on windows if it fails and emit a
warning. (skybrian)
- Issue 8716
https://code.google.com/p/google-web-toolkit/issues/detail?id=8716:
Package names can collide with class names on case insensitive file 
 system.
John will come up with a fix for GWT 2.7 if it is not to hard to do
(stalcup).
- Issue 8938
https://code.google.com/p/google-web-toolkit/issues/detail?id=8938:
GWT RPC base url is not set correctly for all cases in SDM recompiles.
dankurka will update the implementation to include a full 
 computeScriptBase
implementation.
- GWT RPC policy files should be written to -launcherDir so that the
normal server can use them easily (skybrian)
- verify sample apps are actually compiling in SDM (since it is now
default) (dankurka)
- remove generation of SDM targets in samples since it is now
default (skybrian)
- John found two small issues in incremental. These need to be fixed
for GWT 2.7 (stalcup  rluble)
- Exception links in the chrome dev tools are not clickable (goktug)
- Issue 4236
https://code.google.com/p/google-web-toolkit/issues/detail?id=4236:
NavigatableMap: We would like to include this in GWT 2.7, but it needs 
 more
testing. Ask Andrei to copy all apache testcases and make them work, then
we include it in GWT 2.7 (goktug)
- Removing IE6 references in the code base (niloc)


 -Daniel

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/b8d11950-f32a-466a-b748-036622710c70%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/b8d11950-f32a-466a-b748-036622710c70%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT9X18-yHWp370JRRnfndkfuW1PRoPZyjJgSi-xgRis3Aw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT9X18-yHWp370JRRnfndkfuW1PRoPZyjJgSi-xgRis3Aw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

[Daniel Kurka]

Hi all,

summarizing the discussion I just had with Julien: We want to have the in 
memory conversion in GWT 2.7 (even if it is not battle tested yet), since 
this is the way to move foward. We can even do a followup release (2.8) as 
soon as google is using it in production and we sorted all issues out.

If GSS is turned on we will:

 - We will make a decision which generator to use based on file extension
 - You can not mix gss / css on the same interface
 - In UiBinder we will add a new attribute to tell that this interface 
needs gss (default css)
 - If lib has gss in it the app using that lib needs to have it enabled.

I think there is good value in including this in GWT 2.7 since we can ask 
for external feedback as well, while at the same time making sure its 
mature within google.

-Daniel



On Tuesday, October 7, 2014 8:55:27 AM UTC-7, Goktug Gokdogan wrote:

 I didn't take notes in the meetup so I cannot recall all the reasons 
 (perhaps someone else did?) but I think one of the reasons to introduce in 
 memory conversion was to get rid of the CSS generator code with the GSS 
 release and another one was the possible complications of coexisting css 
 and gss in the same page (e.g. name collisions).

 Given that we cannot get rid of the CSS generator in 2.7 and if you think 
 everything would be fine with css/gss mixed together (e.g. with prefixes), 
 I'm totally fine with kicking in-memory conversion out and it is definitely 
 not required for 2.7 even if we decide to keep it.

 However, arguably there might be still value in having an experimental 
 flag to enable GSS as it is not well tested yet.

 On Tue, Oct 7, 2014 at 1:37 AM, Julien Dramaix julien@gmail.com 
 javascript: wrote:

 I think we are making the things too complex. Initially, we wanted to 
 remove the code of the existing generator for the CssResource and 
 deprecated the existing syntax. It's why we have introduced the in-memory 
 automatic conversion.

 Now, we've decided to keep the existing generator in GWT 2.7. So I think 
 that we had better to remove this automatic conversion and choose the right 
 generator in fonction of the file extension. People that want to use GSS 
 have to use files with .gss extension. Old files with .css extension will 
 continue to work because the current generator will be used for these kind 
 of files. For the uibinder, we add a temporary attributes (and/or we can 
 foreseen an configuration property that enable GSS by default in UiBinder.)

 That simplify a lot the implementation, removes three configuration 
 properties (CssResource.enableGss, CssResource.legacy, 
 CssResource.conversionMode) and we support all uses cases of application 
 using third party libraries that will result of a mix of GSS and CSS. So 
 it's simpler for the user and simpler for us.

 In the next release of GWT, when we remove the code for the existing 
 generator, we 
 will be able to reintroduce this automatic in-memory conversion if we 
 want still to support the old syntax.

 Now I think we have to mark the current syntax of CssResource as 
 deprecated in favor of GSS. In order to able to remove the generator in the 
 next releases.

 Another idea: In order to ease the conversion of existing CssResource to 
 GSS, we could maybe during the compilation convert every .css file with the 
 converter and write the result on disk (in the extra directory) if the 
 -extra flag is set.

 Julien

 On Mon, Oct 6, 2014 at 11:43 PM, 'Goktug Gokdogan' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com javascript: wrote:

 We worked on a migration plan a few weeks back. I don't think we need to 
 mix css and gss together inside the same app.

 At this point, the libraries have multiple reasonable options on 
 compatibility:

 1- Provide both css and gss file for the resource (recommended).
 The library will work fine regardless if the app enables gss or not as 
 the right file will be chosen for the app. That's what we will do for 
 internal resources in the SDK.

 2- Keep providing the css file and make sure it works in strict mode.
 The library will work fine in css mode and will work with gss only if 
 the legacy mode is enabled.

 3- Keep the old css that requires lenient mode.
 The library will work fine in css mode and *may* work with gss 
 if lenient legacy mode is enabled. 

 More problematic part is the css inside uibinder. Like you said, 
 simplest option is to introduce a temporary attribute in ui:style tag 
 that marks the content as gss. In this case it is more tricky for the 
 library to support compatibility mode similar to the mode (1) above. Either 
 the lib should write the style that both compiles with css and gss or if it 
 is not feasible then it should extract the resource to a file and follow 
 the two file approach described above.


 On Mon, Oct 6, 2014 at 12:54 PM, Julien Dramaix julien@gmail.com 
 javascript: wrote:

  Hmm but still a bit of work if a library has lots of 

[gwt-contrib] Last call for patches

['Daniel Kurka' via GWT Contributors]

Hi all,

as a reminder: Please make sure to get your patches in for GWT 2.7 until
tomorrow (October 7th).

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiot7yhnKTbXepwskgBYxOpqzMEHQMhTc%3D3NHGbMP5%2BDqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] bug with the new snapshot

['Daniel Kurka' via GWT Contributors]

Hi Julien,

I think this is related to us not waiting for the body to be loaded before
injecting the recompile.nocache.js.

Can you try: https://gwt-review.googlesource.com/#/c/9451/ and let me know
if this fixes your issue?

-Daniel

On Thu, Oct 2, 2014 at 4:34 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

 This morning, I've updated my GWT snapshot to the last one and I'm not
 able to run the super dev mode (with the flag -superDevMode) for my
 applications.

 The problem comes from that the .nocache.js tries to add the compilation
 dialog to the body before the body is initialized.

 Error:
 Uncaught TypeError: Cannot read property 'appendChild' of null
 in:
 Dialog.prototype.show = function() {
   $doc.body.appendChild(this.__overlay);
   $doc.body.appendChild(this.__dialog);
 };

 $doc.body is null when the method is called. This method should be called
 when the html is fully loaded.


 If I include the nocache.js script at the end of the body instead of in
 the head of the html, it works fine.

 Julien


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5%3DMU8--RcXrHwjM8ZSPvB%2B2MG-7nAvF1Sq8BjDEeJ5Kw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5%3DMU8--RcXrHwjM8ZSPvB%2B2MG-7nAvF1Sq8BjDEeJ5Kw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqQnryHwbPUYRV1Uyborxpd31sFNHxSUkz063k7otE5Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT incremental compiles in action

['Daniel Kurka' via Google Web Toolkit]

Hi all,

here is a small video of GWT incremental compiles in action:
https://www.youtube.com/watch?v=qpCSbj36O44feature=youtu.be

-Daniel

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

Re: [gwt-contrib] Re: JsInterop

['Daniel Kurka' via GWT Contributors]

Make sure turn turn on -XjsInteropMode JS

-Daniel

On Wed, Oct 1, 2014 at 12:03 PM, 'John Stalcup' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Make sure turn turn on -XjsInteropMode JS

 On Tue, Sep 30, 2014 at 9:18 AM, 'Chris DiGiano' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Have you enabled jsInterop mode via the compiler flag? It looks like this
 on the command line:
  -XjsInteropMode JS

 Chris

 On Tue Sep 30 2014 at 7:05:23 AM Michael Vogt mich...@michaelvogt.eu
 wrote:

 Btw, when calling parse() out of jsni or in the browser console, it
 works fine. So the Javascript side is ok.

 --
 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
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


  --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ_PjHJ0K89e%2B6Li1dL21TubXRoG%2B9aA-H4d5YWMcWjcEw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ_PjHJ0K89e%2B6Li1dL21TubXRoG%2B9aA-H4d5YWMcWjcEw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




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

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipaFHw%2BL_%3D-zKZ5LXFp%3DKfPToxPzyuhT-92fRbseQiTow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7 release plan

['Daniel Kurka' via GWT Contributors]

Hi all,

we just settled on a GWT 2.7 release plan:

 - We *code freeze* on *October 7th* and branch for GWT 2.7.
 - As soon as we have the *remaining patches submitted*, we put out a beta1
build, this should be no later than *October 7th.*
 - Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
 - We are going to *flip incremental to default* tomorrow and *wait for 1-2
weeks* for google internal feedback, if there is no serious issues we are
going to *put out RC1*
 - GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
 - Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/
 (dankurka)
 - Sending the wrong permutation to the client in SDM, if no files have
changed (dankurka).
 - Investigate why some people are seeing errors with incremental  not
restricting to one permutation (dankurka).
 - Public directories are not copied o the war directory when using SDM
(skybrian).
 - Restore Java 6 compatibility (skybrian).
 - Document limitations of JsonUtils.safeEval and discourage usage (goktug)
(promote Json.parse)

Patches that are nice to have:
 - Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go into GWT
2.7, please bring them to our attention, by replying to this thread or
adding me as a reviewer on Gerrit and setting the topic to GWT2.7.*

-Daniel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.