[gwt-contrib] Elemental2-1.1.0 released

[Julien Dramaix]

Hi,

We released and pushed to maven central a new version of Elemental2 today: 
Elemental2-1.1.0.

Please refer to the github page  for 
an explanation on how to use it. 

Summary of fixes/improvements included in this release:
- Elemental2 have been generated from the last version of closure extern 
files. Please refer to this page 
 for the 
list of improvements/fixes on those extern files.
- Fix elemental2-webassembly maven pom file to correctly depend on 
elemental2-dom
- Update jsinterop-annotations dependency to jsinterop-annotations 2.0.0.
- Fix uncheckedCast overlay call when parameter is a varargs.

Please report any issues to https://github.com/google/elemental2/issues

-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/a41bdcc6-48de-4b84-9ea7-5dc453fb4bb2o%40googlegroups.com.

Re: [gwt-contrib] Re: Happy to announce general access for J2CL!

[Julien Dramaix]

I need to fix https://github.com/google/elemental2/issues/68 first
I hope to find some time today or tomorrow to make elemental2 repo
compliant with the opensource version of j2cl.

On Thu, Nov 29, 2018 at 9:34 AM John Huss  wrote:

> Is there an example bazel WORKSPACE and BUILD file that pulls in
> elemental2?  I tried for a good while to figure out how to add it and
> didn't get anywhere.  The instructions on the project page seems out of
> date: https://github.com/google/elemental2
>
> Thanks,
> John
>
> On Tuesday, November 13, 2018 at 7:39:13 PM UTC-6, Goktug Gokdogan wrote:
>>
>>
>>
>> -- Forwarded message -
>> From: Goktug Gokdogan 
>> Date: Tue, Nov 13, 2018 at 5:38 PM
>> Subject: Happy to announce general access for J2CL!
>> To: 
>>
>>
>> Dear GWTers!
>>
>> We are happy to announce that we have opened up J2CL repository for
>> general access:
>> http://github.com/google/j2cl
>>
>> Please see the README for details and instructions.
>>
>> I also would like to use this opportunity to thank all Googlers who
>> contributed over the years and made this happen.
>>
>> Enjoy!
>>
>> Goktug, on behalf of J2CL team
>>
>> PS: If you are using Windows, you might have a bumpy road but should get
>> better over time with your feedback and contributions.
>>
> --
> 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/0dde7fef-9080-4f3f-bdc8-271c681a474d%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/CABb_3%3D4ac%2BYiDtzvR9C_A6QG_FYDFLMz2QX-xSp55_VWUke48w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Update on J2CL

[Julien Dramaix]

Note that J2CL works for a while now inside Google and is used by several
big applications. But it was using several internal tools and api that
prevent us to opensource it.
We are close to finish the clean up and as Goktug mentioned in his previous
email, you should get an announcement soon if our internal priorities don't
change.

On Tue, Oct 23, 2018 at 7:30 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> We got it mostly working. Hopefully you should get an announcement soon.
>
> On Tue, Oct 23, 2018 at 10:06 AM Konstantin Solomatov <
> konstantin.soloma...@gmail.com> wrote:
>
>> Are there any updates on J2CL? A lot of time has passed.
>>
>> On Friday, June 15, 2018 at 3:54:08 AM UTC-4, Julien Dramaix wrote:
>>>
>>> > 2. J2CL itself is build with Bazel (for the reasons you mentioned).
>>> This would not matter much, *as long as you could push the J2CL
>>> artifacts to Maven Central in an automated (Bazel) pipeline*. *Can
>>> Bazel do that*?
>>>
>>> Yes it can. We are already building jsinterop-base and Elemental2 with
>>> Bazel and push artifact on Maven Central.
>>>
>>> -Julien
>>>
>>> On Thu, Jun 14, 2018 at 3:50 PM Hristo Stoyanov 
>>> wrote:
>>>
>>>> Guys,
>>>> Thanks for the update to J2CL! Here is what I understood, the questions
>>>> I have - correct me, if I am wrong:
>>>>
>>>> 1. Google is seeing good results from J2CL in a number of products, so
>>>> your internal funding won't be cut, J2CL won't be abandoned! That is good
>>>> news!
>>>>
>>>> 2. J2CL itself is build with Bazel (for the reasons you mentioned).
>>>> This would not matter much, *as long as you could push the J2CL
>>>> artifacts to Maven Central in an automated (Bazel) pipeline*. *Can
>>>> Bazel do that*?
>>>>
>>>> 3. Some GWT folks are developing Gradle and Maven plug-ins. *What is
>>>> the status of those*? I think this is the most important thing - once
>>>> the J2CL jars are in Maven central and the plug-ins ready, people can start
>>>> building apps with J2CL?
>>>>
>>>> 4. This comment from Goktug: ..."*we use some tools that does code
>>>> pruning during build which helps some with the performance, and those tools
>>>> are not available for open source. Something we will eventually look at but
>>>> not very soon" worries me. Is J2CL a 100% Java or you use other stuff that
>>>> can not be released?*
>>>>
>>>>
>>>> *5. I still don't quite understand why not dump everything J2CL on
>>>> Gihub "AS IS" and let us sort it out?*
>>>>
>>>>
>>>> *Also, It would be helpful if some of the developers who already
>>>> received the J2CL code drop comment and clarify what needs to be finished
>>>> from their point of view.*
>>>>
>>>>
>>>> *As far as GWT3, I don't understand what is the value of it at all,
>>>> maybe valuable time/resources can be spent on J2CL instead, once it is
>>>> placed on Github*
>>>>
>>>>
>>>>
>>>> *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/807613cc-5945-49c1-8f5e-205dd53f5dea%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/807613cc-5945-49c1-8f5e-205dd53f5dea%40googlegroups.com?utm_medium=email&utm_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/d4af467b-ae98-4ab6-a665-d465c5145527%40googlegroups.com
>>

Re: [gwt-contrib] Update on J2CL

[Julien Dramaix]

> 2. J2CL itself is build with Bazel (for the reasons you mentioned). This
would not matter much, *as long as you could push the J2CL artifacts to
Maven Central in an automated (Bazel) pipeline*. *Can Bazel do that*?

Yes it can. We are already building jsinterop-base and Elemental2 with
Bazel and push artifact on Maven Central.

-Julien

On Thu, Jun 14, 2018 at 3:50 PM Hristo Stoyanov 
wrote:

> Guys,
> Thanks for the update to J2CL! Here is what I understood, the questions I
> have - correct me, if I am wrong:
>
> 1. Google is seeing good results from J2CL in a number of products, so
> your internal funding won't be cut, J2CL won't be abandoned! That is good
> news!
>
> 2. J2CL itself is build with Bazel (for the reasons you mentioned). This
> would not matter much, *as long as you could push the J2CL artifacts to
> Maven Central in an automated (Bazel) pipeline*. *Can Bazel do that*?
>
> 3. Some GWT folks are developing Gradle and Maven plug-ins. *What is the
> status of those*? I think this is the most important thing - once the
> J2CL jars are in Maven central and the plug-ins ready, people can start
> building apps with J2CL?
>
> 4. This comment from Goktug: ..."*we use some tools that does code
> pruning during build which helps some with the performance, and those tools
> are not available for open source. Something we will eventually look at but
> not very soon" worries me. Is J2CL a 100% Java or you use other stuff that
> can not be released?*
>
>
> *5. I still don't quite understand why not dump everything J2CL on Gihub
> "AS IS" and let us sort it out?*
>
>
> *Also, It would be helpful if some of the developers who already received
> the J2CL code drop comment and clarify what needs to be finished from their
> point of view.*
>
>
> *As far as GWT3, I don't understand what is the value of it at all, maybe
> valuable time/resources can be spent on J2CL instead, once it is placed on
> Github*
>
>
>
> *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/807613cc-5945-49c1-8f5e-205dd53f5dea%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/CABb_3%3D7wNXvwmuLdOfATWyrBaMUp6uNt_D5SLLmFucVwFbWxUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Update on J2CL

[Julien Dramaix]

> I fail to understand why the prerequisite of using bazel was enforced

Bazel is enforced if you want to contribute to J2CL not if you want to use
it. As Goktug mentioned in his post, J2CL has been built for our internal
users first. So it's natural to first integrate it with Bazel as we use it
internally and it's our domain of expertise. As any other project, we don't
want to maintain different build files for building and developing J2CL.
J2CL is a java application that takes java files as input and generates
closure annotated js files.  You need then to pass those generated js file
to the javascript/closure pipeline. That part is slightly different for
each build system and we rely on open source contributors to make the right
decision.

That being said, we truly think J2CL can bring some added value to the
opensource community and that people outside of Google (mainly GWT
contributors) could be interested. You should just stop thinking  that J2CL
is intended to be the replacement of GWT.  GWT 3.0 could use j2cl as main
compiler or not. It will be up to the GWT steering committee to decide.


On Tue, Jun 12, 2018 at 12:10 AM David Nouls  wrote:

> Thanks for the update,
>
> I fail to understand why the prerequisite of using bazel was enforced and
> why it seems to have such a big impact on opensourcing J2CL.
> As far as I understand Google is probably the only company that uses
> bazel, and internally that is not even the same product as the opensource
> one.
>
> Does J2CL depend on Bazel somehow ? That sounds like a liability to me.
> Newer versions of Gradle have a lot of optimisations and caching
> implemented, so was it really worth the effort to use Bazel ?
> On 12 Jun 2018, 08:54 +0200, 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com>, wrote:
>
> *We recently sent an update on J2CL and we would like to cross post it to
> GWT contributor list since there was recent questions about it. I would
> like to also remind everybody that GWT3 != J2CL; GWT3 work is still ongoing
> in the open source community and I will talk to steering committee to see
> if an update on it could be provided as well.*
> 
>
> *Since we gave access to more people, we thought that this would be a good
> time to give you an update on J2CL; what is happening, if it is really a
> thing or not and what to expect from it.*
>
> *First the good parts:*
>
> *1- J2CL is feature complete for a while and had a very strong traction in
> Google in the last year.*
>
> *We got pretty big customers on board and some launched to production and
> they are pretty happy about it.  To name a few projects that are already
> running J2CL code: New GMail, Inbox, Docs, Slides. And more are coming.*
>
> *We could not have achieved this with GWT since our customers apps have
> very strict expectations on code size/performance and interoperation with
> their existing JavaScript stack. And this is why we built J2CL in the first
> place.*
>
> *2- J2CL has improved on code size compared to already quite performant
> GWT compiler.*
>
> *The last time I checked it was around 5-10% code size reduction and we
> will continue working on that.*
>
> *3- Optimized compiles improved by 50% and it is possible to get a couple
> of second refresh times for development.*
>
>
> *And now the “could be better” parts :)*
>
> *1- Open-source build is not fully working*
>
> *J2CL is highly optimized for Google infrastructure and scales very well
> with Bazel. There are multiple reasons for that:*
>
> *- Bazel works very well as a cross-platform build solution. You can build
> your Android, iOS and Web application together with Bazel.*
>
> *- Bazel has a very good caching/scaling architecture and we already
> designed J2CL based on that.*
>
> *- Bazel is our only expertise on build systems so we can only ensure
> developers gets a good development experience using Bazel.*
>
> *For pure J2CL experience in open source, we decided early on to rely on
> Bazel and made it a prerequisite for open-sourcing it.*
>
> *However, our internal build macros used things that are only available
> internally so we need to clean and port to a more proper solution that
> could also work well for open-source. And during that process we keep
> hitting limitations that block us and cause delays. Also please keep in
> mind that J2CL’s success is highly related to its internal success and we
> were busy helping internal customers to have successful production launches
> so we didn't have much bandwidth either.*
>
> *On the bright side, most of the blocking issues are getting resolved and
> we had progress in the last couple of months and we are prioritizing this
> even further.*
>
> *(Note that this doesn’t mean you will be *required* to use Bazel for J2CL
> and our contributors are already working on Maven/Gradle solutions.)*
>
> *2- For now your mileage may vary w.r.t performance*
>
> *Even though optimized compiles are much better for Google, I am no

Re: [gwt-contrib] Re: The elusive J2CL

[Julien Dramaix]

I changed the permission settings. You should now be able to apply for
membership at https://groups.google.com/forum/#!forum/j2cl-external

-Julien

On Fri, Jun 1, 2018 at 1:50 PM Alberto Mancini  wrote:

> Hello Goktug,
> thanks a lot for the opportunity.
> Actually seems that the address j2cl-exter...@googlegroups.com does not
> exist.
>  mailer-dae...@google.com 
> We're writing to let you know that the group you tried to contact
> (j2cl-external) may not exist, or you may not have permission to post
> messages to the group. A few more details on why you weren't able to post:
>
>  * You might have spelled or formatted the group name incorrectly.
>  * The owner of the group may have removed this group.
>  * You may need to join the group before receiving permission to post.
>  * This group may not be open to posting.
> - -
>
> It is just me, I'm not autrorized or actually the address is spelled
> incorrectly?
>
> Thanks,
>Alberto.
>
>
> On Thu, May 31, 2018 at 11:51 PM 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> Hi all.
>>
>> Sorry for the delays in getting J2CL work for opensource. Some of the
>> delays were out of our control but this is something we actively working on
>> in the last few months and having progress. In the meantime plenty of
>> active GWT contributors already has access to it for a long time and
>> working on getting GWT 3 ready. Also a while back, I said "if there are
>> more people who needs access to J2CL for GWT 3 porting, we can give them
>> access" but it is not usable for average developer.
>>
>> If you think you need earlier access to J2CL in as-is state (which
>> partially builds with plenty of workarounds), pls send a message to
>> j2cl-exter...@googlegroups.com; and pls make your case (e.g. porting X
>> from GWT 2 SDK to GWT 3) and we will give access. However we cannot help
>> you a lot at the moment when you hit problems (you will) so pls set your
>> expectations accordingly.
>>
>>
>> On Thu, May 31, 2018 at 6:02 AM Ivan Markov 
>> wrote:
>>
>>> Don't you think there could've been 2x or even 3x as much people working
>>> on porting GWT2 stuff over to J2CL if J2CL was released in the first place?
>>> For one, releasing J2CL could've made me reconsider how much time I invest
>>> in my own SDBG pet project. Which - at the current situation is exactly
>>> zero. Or whether to invest time in the abandoned typescript2java effort,
>>> which would bring seamless JSInterop with gazillions of .d.ts'd JS
>>> libraries without the need to manually code JSInterop bindings...
>>>
>>> Say what you want, but 3 months since my original rant that at the top
>>> of this thread, the "basic Bazel building issues" of Goktug seem still to
>>> be a roadblock and J2CL is still nowhere to be seen.
>>>
>>> ... and then we had Daniel planning to write a book on J2CL end of 2016,
>>> remember? Come on guys, it is Q3 2018 now... I might now agree with Learner
>>> Evermore on his points 2) to 5), but with point 1) he nailed it:
>>> "1. The backing company backed off but kept the crucial new piece secret
>>> - J2CL."
>>>
>>>
>>> On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote:

 That's not really true. There are a lot of people working on the GWT
 module, getting them out of GWT and moving them to standalone artifacts.
 Doing that, they replace JSNI with JsInterop, replace generators, etc. This
 is all done, to get GWT 2 ready for GWT 3. And if you want to see something
 existing in GWT 3, you can ask vertispan to do the job.

 With the knowledge about the things, that will change with GWT 3 /
 J2CL, I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the
 generator with APT and remove the dependency to any GWT classes. I created
 a sample application based on the new version (mvp4g2) and Elemental 2. And
 yes, it works with J2CL.

 And, keep in mind, applications written in GWT in 2010 still work. What
 was the favorite JS framework at that time? I don't remember.

>>> --
>>> 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/03d79d23-11e5-423b-9009-d439a569c512%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 goo

Re: [gwt-contrib] Elemental2 1.0 release date

[Julien Dramaix]

I planned to spend some time on that this quarter but keep in mind it
always depends on our internal priorities and workload.

On Tue, Apr 3, 2018 at 8:20 AM Paul Stockley  wrote:

> Any idea when Elemental2 1.0.0 will be released? The RC1 has been out
> there for a while 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/491ffc56-b012-4609-ba4c-aea17362b133%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/CABb_3%3D5AUq2%3DYzrig9VDfp_03u-_q5%3DdR3Hgk1rZi5xhNGC_sA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Release candidate of Elemental2 and JsInterop-base.

[Julien Dramaix]

Hi,

I've released the first release candidate of Elemental2 and jsinterop-base
today.

As usual, elemental2 is split into small jar files:

Jar file

artifact-id

GWT module

elemental2-core.jar


elemental2-core

elemental2.core.Core

elemental2-promise.jar


elemental2-promise

elemental2.promise.Promise

elemental2-dom.jar


elemental2-dom

elemental2.dom.Dom

elemental2-svg.jar


elemental2-svg

elemental2.svg.Svg

elemental2-webgl.jar


elemental2-webgl

elemental2.webgl.WebGl

elemental2-media.jar


elemental2-media

elemental2.media.Media

elemental2-indexeddb.jar


elemental2-indexeddb

elemental2.indexeddb.IndexedDb

elemental2-webstorage.jar


elemental2-webstorage

elemental2.webstorage.WebStorage

You can try them by downloading the jar files or adding Maven dependencies:



  com.google.elemental2
  ${artifact-id}
  1.0.0-RC1


Then inherit the right gwt module in your gwt.xml file.

For JsInterop-base, you can try it by downloading the jar file

or use the following Maven dependency:




  com.google.jsinterop
  base
  1.0.0-RC1


Don’t hesitate to report any bugs, issues, concerns you have on the
elemental2 github bug tracker 
or the jsinterop-base github tracker.


-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%3D7t1VU0mUT9b0e7_fOg81ozT%2B_qpDd2L%3DBXt5bXqEzRDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2:1.0.0-beta-3 released

[Julien Dramaix]

Correction of my previous email: Elemental2:1.0.0-beta-3 is working with
the current version of GWT. You don't need to use the HEAD_SNAPSHOT release
of GWT.

Sorry for the confusion.

-Julien

On Tue, Dec 5, 2017 at 9:54 AM Julien Dramaix 
wrote:

> I've released a Elemental2:1.0.0-beta-3 yesterday in order to fix the
> maven issue.
>
> As usual, elemental2 is split into small jar files:
>
>
>
> Jar file
>
> artifact-id
>
> GWT module
>
> elemental2-core.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-core/1.0.0-beta-3/elemental2-core-1.0.0-beta-3.jar>
>
> elemental2-core
>
> elemental2.core.Core
>
> elemental2-promise.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-promise/1.0.0-beta-3/elemental2-promise-1.0.0-beta-3.jar>
>
> elemental2-promise
>
> elemental2.promise.Promise
>
> elemental2-dom.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-dom/1.0.0-beta-3/elemental2-dom-1.0.0-beta-3.jar>
>
> elemental2-dom
>
> elemental2.dom.Dom
>
> elemental2-svg.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-svg/1.0.0-beta-3/elemental2-svg-1.0.0-beta-3.jar>
>
> elemental2-svg
>
> elemental2.svg.Svg
>
> elemental2-webgl.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webgl/1.0.0-beta-3/elemental2-webgl-1.0.0-beta-3.jar>
>
> elemental2-webgl
>
> elemental2.webgl.WebGl
>
> elemental2-media.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-media/1.0.0-beta-3/elemental2-media-1.0.0-beta-3.jar>
>
> elemental2-media
>
> elemental2.media.Media
>
> elemental2-indexeddb.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-indexeddb/1.0.0-beta-3/elemental2-indexeddb-1.0.0-beta-3.jar>
>
> elemental2-indexeddb
>
> elemental2.indexeddb.IndexedDb
>
> elemental2-webstorage.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webstorage/1.0.0-beta-3/elemental2-webstorage-1.0.0-beta-3.jar>
>
> elemental2-webstorage
>
> elemental2.webstorage.WebStorage
>
>
>
>
>
> You can try them by downloading the jar files or adding Maven dependencies:
>
>
>
> 
>
> com.google.elemental2
>
> ${artifact-id}
>
> 1.0.0-beta-3
>
> 
>
>
>
> Then inherit the right gwt module in your gwt.xml file.
>
>
>
> This beta version works only with the latest HEAD_SNAPSHOT release of GWT
> <https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt/HEAD-SNAPSHOT/>
> .
>
>
>
> Don’t hesitate to report any bugs, issues, concerns you have on the
> github bug tracker <https://github.com/google/elemental2/issues>.
>
>
>
> Important note: This is a beta releases and future updates (up until the
> final release) may break code!
>
>
>
> -Julien
>
>
> On Wed, Nov 22, 2017 at 5:59 PM Colin Alworth  wrote:
>
>> It looks like the poms weren't correctly updated - they still depend on
>> jsinterop-base 1.0.0-beta-1, tickling
>> https://github.com/google/elemental2/issues/20 again. The gwt2 compiler
>> fails on this with this sort of error:
>> [INFO][ERROR] Errors in
>> 'jar:file:/Users/colin/.m2/repository/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar!/elemental2/dom/Element.java'
>> [INFO]   [ERROR] Line 260: The method asString(Element.
>> ReplaceWithNodesUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 303: The method asBoolean(Element.
>> ScrollIntoViewTopUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 326: The method asBoolean(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 331: The method asDouble(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 336: The method asString(Element.
>> SetAttributeNSValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 364: The method asBoolean(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 369: The method asDouble(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>> [INFO]   [ERROR] Line 374: The method asString(Element.
>> SetAttributeValueUnionType) is undefined for the type Js
>>
>> Simple workaround, manually add excludes

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

[Julien Dramaix]

So I think Thomas is right.
One of our change in this new release was to rename toString() method on
some objects to avoid confusion with java.lang.Object methods.
That broke Elemental with J2CL because java.lang.Object is a JsType in J2CL
and we need to lift up some jsinterop restriction to allows user to
override an implementation with a native override (something similar to
https://gwt-review.googlesource.com/c/gwt/+/20122)
But in GWT, Object is not a JsType and we don't have that problem. So we
dont need https://gwt-review.googlesource.com/c/gwt/+/20122 for Elemental
in GWT.

The good news is Elemental2:1.0.0-beta-3 is working with the current
version of GWT. Sorry for the confusion.

On Mon, Dec 4, 2017 at 11:08 PM Thomas Broyer  wrote:

> There must be some cases where it requires the current head, but so far I
> haven't had any issue with 2.8.2.
>
> --
> 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/bb66fed8-82a5-4b80-a36c-c223578d7e8c%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/CABb_3%3D7cdZwbC5uVHkBTQ%3DAr8vZ%2BgqMzDWoQ6_gS0AO43tU6ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Elemental2:1.0.0-beta-3 released

[Julien Dramaix]

I've released a Elemental2:1.0.0-beta-3 yesterday in order to fix the maven
issue.

As usual, elemental2 is split into small jar files:



Jar file

artifact-id

GWT module

elemental2-core.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-core/1.0.0-beta-3/elemental2-core-1.0.0-beta-3.jar>

elemental2-core

elemental2.core.Core

elemental2-promise.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-promise/1.0.0-beta-3/elemental2-promise-1.0.0-beta-3.jar>

elemental2-promise

elemental2.promise.Promise

elemental2-dom.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-dom/1.0.0-beta-3/elemental2-dom-1.0.0-beta-3.jar>

elemental2-dom

elemental2.dom.Dom

elemental2-svg.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-svg/1.0.0-beta-3/elemental2-svg-1.0.0-beta-3.jar>

elemental2-svg

elemental2.svg.Svg

elemental2-webgl.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webgl/1.0.0-beta-3/elemental2-webgl-1.0.0-beta-3.jar>

elemental2-webgl

elemental2.webgl.WebGl

elemental2-media.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-media/1.0.0-beta-3/elemental2-media-1.0.0-beta-3.jar>

elemental2-media

elemental2.media.Media

elemental2-indexeddb.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-indexeddb/1.0.0-beta-3/elemental2-indexeddb-1.0.0-beta-3.jar>

elemental2-indexeddb

elemental2.indexeddb.IndexedDb

elemental2-webstorage.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webstorage/1.0.0-beta-3/elemental2-webstorage-1.0.0-beta-3.jar>

elemental2-webstorage

elemental2.webstorage.WebStorage





You can try them by downloading the jar files or adding Maven dependencies:





com.google.elemental2

${artifact-id}

1.0.0-beta-3





Then inherit the right gwt module in your gwt.xml file.



This beta version works only with the latest HEAD_SNAPSHOT release of GWT
<https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt/HEAD-SNAPSHOT/>
.



Don’t hesitate to report any bugs, issues, concerns you have on the github
bug tracker <https://github.com/google/elemental2/issues>.



Important note: This is a beta releases and future updates (up until the
final release) may break code!



-Julien


On Wed, Nov 22, 2017 at 5:59 PM Colin Alworth  wrote:

> It looks like the poms weren't correctly updated - they still depend on
> jsinterop-base 1.0.0-beta-1, tickling
> https://github.com/google/elemental2/issues/20 again. The gwt2 compiler
> fails on this with this sort of error:
> [INFO][ERROR] Errors in
> 'jar:file:/Users/colin/.m2/repository/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar!/elemental2/dom/Element.java'
> [INFO]   [ERROR] Line 260: The method asString(Element.
> ReplaceWithNodesUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 303: The method asBoolean(Element.
> ScrollIntoViewTopUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 326: The method asBoolean(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 331: The method asDouble(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 336: The method asString(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 364: The method asBoolean(Element.
> SetAttributeValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 369: The method asDouble(Element.
> SetAttributeValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 374: The method asString(Element.
> SetAttributeValueUnionType) is undefined for the type Js
>
> Simple workaround, manually add excludes on jsinterop-base, and inherit
> the correct version in your project:
> 
>   com.google.elemental2
>   elemental2-dom
>   1.0.0-beta-2
>   
> 
>   com.google.jsinterop
>   base
> 
>   
> 
> 
>   com.google.jsinterop
>   base
>   1.0.0-beta-3
> 
>
> Julien, if you do happen to release an updated beta to solve this, perhaps
> also update jsinterop-annotations to 1.0.2, the version that was released
> with GWT 2.8.2.
>
>
>
> On Wednesday, November 22, 2017 at 7:13:29 PM UTC-6, Julien Dramaix wrote:
>>
>> The beta version of Elemental2 using the JsInterop specification has been
>> released on Sonatype today and is available on Maven central. This release
>> should be t

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

[Julien Dramaix]

Thanks for this feedback Colin. I'll update the pom accordingly and do a
beta-3 release on Tuesday.

Julien

On Wed, Nov 22, 2017 at 5:59 PM Colin Alworth  wrote:

> It looks like the poms weren't correctly updated - they still depend on
> jsinterop-base 1.0.0-beta-1, tickling
> https://github.com/google/elemental2/issues/20 again. The gwt2 compiler
> fails on this with this sort of error:
> [INFO][ERROR] Errors in
> 'jar:file:/Users/colin/.m2/repository/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar!/elemental2/dom/Element.java'
> [INFO]   [ERROR] Line 260: The method asString(Element.
> ReplaceWithNodesUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 303: The method asBoolean(Element.
> ScrollIntoViewTopUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 326: The method asBoolean(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 331: The method asDouble(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 336: The method asString(Element.
> SetAttributeNSValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 364: The method asBoolean(Element.
> SetAttributeValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 369: The method asDouble(Element.
> SetAttributeValueUnionType) is undefined for the type Js
> [INFO]   [ERROR] Line 374: The method asString(Element.
> SetAttributeValueUnionType) is undefined for the type Js
>
> Simple workaround, manually add excludes on jsinterop-base, and inherit
> the correct version in your project:
> 
>   com.google.elemental2
>   elemental2-dom
>   1.0.0-beta-2
>   
> 
>   com.google.jsinterop
>   base
> 
>   
> 
> 
>   com.google.jsinterop
>   base
>   1.0.0-beta-3
> 
>
> Julien, if you do happen to release an updated beta to solve this, perhaps
> also update jsinterop-annotations to 1.0.2, the version that was released
> with GWT 2.8.2.
>
>
>
> On Wednesday, November 22, 2017 at 7:13:29 PM UTC-6, Julien Dramaix wrote:
>>
>> The beta version of Elemental2 using the JsInterop specification has been
>> released on Sonatype today and is available on Maven central. This release
>> should be the last beta release and I expect to release the first RC in few
>> weeks.
>>
>>
>> This release introduces -- among others:
>>
>> - a better granularity for api with numbers. Config files list APIs using
>> integer instead of double.
>>
>> - usage of wildcard type for more flexibility.
>>
>> - support for javascript constructor function
>>
>> - static factory methods for dictionary type.
>>
>> Elemental2 is split into small jar files:
>>
>>
>> Jar file
>>
>> artifact-id
>>
>> GWT module
>>
>> elemental2-core.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-core/1.0.0-beta-2/elemental2-core-1.0.0-beta-2.jar>
>>
>> elemental2-core
>>
>> elemental2.core.Core
>>
>> elemental2-promise.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-promise/1.0.0-beta-2/elemental2-promise-1.0.0-beta-2.jar>
>>
>> elemental2-promise
>>
>> elemental2.promise.Promise
>>
>> elemental2-dom.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-dom/1.0.0-beta-2/elemental2-dom-1.0.0-beta-2.jar>
>>
>> elemental2-dom
>>
>> elemental2.dom.Dom
>>
>> elemental2-svg.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-svg/1.0.0-beta-2/elemental2-svg-1.0.0-beta-2.jar>
>>
>> elemental2-svg
>>
>> elemental2.svg.Svg
>>
>> elemental2-webgl.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webgl/1.0.0-beta-2/elemental2-webgl-1.0.0-beta-2.jar>
>>
>> elemental2-webgl
>>
>> elemental2.webgl.WebGl
>>
>> elemental2-media.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-media/1.0.0-beta-2/elemental2-media-1.0.0-beta-2.jar>
>>
>> elemental2-media
>>
>> elemental2.media.Media
>>
>> elemental2-indexeddb.jar
>> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-indexeddb/1.0.0-beta-2/elemental2-indexeddb-1.0.0-beta-2.jar>
>

[gwt-contrib] Elemental2:1.0.0-beta-2 released

[Julien Dramaix]

The beta version of Elemental2 using the JsInterop specification has been
released on Sonatype today and is available on Maven central. This release
should be the last beta release and I expect to release the first RC in few
weeks.


This release introduces -- among others:

- a better granularity for api with numbers. Config files list APIs using
integer instead of double.

- usage of wildcard type for more flexibility.

- support for javascript constructor function

- static factory methods for dictionary type.

Elemental2 is split into small jar files:


Jar file

artifact-id

GWT module

elemental2-core.jar


elemental2-core

elemental2.core.Core

elemental2-promise.jar


elemental2-promise

elemental2.promise.Promise

elemental2-dom.jar


elemental2-dom

elemental2.dom.Dom

elemental2-svg.jar


elemental2-svg

elemental2.svg.Svg

elemental2-webgl.jar


elemental2-webgl

elemental2.webgl.WebGl

elemental2-media.jar


elemental2-media

elemental2.media.Media

elemental2-indexeddb.jar


elemental2-indexeddb

elemental2.indexeddb.IndexedDb

elemental2-webstorage.jar


elemental2-webstorage

elemental2.webstorage.WebStorage



You can try them by downloading the jar files or adding Maven dependencies:




 com.google.elemental2

 ${artifact-id}

 1.0.0-beta-2




Then inherit the right gwt module in your gwt.xml file.


This beta version works only with the latest HEAD_SNAPSHOT release of GWT

.


Don’t hesitate to report any bugs, issues, concerns you have on the github
bug tracker .


Important note: This is a beta releases and future updates (up until the
final release) may break code!


-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%3D6XFFvmcM3_b2ed51cv3K9cOwEFXQ4eNYSPXrXJ9CwDKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] jsinterop-base github repository and new beta release

['Julien Dramaix' via GWT Contributors]

I'll create a new release of elemental2 next week. Stay tuned.

On Friday, November 10, 2017 at 6:13:31 PM UTC-8, Peter Donald wrote:
>
> Great work - thanks!
>
> Is this compatible with the last release of elemental2? (IIRC it 
> was 1.0.0-beta-1)
>
> On Sat, Nov 11, 2017 at 12:22 PM, 'Julien Dramaix' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com > wrote:
>
>> Dear contributors, 
>>
>> We've just created a new github repository containing the source code of 
>> jsinterop-base: https://github.com/google/jsinterop-base
>>
>> We've also released a new beta version of the library: 
>> jsinterop-base:1.0.0-beta-3 
>> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/>
>>
>> You can try it by downloading the jar file 
>> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/base-1.0.0-beta-3.jar>
>>  
>> or use the following Maven dependency:
>>
>>
>> 
>>   com.google.jsinterop
>>   base
>>   1.0.0-beta-3
>> 
>>
>>
>> Don’t hesitate to report any bugs, issues, concerns you have on the github 
>> issue tracker <https://github.com/google/jsinterop-base/issues>.
>>
>> -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/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Cheers,
>
> Peter Donald
>

-- 
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/ff40c05b-5f30-418e-9caa-6a53a96dfa84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] jsinterop-base github repository and new beta release

['Julien Dramaix' via GWT Contributors]

Dear contributors,

We've just created a new github repository containing the source code of
jsinterop-base: https://github.com/google/jsinterop-base

We've also released a new beta version of the library:
jsinterop-base:1.0.0-beta-3


You can try it by downloading the jar file

or use the following Maven dependency:



  com.google.jsinterop
  base
  1.0.0-beta-3



Don’t hesitate to report any bugs, issues, concerns you have on the github
issue tracker .

-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/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Last call for GWT 2.8.2 patches, and testers needed!

[Julien Dramaix]

Roberto is working on a patch needed for Elemental2 (lifting jsinterop
restrictions up for native method overloads).
I let Roberto give more info on the patch and eta.

Julien

On Tue, Oct 3, 2017 at 9:12 AM Thomas Broyer  wrote:

>
>
> On Tuesday, October 3, 2017 at 12:28:48 PM UTC+2, Colin Alworth wrote:
>>
>> As you can see from https://github.com/gwtproject/gwt/milestone/18
>> ,
>> GWT 2.8.2 is almost ready to go! This release is important to get out for
>> several reasons:
>>
>>  * Supports running the compile on Java 9 (note that it does not yet add
>> support for the Java 9 language or sdk)
>>  * Fixes a bug users are experiencing in latest versions of Chrome with
>> getAbsoluteLeft/getAbsoluteTop (see
>> https://github.com/gwtproject/gwt/issues/9542 and related bugs).
>>
>> If you have more patches not yet ready for review, or not listed in the
>> issues above, please let us know so we can track them and get ready for the
>> release.
>>
>
> Just added https://github.com/gwtproject/gwt/issues/9534 to the
> milestone, and will send the patch asap.
>
>
>> If you are able to volunteer a small amount of time to help us perform
>> acceptance testing on 2.8.2, please contact me with the Operating System
>> and Browsers you have available to you, and I will put you on the list.
>> This work will start in a few days once we have a release candidate ready.
>>
>
> Chrome 61 & Firefox 55 on ArchLinux w/ OpenJDK 7u151, 8u144 and/or 9u181.
> (could possibly test on Windows in VirtualBox using Microsoft's virtual
> machines, would take more time; so if can have people who actually use
> Windows, that'd be preferable)
>
> --
> 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/ed6de357-d35d-4a83-864f-b8808de83761%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/CABb_3%3D6xSbDvZAkGiZt7R1-A%2Bh3rRXRszZ2_u9JsobUn6B%2B9nQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 source code on github

[Julien Dramaix]

I've enabled the issue tab.

On Tue, May 30, 2017 at 11:04 PM Daniel Harezlak 
wrote:

> Hi, it looks like issues are disabled for the
> https://github.com/google/elemental2 project.
>
>
> On Saturday, May 20, 2017 at 12:34:09 AM UTC+2, Julien Dramaix wrote:
>
>>
>> If you have any questions/issues, feel free to open a bug in the github
>> project.
>>
> --
> 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/7d91a558-d332-471c-9181-f2664336229d%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/7d91a558-d332-471c-9181-f2664336229d%40googlegroups.com?utm_medium=email&utm_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%3D7naet%3D84KNY_c1ePG%2BAiPk%2BMdtk-8Ri6NKWKmE26ytiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Elemental2 source code on github

[Julien Dramaix]

The source code of Elemental2 is now available on github:
https://github.com/google/elemental2

Please refer to the project README for more information about how to use it.

If you have any questions/issues, feel free to open a bug in the github
project.

Important note: Elemental2 is in beta state and future updates (up until
the final release) may break code!

-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%3D4HOJm-_31bbUDF8qWHh34AEaTtySOt35o0ukH73mdusQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

I forgot to mention: as a workaround, you can create your own JsFunction
callback and cast it to Function:
@JsFunction
interface MyJsFunction {
  void onInvoke();

  default Function asFunction() {
return (Function) this;
  }
}

On Tue, May 9, 2017 at 9:37 AM Julien Dramaix 
wrote:

> > I believe it's due to how they're declared in the Closure externs:
> onreadystatechange and onerror:
> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
> vs all the other callbacks:
> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>
> Yes, the externs use the Function object as type instead of using a
> function type like {function():any}.
> We'll fix that for the next version.
>
> On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:
>
>>
>>
>> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>>>
>>>>
>>>>
>>>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>>>>
>>>>> HI, what are the replacements for elemental2.Global.window and
>>>>> similar in this new release?
>>>>>
>>>>
>>>> elemental2.DomGlobal.window (in elemental2-dom dependency)
>>>>
>>> Thanks!
>>>
>>> Another inconsistency with the previous release of elemental2 which
>>> broke my code is the use of elemental2.core.Function for the
>>> onreadystatechange field in the elemental2.dom.XMLHttpRequest type
>>> which prevents providing the function as a lambda. Other function fields in
>>> the mentioned type (e.g. onprogress or onloadstart) seem to keep the
>>> functional interface semantics. Is this intended or is it an oversight?
>>>
>>
>> I believe it's due to how they're declared in the Closure externs:
>> onreadystatechange and onerror:
>> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
>> vs all the other callbacks:
>> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>>
>>
>> --
>> 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%40googlegroups.com?utm_medium=email&utm_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%3D52vj1gbcf_MPq5UiThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

> I believe it's due to how they're declared in the Closure externs:
onreadystatechange and onerror:
https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
vs all the other callbacks:
https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862

Yes, the externs use the Function object as type instead of using a
function type like {function():any}.
We'll fix that for the next version.

On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:

>
>
> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:

 HI, what are the replacements for elemental2.Global.window and similar
 in this new release?

>>>
>>> elemental2.DomGlobal.window (in elemental2-dom dependency)
>>>
>> Thanks!
>>
>> Another inconsistency with the previous release of elemental2 which broke
>> my code is the use of elemental2.core.Function for the onreadystatechange
>> field in the elemental2.dom.XMLHttpRequest type which prevents providing
>> the function as a lambda. Other function fields in the mentioned type (e.g.
>> onprogress or onloadstart) seem to keep the functional interface
>> semantics. Is this intended or is it an oversight?
>>
>
> I believe it's due to how they're declared in the Closure externs:
> onreadystatechange and onerror:
> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
> vs all the other callbacks:
> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>
>
> --
> 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/CABb_3%3D6wNB25OWdgjbJrYk8vpozWqaNz7XtBa3K6rgn-3fq2ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] auto generation of jsinterop from .d.ts

[Julien Dramaix]

yes it is.

On Tue, Apr 18, 2017 at 4:55 PM Colin Alworth  wrote:

> Is the current plan to open source the experimental part as well? I
> suspect there are people on this list who would be very interested in
> helping to continue that effort.
>
>
> On Tuesday, April 18, 2017 at 6:52:57 PM UTC-5, Julien Dramaix wrote:
>
>> We are working internally on a jsinterop generator that can take closure
>> extern files and d.ts files as input.
>> For the time being only the closure part works fine and we use it to
>> generate elemental. We are in the process to opensource it. The d.ts part
>> was an experiment and doesn't work (yet) with the last changes in
>> typescript compiler and need still some work. Unfortunately, it's not our
>> first priority right now and I cannot give you any timeline.
>>
>>
>>
>> On Thu, Feb 16, 2017 at 8:44 AM Joshb  wrote:
>>
>>> Hi All,
>>>
>>> I had seem some conversations a while back about potentially being able
>>> to generate interfaces directly from a typescript definition file.  Did
>>> anything ever come of this?  I have a library I would very much like to get
>>> hooked into GWT and there is a typescript file.  It is quite large, and
>>> this would save a ton of time.  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/68267db6-c9b9-4acb-8499-b92b37a5263d%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/68267db6-c9b9-4acb-8499-b92b37a5263d%40googlegroups.com?utm_medium=email&utm_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/4bdea408-3421-4d37-b4f9-1273a9c490d9%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/4bdea408-3421-4d37-b4f9-1273a9c490d9%40googlegroups.com?utm_medium=email&utm_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%3D67c09tf8H7pb81YNG01Wm8sCfoX3okpBPF-6PupsT%2BNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] auto generation of jsinterop from .d.ts

[Julien Dramaix]

We are working internally on a jsinterop generator that can take closure
extern files and d.ts files as input.
For the time being only the closure part works fine and we use it to
generate elemental. We are in the process to opensource it. The d.ts part
was an experiment and doesn't work (yet) with the last changes in
typescript compiler and need still some work. Unfortunately, it's not our
first priority right now and I cannot give you any timeline.



On Thu, Feb 16, 2017 at 8:44 AM Joshb  wrote:

> Hi All,
>
> I had seem some conversations a while back about potentially being able to
> generate interfaces directly from a typescript definition file.  Did
> anything ever come of this?  I have a library I would very much like to get
> hooked into GWT and there is a typescript file.  It is quite large, and
> this would save a ton of time.  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/68267db6-c9b9-4acb-8499-b92b37a5263d%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/CABb_3%3D6LatcSTcvd8pq%3Dc1nBuKD%3DqMje4OU9E7KPn_ACHhMMew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

good catch! It's a bug in GWT. Roberto is fixing it and will propose a
patch for that.


On Thu, Apr 6, 2017 at 3:17 PM Jens  wrote:

> Hmm, I have just built gwt head from source and used the above jars but
> SDM tells me:
>
>  Errors in jsinterop/base/Js.java
>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a
> correct setter or getter signature.
>
>
> Can anyone confirm?
>
>
> -- 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/d460f0fb-6519-4eab-869b-4838e51077ad%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/CABb_3%3D67CuAEYB6gKfX7tSoRGCtGfCL0QTn%3D9ZoLDArec__bbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Elemental2 and JsInterop base beta releases available.

['Julien Dramaix' via GWT Contributors]

The beta version of Elemental2 using the JsInterop specification has been
released on Sonatype today and is available on Maven central.


This release introduces the concept of union types (which are heavily used
in JavaScript) and many more improvements. More information about union
types can be found in this document
<https://docs.google.com/document/d/14mQeAGQ9M_5uTTUbzRQzCYETA887dTO-xFLtQhgUXXk/edit?usp=sharing>
.


We also split Elemental into smaller jar files:


Jar file

artifact-id

GWT module

elemental2-core.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-core/1.0.0-beta-1/elemental2-core-1.0.0-beta-1.jar>

elemental2-core

elemental2.core.Core

elemental2-promise.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-promise/1.0.0-beta-1/elemental2-promise-1.0.0-beta-1.jar>

elemental2-promise

elemental2.promise.Promise

elemental2-dom.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-dom/1.0.0-beta-1/elemental2-dom-1.0.0-beta-1.jar>

elemental2-dom

elemental2.dom.Dom

elemental2-svg.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-svg/1.0.0-beta-1/elemental2-svg-1.0.0-beta-1.jar>

elemental2-svg

elemental2.svg.Svg

elemental2-webgl.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webgl/1.0.0-beta-1/elemental2-webgl-1.0.0-beta-1.jar>

elemental2-webgl

elemental2.webgl.WebGl

elemental2-media.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-media/1.0.0-beta-1/elemental2-media-1.0.0-beta-1.jar>

elemental2-media

elemental2.media.Media

elemental2-indexeddb.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-indexeddb/1.0.0-beta-1/elemental2-indexeddb-1.0.0-beta-1.jar>

elemental2-indexeddb

elemental2.indexeddb.IndexedDb

elemental2-webstorage.jar
<https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webstorage/1.0.0-beta-1/elemental2-webstorage-1.0.0-beta-1.jar>

elemental2-webstorage

elemental2.webstorage.WebStorage



You can try them by downloading the jar files or adding Maven dependencies:




 com.google.elemental2

 ${artifact-id}

 1.0.0-beta-1




Then inherit the right gwt module in your gwt.xml file.


This beta version works only with the latest HEAD_SNAPSHOT release of GWT
<https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt/HEAD-SNAPSHOT/>
.


We’ve also released a beta version of JsInterop.base. This library contains
base classes and utilities that provide access to JavaScript language
constructs that are not available in pure Java.


You can try it by downloading the jar file
<https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-1/base-1.0.0-beta-1.jar>
or use the following Maven dependency:




 com.google.jsinterop

 base

 1.0.0-beta-1




Don’t hesitate to report any bugs, issues, concerns you have on this
mailing list.


Important note: They are beta releases and future updates (up until the
final release) may break code!


-Julien


-- 

Julien Dramaix |  Software Engineer |  dram...@google.com |  650-750-6053

-- 
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/CABXeq2QsTarhDKbYmz0y1SOrjpuFNdoNmAnvAYKacO1f4rLcLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

['Julien Dramaix' via GWT Contributors]

The problem with generating getters and setters is that you can potentially
conflict with an existing method. I had this problem when I've generated
the java classes to interacting with the typescript compiler. Some classes
had a field named foo and a method named getFoo() and that's not
necessarily a simple getter.

On Wed, Feb 15, 2017 at 3:34 PM Colin Alworth  wrote:

>
>
> On Wednesday, February 15, 2017 at 4:01:01 PM UTC-6, Goktug Gokdogan wrote:
>
> Thanks for the feedback.
>
>
>
> On Wed, Feb 15, 2017 at 1:05 PM, Ming-Yee Iu  wrote:
>
> Well, ok. Thanks.
>
> Just in terms of general feedback on Elemental2:
>
> 1. I'm not sure whether the conversion of JavaScript properties to Java
> fields is the best choice. Sure, it "feels" more like the original
> JavaScript, but
>
>
>
> a) it's inconsistent with Java semantics,
>
>
> This could be a stylistic inconsistency not a semantic one. All arguments
> that I have seen in favor for having accessors instead of fields are
> inapplicable to Elemental fields since they all assume changes in the
> implementation of accessors which in our case always a pass through.
>
> However I am aware of the stylistic expectation from some java devs and we
> might end up providing setter/getter as overlays for people who would like
> to stick conventional style.
>
>
> There are also a variety of tools that assume methods rather than fields -
> uibinder, cssresource, editors all made assumptions about turning dot
> notation into getters (and in the case of editors, setters), and did not
> support fields at all as far as I'm aware. This is true of most (though not
> all) codegen tools I've worked with since as well.
>
> Another advantage: You can't turn a field into a method-reference.
>
>
-- 

Julien Dramaix |  Software Engineer |  dram...@google.com |  650-750-6053

-- 
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/CABXeq2SeEiWTyCJDdUNbeH8mdfTtDOc7SpqcYTPC9eGqH71DpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

elemental2 is generated from closure extern files.

The open source version of the generator should have a support for
converting d.ts file to java. We don't know yet when the generator will be
open sourced.

On Fri, Aug 19, 2016 at 4:12 PM James Horsley 
wrote:

> I remember hearing that elemental2 was being generated from TypeScript
> definitions. If that's true, is there any chance we could get a look at the
> generator code too?
>
>
> On Thursday, June 30, 2016 at 1:23:51 AM UTC+1, Julien Dramaix wrote:
>>
>> A new experimental version of Elemental2 using the new JsInterop
>> specification has been pushed on Sonatype today.
>>
>> You can try it by downloading the jar file
>> <https://oss.sonatype.org/service/local/repositories/google-releases/content/com/google/gwt/elemental2-experimental/16-06-30/elemental2-experimental-16-06-30.jar>
>> or adding this following maven dependency:
>>
>> 
>>
>>  com.google.gwt
>>
>>  elemental2-experimental
>>
>>  16-06-30
>>
>> 
>>
>> Then, inherits the elemental2 module:
>>
>> 
>>
>> This experimental version works only with the last 2.8-snapshot release
>> of GWT.
>>
>> The goal of this release is to get feedback so don’t hesitate to report
>> any bugs, issues, concerns you have on this mailing list.
>>
>>
>> Important note: This is an experimental release and without doubt the
>> future updates until the final release are going to break code!
>>
>> - 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/cd662014-000e-4823-8eab-0acb469c574c%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/cd662014-000e-4823-8eab-0acb469c574c%40googlegroups.com?utm_medium=email&utm_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%3D6y-xP%3DUU-LzPBXj68KPycBT6hdep%3DFehbh8QbPvb_vJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GSS Resource is Default

[Julien Dramaix]

We took the decision to set 'CssResource.enableGss' to false to provide a
smooth transition/migration to GWT 2.8. If we set the value of the property
to true, applications that don't migrate to GSS will stop to compile and
that could slow down the migration to GWT 2.8


On Mon, Aug 15, 2016 at 7:05 PM Ali Jalal  wrote:

> Hi all,
>
> I've been noticed that 'CssResource.enableGss' property default value is
> 'false' (in 'com/google/gwt/resources/Resources.gwt.xml'), but in GWT
> 2.8.0-beta1 release note
> 
> mentioned that 'GSS is no longer considered as experimental and old
> CssResource is now deprecated.'
>
> I think if GSS is default, then 'CssResource.enableGss' property default
> value should be set to 'true' (or something like
> 'GssResource.enabled=true').
>
> Is that correct?
>
> thanks,
> Ali.
>
> --
> 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/CAMNmzoJqJ-6EhcPGupFx24TV1O5QGdzagBfjcgKCuSzgFpYuBA%40mail.gmail.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/CABb_3%3D68DqEOXkYu6RvfPRTFZvDpdt174GN7jczz8Z%3D0tooJWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Experimental release of Elemental2

[Julien Dramaix]

>
> - The API's do not use set/get/is as was the case in the old Elemental. So
> how can I now detect that a property is readOnly ?
>
>
> We can probably make it final but if we know it is readonly but I think
we are not sure when the field is readonly. Julien?

a property flagged as @Const could be make final if it belongs to a class
or convert to a simple getter if it belongs to an interface.

That being said, clutz doesn't convert correctly a constant closure
property to a constant typescript property.

I've created a bug internally to track this problem.

On Tue, Aug 9, 2016 at 2:11 AM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> On Mon, Aug 8, 2016 at 6:40 AM, stuckagain  wrote:
>
>> Some comments:
>>
>> - Is there a possibility that the API's don't overuse double in the
>> future ? For example the XMLHttpRequest.status property is supposed to be
>> an integer not a double.
>>
>
> Yes, we will look into.
>
>
>> - The API's do not use set/get/is as was the case in the old Elemental.
>> So how can I now detect that a property is readOnly ?
>>
>>
> We can probably make it final but if we know it is readonly but I think we
> are not sure when the field is readonly. 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/a39c2d63-82e7-4131-8804-7cecd70af0de%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/CAN%3DyUA22pvB4kqUCF9figh9FHTdEHk_nB39wqx7_EFng3VKicQ%40mail.gmail.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/CABb_3%3D7n3q-xXZFndz10PxH_pmNNjvNE4tdoxr0%2BqJ8-Cu37Cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

[Julien Dramaix]

The release note is now available on the web site:
http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1

- Julien

On Fri, Jul 29, 2016 at 11:19 AM Jens  wrote:

> You should file a bug on the maven plugin issue tracker
> https://github.com/gwt-maven-plugin/gwt-maven-plugin
>
> -- 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/526d06dc-682b-4263-9cdb-16d5488acadc%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/CABb_3%3D7TJVod2H3TtPMD62JJ0s_z14bXHQOXz9auDRbF1atQ%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

This is a bug :)
That should be void and not object.

On Mon, Jul 4, 2016 at 9:05 PM Jens  wrote:

>
> > - often method signature defines Object as return type while I am pretty
>> sure something more concrete would be more appropriate.
>>
>> if a method "getFoo" can return different types "string or Foo", we
>> create different methods :
>> public Object getFoo();
>> public String getFooAsString();
>> public Foo getFooAsFoo();
>>
>> In the future there will be javadoc above the methods mentioning these
>> links between a set of methods.
>>
>
> What about methods that do not return different types and sometimes even
> should return void? For example
>
> void Window.alert(String)
> void Window.focus()
> long Date.setDate(int)
>
> They all return Object currently.
>
> -- 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/fa7580d3-f355-44e1-a923-c588b3c6da45%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/CABb_3%3D7qxuWywowiAC5C1gks4FfQJ9zgLbAWKt65_YhJeaQ2Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

> - only doubles while int would make sense here and there
we are aware of that. That should be solved before the first release

> - no use of generics and enums
generics are used (look at NativeArray ot HtmlCollection). Enums not yet

> - no packages. Would be nice to have things like dom, crypto, promise,
audio, webgl, etc.
it's planned

> - often method signature defines Object as return type while I am pretty
sure something more concrete would be more appropriate.

if a method "getFoo" can return different types "string or Foo", we create
different methods :
public Object getFoo();
public String getFooAsString();
public Foo getFooAsFoo();

In the future there will be javadoc above the methods mentioning these
links between a set of methods.

> - obviously no JavaDoc, but it would be nice to have. Especially for
people working in a no-internet environment.
As mentioned above, it's planned

> - edge cases like EventTarget.addEventListener(EventListener) and
EventTarget.addEventListener(AddEventListenerListenerCallback) that should
be cleaned up
I don't think we will clean that up. At least it's not planned.

On Mon, Jul 4, 2016 at 6:32 PM Jens  wrote:

>
> I do think we should have another library that builds on Elemental2. While
>> browser compatibility is a lot better, it still isn't perfect and we need
>>  somewhere to collect workarounds for specific issues and add helper
>> functions to make working with the library easier.
>>
>
> But then you have the GWT overhead on top of it again. But I tend to agree
> that a purely generated API can never be that nice to use as a hand crafted
> one. I have only taken a very brief look at the generated code of the
> elemental2 snapshot build but I think my major points are:
>
> - vendor prefixes. Sticking to standard API and asking devs to polyfill
> them if needed sounds better to me. Avoids potential API duplication.
> - only doubles while int would make sense here and there
> - no use of generics and enums
> - no packages. Would be nice to have things like dom, crypto, promise,
> audio, webgl, etc.
> - often method signature defines Object as return type while I am pretty
> sure something more concrete would be more appropriate.
> - obviously no JavaDoc, but it would be nice to have. Especially for
> people working in a no-internet environment.
> - edge cases like EventTarget.addEventListener(EventListener) and
> EventTarget.addEventListener(AddEventListenerListenerCallback) that should
> be cleaned up
>
> Maybe it is worth thinking about providing some patch files in addition to
> the generator to fix some stuff that are hard to fix inside the elemental2
> generator. Given that existing non-prefixed API does not change these patch
> files should be pretty stable and always applicable.
>
> -- 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/71f5352a-41dc-4f91-a22b-9a9bb21b8bbb%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/CABb_3%3D47SY%2BY%3DOV05bCFj41PecQXTEbx-Wgqazh0KJznt8g-Kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

> So I guess this is also the reason for why e.g. Int32Array returns double
instead of int?
yes we just have the information that it's a number, so we convert that to
double. We should be able to improve the number conversion before the final
release.

> Right now, as HTMLCanvasElement.getContext(String contextId) returns a
NativeObject I have to do things like this when getting the context:

This is an isue we are aware of. In the next release, Object will be used
instead of NativeObject.



On Mon, Jul 4, 2016 at 3:24 PM Kalle Persson 
wrote:

> So I guess this is also the reason for why e.g. Int32Array returns double
> instead of int?
>
> Also, would it be possible / make sense to make CanvasRenderingContext2D
> and WebGLRenderingContext extend NativeObject?
> Right now, as HTMLCanvasElement.getContext(String contextId) returns a
> NativeObject I have to do things like this when getting the context:
>
> context_ = (CanvasRenderingContext2D) (Object) canvas.getContext("2d")
>
> It works but it feels wrong. Or am I just missing something obvious?
>
> On Monday, July 4, 2016 at 9:46:44 AM UTC+2, Goktug Gokdogan wrote:
>
>> Elemental2 currently purely driven by the JavaScript extern files. So it
>> is not trivial. Maybe a later version could include some kind of type
>> extension.
>> For now perhaps we can improve the generated code to use generics so you
>> don't need to cast but we cannot modify the API.
>>
> On Sat, Jul 2, 2016 at 2:07 PM, Manuel Carrasco Moñino 
>> wrote:
>>
> I'm wondering if it would be possible to have type-safe convenience
>>> methods for creating elements, so as the user does not have to provide the
>>> string tag name, nor cast the object, maybe something like :
>>>
>>> HTMLButtonElement button = HTMLButtonElement.createElement();
>>>
>>> instead of
>>>
>>> HTMLButtonElement button = (HTMLButtonElement)
>>> document.createElement("button");
>>>
>>>
>>>
>>> El sáb., 2 jul. 2016 a las 4:38, 'Goktug Gokdogan' via GWT Contributors
>>> () escribió:
>>>
>> Closure extern definition uses a union type here:

 https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_event.js#L34

 So it accepts either EventListener interface or a function.

 When we see a union type, we generate overloads for each type so
 Elemental should provide overloads that includes both. And it seems like it
 does. If not please let us know.

>>>
 On Fri, Jul 1, 2016 at 3:39 AM, Jens  wrote:

>
> Thanks, now makes sense. I get confused with the JsFunction
>> JsType(native) because elemental2 has some callbacks as JsFunction and
>> others as JsType(native), now an actual elemental2 question; what 
>> criteria
>> is used to apply JsFunction (ex. 
>> elemental2.Node.AddEventListenerCallback)
>> instead of JsType (ex. elemental2.JsType)?
>>
>
> I think its the result of definition of EventTarget.addEventListener():
>
> *listener - The object that receives a notification (an object that
> implements the Event
>  interface) when 
> an
> event of the specified type occurs. This must be an object implementing 
> the
> EventListener
>  
> interface,
> or simply a JavaScript function
> .*
>
> The EventListener interface is a defined API and thus a
> @JsType(isNative = true) interface has been generated. But to conform to
> "or simply a JavaScript function" there is also an 
> AddEventListenerCallback
> that is a @JsFunction. Not sure if this distinction has any real value, in
> a hand coded elemental2 I would have only created a @JsFunction
> interface EventListener
>
> -- 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/73b36bdb-c496-4768-a221-21fe8b5a437c%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-w

[gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

I'm fixing my script in order to avoid that for the next release.

Thanks for the bug reporting!

On Sunday, July 3, 2016 at 1:18:28 PM UTC+2, Jakob Jarosch wrote:
>
> It seems that the deployed dependency is inconsistent.
> The pom.xml says "elemental-experimental" with version "2016-06-30".
> But the dependency is available as "elemental2-experimental" with version 
> "16-06-30".
> So gradle is not able to resolve the dependency.
>
> Warning:project ':frontend': Web Facets/Artifacts will not be configured 
> properly
> Details: org.gradle.api.artifacts.ResolveException: Could not resolve all 
> dependencies for configuration ':frontend:runtime'.
> Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: 
> Could not resolve com.google.gwt:elemental2-experimental:16-06-30.
> Required by:
> itdidea:frontend:unspecified
> Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: 
> Could not resolve com.google.gwt:elemental2-experimental:16-06-30.
> Caused by: 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.MetaDataParseException:
>  
> inconsistent module metadata found. Descriptor: 
> com.google.gwt:elemental-experimental:2016-06-29 Errors: bad module name: 
> expected='elemental2-experimental' found='elemental-experimental'
> bad version: expected='16-06-30' found='2016-06-29'
>
> - Jakob
>
> On Thursday, June 30, 2016 at 2:23:51 AM UTC+2, Julien Dramaix wrote:
>>
>> A new experimental version of Elemental2 using the new JsInterop 
>> specification has been pushed on Sonatype today.
>>
>> You can try it by downloading the jar file 
>> <https://oss.sonatype.org/service/local/repositories/google-releases/content/com/google/gwt/elemental2-experimental/16-06-30/elemental2-experimental-16-06-30.jar>
>>  
>> or adding this following maven dependency:
>>
>> 
>>
>>  com.google.gwt
>>
>>  elemental2-experimental
>>
>>  16-06-30
>>
>> 
>>
>> Then, inherits the elemental2 module:
>>
>> 
>>
>> This experimental version works only with the last 2.8-snapshot release 
>> of GWT.
>>
>> The goal of this release is to get feedback so don’t hesitate to report 
>> any bugs, issues, concerns you have on this mailing list.
>>
>>
>> Important note: This is an experimental release and without doubt the 
>> future updates until the final release are going to break code!  
>>
>> - 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/2aaa5dab-26f6-47bc-9b20-64a93fdbb077%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

yep it's planned

On Sunday, July 3, 2016 at 3:13:17 AM UTC+2, Paul Stockley wrote:
>
> Would it be possible to break the project into a few packages? It would 
> make it easier to find things.

-- 
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/24ab16a6-e67e-457c-a39f-9b85fff01cae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

yes, we are thinking about that. We would like also to add a feature 
checking system.
 AFAIC, I think this kind of wrapper code should be part of a separate 
library using elemental. I would like that elemental stays "close to the 
metal".
But we don't have decided anything yet now.

On Saturday, July 2, 2016 at 11:07:16 PM UTC+2, Manuel Carrasco Moñino 
wrote:
>
> I'm wondering if it would be possible to have type-safe convenience 
> methods for creating elements, so as the user does not have to provide the 
> string tag name, nor cast the object, maybe something like :
>
> HTMLButtonElement button = HTMLButtonElement.createElement();
>
> instead of
>
> HTMLButtonElement button = (HTMLButtonElement) 
> document.createElement("button");
>
>
>
> El sáb., 2 jul. 2016 a las 4:38, 'Goktug Gokdogan' via GWT Contributors (<
> google-web-toolkit-contributors@googlegroups.com >) escribió:
>
>> Closure extern definition uses a union type here:
>>
>> https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_event.js#L34
>>
>> So it accepts either EventListener interface or a function.
>>
>> When we see a union type, we generate overloads for each type so 
>> Elemental should provide overloads that includes both. And it seems like it 
>> does. If not please let us know.
>>
>> On Fri, Jul 1, 2016 at 3:39 AM, Jens > 
>> wrote:
>>
>>>
>>> Thanks, now makes sense. I get confused with the JsFunction 
 JsType(native) because elemental2 has some callbacks as JsFunction and 
 others as JsType(native), now an actual elemental2 question; what criteria 
 is used to apply JsFunction (ex. elemental2.Node.AddEventListenerCallback) 
 instead of JsType (ex. elemental2.JsType)?

>>>
>>> I think its the result of definition of EventTarget.addEventListener():
>>>
>>> *listener - The object that receives a notification (an object that 
>>> implements the Event 
>>>  interface) when an 
>>> event of the specified type occurs. This must be an object implementing the 
>>> EventListener 
>>>  interface, 
>>> or simply a JavaScript function 
>>> .*
>>>
>>> The EventListener interface is a defined API and thus a @JsType(isNative 
>>> = true) interface has been generated. But to conform to "or simply a 
>>> JavaScript function" there is also an AddEventListenerCallback that is a 
>>> @JsFunction. Not sure if this distinction has any real value, in a hand 
>>> coded elemental2 I would have only created a @JsFunction interface 
>>> EventListener
>>>
>>> -- 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/73b36bdb-c496-4768-a221-21fe8b5a437c%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/CAN%3DyUA0ZfCbS%2Bnwtre0QuAnhDdLYz%2B3LuzXqD3WqoWqK%3DFe%2BEg%40mail.gmail.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/f6baffb5-dbc8-476f-8690-591a36d31043%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Julien Dramaix]

I'll try to find some time next week for uploading examples on my github
account.

A simple example could be:

package elemental.sample.simple;

import static elemental2.Global.alert;
import static elemental2.Global.document;

import com.google.gwt.core.client.EntryPoint;

import elemental2.Event;
import elemental2.EventListener;
import elemental2.HTMLButtonElement;

public class SimpleApp implements EntryPoint{
  public void onModuleLoad() {
final HTMLButtonElement button = (HTMLButtonElement)
document.createElement("button");
button.textContent = "Click me";
button.addEventListener(
"click",
new EventListener() {
  @Override
  public void handleEvent(Event evt) {
button.parentNode.removeChild(button);
alert("Button has been removed.");
  }
});
document.body.appendChild(button);
  }
}

Elemental2.Global can be considered as the entry point of the library. It
gathers all methods/fields available from the global scope (but not the
window API).

On Thu, Jun 30, 2016 at 12:15 PM Matic Petek  wrote:

> Hi,
>   I would be nice If you could publish simple example how to start using
> it.
> Regards,
>    Matic
>
> On Thursday, June 30, 2016 at 2:23:51 AM UTC+2, Julien Dramaix wrote:
>>
>> A new experimental version of Elemental2 using the new JsInterop
>> specification has been pushed on Sonatype today.
>>
>> You can try it by downloading the jar file
>> <https://oss.sonatype.org/service/local/repositories/google-releases/content/com/google/gwt/elemental2-experimental/16-06-30/elemental2-experimental-16-06-30.jar>
>> or adding this following maven dependency:
>>
>> 
>>
>>  com.google.gwt
>>
>>  elemental2-experimental
>>
>>  16-06-30
>>
>> 
>>
>> Then, inherits the elemental2 module:
>>
>> 
>>
>> This experimental version works only with the last 2.8-snapshot release
>> of GWT.
>>
>> The goal of this release is to get feedback so don’t hesitate to report
>> any bugs, issues, concerns you have on this mailing list.
>>
>>
>> Important note: This is an experimental release and without doubt the
>> future updates until the final release are going to break code!
>>
>> - 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/01963a7c-7972-4fd9-88ef-629d0a7bcbac%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/01963a7c-7972-4fd9-88ef-629d0a7bcbac%40googlegroups.com?utm_medium=email&utm_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%3D5M5DQS--awYZ1bS8nHBu9po8Ne8JPY_ianrUjNZrSqyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Experimental release of Elemental2

['Julien Dramaix' via GWT Contributors]

A new experimental version of Elemental2 using the new JsInterop
specification has been pushed on Sonatype today.

You can try it by downloading the jar file

or adding this following maven dependency:



 com.google.gwt

 elemental2-experimental

 16-06-30



Then, inherits the elemental2 module:



This experimental version works only with the last 2.8-snapshot release of
GWT.

The goal of this release is to get feedback so don’t hesitate to report any
bugs, issues, concerns you have on this mailing list.


Important note: This is an experimental release and without doubt the
future updates until the final release are going to break code!

- 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/CABXeq2Q%3DuH8beWj4tiG28tycASsJxK8mnxxNPZnEykUeTcMWXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8 RC1 release notes.

['Julien Dramaix' via GWT Contributors]

Dear contributors,

we've started a pull request on github for the GWT 2.8RC1 release note:

https://github.com/gwtproject/gwt-site/pull/181

Please review and comment if something is missing.

Julien,
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/CABXeq2T9q7eo-RucKh9rJwJhht5ocsRAhPQZKM2gpGo0OfW53w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 - What's the big secret?

[Julien Dramaix]

Elemental is not secret, it is not ready yet...

Stay tuned, in few days we should push an experimental version of elemental
using JsInterop new specification.

- Julien

On Thu, Jun 16, 2016 at 1:13 PM Leif Åstrand  wrote:

> Elemental 2 is a completely new project that is being developed internally
> by Google, but their intention is to publish it as open source once the
> maturity of the code matches their internal threshold.
>
> On Thursday, June 16, 2016 at 10:28:39 AM UTC+3, Alex White wrote:
>>
>> Just wondering where the source code is and why it has not been published
>> before a major release for an allegedly open source project. Is the big
>> secret that it won't be published?
>>
>>
>> --
> 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/f5ec5e86-ffbc-41ca-b007-d337b4bf5caf%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/CABb_3%3D5MjFXjniTc%2BXzUfE2%2BF19ti5G9WKm0S2X7shtLpa6MHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

This is really nice!

Could you create a pull request on the existing Release note and add the
missing items ?

On Tue, Dec 8, 2015 at 3:58 AM Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:

> Hi contributors,
>
> I've created a google doc <https://goo.gl/pLrVkl> with full GWT 2.8.0
> release notes. It's divided by features/components and links for each
> commit. I didn't put reverted commits, and fixes over features like
> JSInterop. Everyone can put comments. It could be added later at GWT
> official documentation once gwt 2.8.0 is completed.
>
> Juan
>
> On 7 December 2015 at 11:15, István Horváth  wrote:
>
>> ok, i have PR for this, i hope it fits Google's needs.
>>
>> 2015. december 7., hétfő 15:47:50 UTC+1 időpontban Julien Dramaix a
>> következőt írta:
>>>
>>> Feel free to fill a patch for that :)
>>>
>>> On Mon, Dec 7, 2015 at 2:28 PM István Horváth  wrote:
>>>
>>>> it would nice to have if you update the release notes page with exact
>>>> dates on all of the version on both the links and the linked details too.
>>>>
>>>> http://www.gwtproject.org/release-notes.html
>>>>
>>>>
>>>> 2015. december 4., péntek 10:51:13 UTC+1 időpontban Daniel Kurka a
>>>> következőt írta:
>>>>>
>>>>> 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
>>>>> <http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_BETA1>
>>>>> .
>>>>>
>>>>> Please start testing and let us know about any issues you encounter by
>>>>> either discussion here or filing bugs on github
>>>>> <https://github.com/gwtproject/gwt/issues/new>.
>>>>>
>>>>> -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/06401611-3eeb-4647-9fca-69459939aa8d%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/06401611-3eeb-4647-9fca-69459939aa8d%40googlegroups.com?utm_medium=email&utm_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/5ac770a2-db1c-4676-b167-8632289decae%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/5ac770a2-db1c-4676-b167-8632289decae%40googlegroups.com?utm_medium=email&utm_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%2BkiFseLrH5LPYM%3DkmqBFNrjqJOuvq28ZC9vvpfiM6xcKxNAYQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFseLrH5LPYM%3DkmqBFNrjqJOuvq28ZC9vvpfiM6xcKxNAYQ%40mail.gmail.com?utm_medium=email&utm_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%3D45OQA06rpq0J3KjZTSiqt-w7TqaNx9QnUV%2Be9VYsPU4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

Feel free to fill a patch for that :)

On Mon, Dec 7, 2015 at 2:28 PM István Horváth  wrote:

> it would nice to have if you update the release notes page with exact
> dates on all of the version on both the links and the linked details too.
>
> http://www.gwtproject.org/release-notes.html
>
>
> 2015. december 4., péntek 10:51:13 UTC+1 időpontban Daniel Kurka a
> következőt írta:
>>
>> 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/06401611-3eeb-4647-9fca-69459939aa8d%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/CABb_3%3D5%3DYLe_WNJbvc48mmfRO8Ds1WqqtDwNvhhPD3C66DJHpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Maven Samples update for GWT 2.8

[Julien Dramaix]

GSS is not turned on by default because we want that people migrate to GWT
2.8 without being blocked by the GSS migration.
As I said in my previous mail, the compiler is smart enough to choose the
right resource file (if both are provided) depending wether GSS is enabled
or not. If you find a .css file in the sdk that doesn't have its gss
equivalent, it's a bug.

Julien

On Thu, Dec 3, 2015 at 4:38 AM Brandon Donnelson 
wrote:

> I updated the Maven samples.
>
> https://gwt-review.googlesource.com/14050
>
>
> I'm not sure why I had to turn on GSS in the module. Possible I missed
> where it was getting turned off at. Anyway, the patch up above fixes the
> gss errors. By the way if you're wondering why I had to turn on gss
> conversion, it's b/c there is some legacy css in the core.
>
>
> --
> 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/9ea6e5fa-dcc7-4329-84b0-8957d95fa993%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/CABb_3%3D726UXCNnLTdsQtouitzcuQh6m3qEoea1Va-cuiOoGKaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Samples .css issue?

[Julien Dramaix]

If you provide both the .css and .gss versions of a file. The
GssResourceGenerator is smart enough to use the gss version of the file
when gss is enabled even if you specify the css version in the @Source
annotation.
GSS is still disabled by default, so we have to keep the backward
compatibility.

On Thu, Dec 3, 2015 at 2:55 AM Brandon Donnelson 
wrote:

> Should this be .gss?
>
> com/google/gwt/user/cellview/client/DataGrid.css in com.google.gwt.user.
> cellview.client.DataGrid?
>
>
> Thanks,
>
> Brandon
>
>
>
> --
> 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/fcb093a2-dd20-4b30-9606-9e1ed290cb0a%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/CABb_3%3D7YtNCA6pjXLMV_p4n16hzROcq%2B3TNfNU7G-n%2BYUu9vKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

[Julien Dramaix]

> Typescript uses type definitions for 3rd party JS libraries (
http://definitelytyped.org/). Potentially something similar could be done
for GWT/Java or even one could leverage the Typescript type definitions to
automatically create Java wrappers.

I'm working on a tool that could convert these d.ts files to Java classes
annotated with JsInterop. Stay tuned.

On Tue, Nov 24, 2015 at 10:28 AM Ümit Seren  wrote:

> Regarding the Java wrapper for 3rd party libraries:
> Typescript uses type definitions for 3rd party JS libraries (
> http://definitelytyped.org/). Potentially something similar could be done
> for GWT/Java or even one could leverage the Typescript type definitions to
> automatically create Java wrappers.
>
> AFAIK the gwt-polymer-elements (
> https://github.com/vaadin/gwt-polymer-elements) wrapper generates the
> Java custom element wrappers by leveraging the polymer static analyser (
> https://github.com/Polymer/hydrolysis), so there is no need to generate
> those wrappers by hand.
>
> I am not that concerned regarding the future of GWT. IMHO having a typed
> language such as Java (especially as Java8 reduces boilerplate quite a bit)
> with a good JsInterop is the way to go.
> BTW the new Dart release (1.13) features a new JsInterop system that looks
> quite similar to GWT's one and they are also working on a dev_compiler,
> that looks a lot like what the J2CL compiler will do (supposed to make it
> easier to consume Dart code from JS).
>
> In the last ChromeDevSummit (https://developer.chrome.com/devsummit),
> that took place a couple of days ago, it became clear that Google is
> pushing the mobile web quiete a lot by exposing mroe and more native APIs
> and providing web-plattform primitives so that mobile web apps can compete
> with native apps.
> Until now performance and tooling has been much better for native app
> development but Google started to tackle the issues from different angles
> ranging from a fully type aware Javascript engine (Turbofan) to improved
> Dev Tools and new best practices (RAIL, app shell, service worker, etc).
> So I think GWT 3.0 (Elemental 2, JsInterop, J2Cl compiler) will be in a
> good place to leverage those things (maybe I am to optimistic and
> deliberately leaving out the pain of migration).
>
>
>
> On Monday, November 16, 2015 at 5:56:20 PM UTC+1, Robert Stone wrote:
>>
>>
>>
>> On Monday, 16 November 2015 12:34:51 UTC, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>>>>
>>>>
>>>>
>>>> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>>>>
>>>>>
>>>>> My worry about "just pick a mainstream JS framework and use it via
>>>>> JSInterop" is that if you're a) coupled to a JS environment for unit
>>>>> testing and b) interfacing with a framework that is inherently
>>>>> dynamic/untyped, what's the benefit of using GWT in the first place?
>>>>>
>>>>
>>>>
>>>> And this for me sums up GWTs main issues going forward. The benefit
>>>> before was that existing Java devs could use GWT to work on all the layers
>>>> of an application. GWT 3 will force (not a bad thing) Java devs to use
>>>> JavaScript for their views and will also force them to deal with
>>>> integrating JS and Java code.
>>>>
>>>
>>> I think Vaadin and Julien Dramaix showed during the last months how you
>>> can use GWT to create Web Components (through Polymer), so no J2CL or GWT 3
>>> won't "force Java devs to use JavaScript for their views".
>>> As for "forc[ing] them to deal with integrating JS and Java code", it
>>> shouldn't be much different from the current situation dealing with Element
>>> and NativeEvent (com.google.gwt.dom.*), Storage, Geolocation, etc. and
>>> Elemental 2 (to be released shortly after 2.8 AFAIK) should help bridging
>>> this gap.
>>>
>>
>> Yes and I agree, but taking this approach doesn't truly isolate the Java
>> devs from needing to know JavaScript as GWT/JsInterop is providing a very
>> thin wrapper over the JS framework of choice. Someone has to put that
>> wrapper in place be it a 3rd party or someone in the team and that someone
>> really does have to understand the underlying JS framework. At the end of
>> the day, the Java devs will benefit from having more of an understanding of
>> JS/HTML than they did in 'pure' GWT days. And again, I'm not saying this is
&g

Re: [gwt-contrib] Re: Elemental 2?

[Julien Dramaix]

It's a bit too early to answer to this question with absolute certainty but 
I don't think I can guarantee the full backward compatibility with the 
first version of elemental.

On Friday, November 20, 2015 at 10:50:26 AM UTC+1, James Horsley wrote:
>
> Thanks for the update Julien. Do you know if Elemental2 will be at all 
> backwards compatible with Elemental1? I was trying to decide on whether to 
> use the Elemental1 interfaces for something I'm working on.
>
> On Fri, Nov 20, 2015 at 9:32 AM 'Julien Dramaix' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com > wrote:
>
>> Yes I'm currently working on Elemental2 and other intersting stuffs 
>> around JsInterop. It's a bit to early to communicate something right now. 
>> But you can expect to have more news in one or two months.
>>
>> Julien
>>
>> On Thu, Nov 19, 2015 at 7:04 PM Goktug Gokdogan > > wrote:
>>
>>> We have been actively working on a JsInterop generator and Elemental 2.0 
>>> in the last month or so.
>>> We will make a separate Elemental release and yes that will be J2CL 
>>> ready.
>>> However I don't expect it to be released before the next quarter. Also 
>>> having other tools that are investigating the same problem and coming with 
>>> its own solutions usually helps us to learn new stuff.
>>>
>>> (adding dramaix@, as he is the one who is actively working on this and 
>>> might provide some feedback as well)
>>>
>>> On Thu, Nov 19, 2015 at 2:35 AM, Bademus l. >> > wrote:
>>>
>>>> Hello,
>>>> Excellent question! 
>>>> Please let me put my 2cents: 
>>>> I'm interested in Chrome Extension API for GWT, it also can be easily 
>>>> generated from Chrome's IDL.
>>>>
>>>> On Thursday, November 19, 2015 at 10:39:20 AM UTC+1, Rene Hangstrup 
>>>> Møller wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> A year ago I tried to write a tool for generating JsInterop classes 
>>>>> from WebIDL, I abandoned the project because there was no good solution 
>>>>> for 
>>>>> method overloading and constructors back then. I know others have 
>>>>> attempted 
>>>>> the same.
>>>>>
>>>>> It looks like the new JsInterop spec solves those problems, so i was 
>>>>> considering reviving that project, but I don't want to waste the time if 
>>>>> Elemental 2 is going to be released within the next couple of months.
>>>>>
>>>>> I guess it should be possible to release it as a separate project that 
>>>>> can be used from GWT 2.8 and the in the far future J2CL.
>>>>>
>>>>> Any chance that Elemental 2 will be available shortly or should I 
>>>>> build my own?
>>>>>
>>>>> Best regards
>>>>> Rene
>>>>>
>>>>> -- 
>>>> 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/9d50d507-f79a-4596-a259-a14213f37875%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/9d50d507-f79a-4596-a259-a14213f37875%40googlegroups.com?utm_medium=email&utm_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/CABXeq2Qe46G2ZcJHvSwMRnsWd4Ycw3fFf5R2OV6x9HcgNHQ5ZQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABXeq2Qe46G2ZcJHvSwMRnsWd4Ycw3fFf5R2OV6x9HcgNHQ5ZQ%40mail.gmail.com?utm_medium=email&utm_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/9069ea83-8229-46b6-8e1b-cb94f3eebe4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental 2?

['Julien Dramaix' via GWT Contributors]

Yes I'm currently working on Elemental2 and other intersting stuffs around
JsInterop. It's a bit to early to communicate something right now. But you
can expect to have more news in one or two months.

Julien

On Thu, Nov 19, 2015 at 7:04 PM Goktug Gokdogan  wrote:

> We have been actively working on a JsInterop generator and Elemental 2.0
> in the last month or so.
> We will make a separate Elemental release and yes that will be J2CL ready.
> However I don't expect it to be released before the next quarter. Also
> having other tools that are investigating the same problem and coming with
> its own solutions usually helps us to learn new stuff.
>
> (adding dramaix@, as he is the one who is actively working on this and
> might provide some feedback as well)
>
> On Thu, Nov 19, 2015 at 2:35 AM, Bademus l.  wrote:
>
>> Hello,
>> Excellent question!
>> Please let me put my 2cents:
>> I'm interested in Chrome Extension API for GWT, it also can be easily
>> generated from Chrome's IDL.
>>
>> On Thursday, November 19, 2015 at 10:39:20 AM UTC+1, Rene Hangstrup
>> Møller wrote:
>>>
>>> Hi
>>>
>>> A year ago I tried to write a tool for generating JsInterop classes from
>>> WebIDL, I abandoned the project because there was no good solution for
>>> method overloading and constructors back then. I know others have attempted
>>> the same.
>>>
>>> It looks like the new JsInterop spec solves those problems, so i was
>>> considering reviving that project, but I don't want to waste the time if
>>> Elemental 2 is going to be released within the next couple of months.
>>>
>>> I guess it should be possible to release it as a separate project that
>>> can be used from GWT 2.8 and the in the far future J2CL.
>>>
>>> Any chance that Elemental 2 will be available shortly or should I build
>>> my own?
>>>
>>> Best regards
>>> Rene
>>>
>>> --
>> 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/9d50d507-f79a-4596-a259-a14213f37875%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/CABXeq2Qe46G2ZcJHvSwMRnsWd4Ycw3fFf5R2OV6x9HcgNHQ5ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

[Julien Dramaix]

ches per
>> argument count in this version. And btw, method overloading never worked
>> earlier and we recently added support and just for native types.
>>
>> On Tue, Nov 10, 2015 at 4:19 PM, Manuel Carrasco Moñino <
>> man...@apache.org> wrote:
>>
>>
>> Another issue in the new implementation is that it's not supported any
>> more static shared fields in JsType native interfaces, I think if we
>> support static methods we should support static fields as well, or is there
>> i any reason to prevent it ?.
>>
>> On Tue, Nov 10, 2015 at 6:11 PM, Manuel Carrasco Moñino <
>> man...@apache.org> wrote:
>>
>> var args sounds pretty good, but some kind of overloading based on the
>> number of parameters like we had in gwt-exporter should cover many use
>> cases, compiler could give an error (like it does now) when it sees two
>> methods with the same-number-of-parameters signature.
>>
>>
>>
>> On Tue, Nov 10, 2015 at 5:59 PM, 'Roberto Lublinerman' via GWT
>> Contributors  wrote:
>>
>> No plan to support through Java implementors, although there are plans to
>> support varargs which would let you accomplish something similar.
>> On Nov 10, 2015 08:53, "Manuel Carrasco Moñino" 
>> wrote:
>>
>> I see, it works, thanks.
>>
>> Any plan to work as well with gwt exported classes ?
>>
>> On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix 
>> wrote:
>>
>> Method overloading works in native JsType JsType(isNative=true)
>>
>> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino 
>> wrote:
>>
>> Seems that method overloading is not working anymore with JS_RC mode, it
>> was working in JS mode though:
>>
>> Example:
>>
>>boolean validate()
>>boolean validate(String foo)
>>
>> Is it a feature not implemented yet, or it is not in the specification?
>>
>> Thanks
>> - Manolo
>>
>>
>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi 
>> wrote:
>>
>> Thanks Julien!!!
>>
>> This work fine!!
>>
>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>> escribió:
>>
>> As we are getting close to 2.8 release I wrote a new document that is
>> concentrating on jsinterop features to be released in 2.8:
>>
>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>
>> Please share your feedback.
>>
>> Thanks,
>>
>> Goktug
>>
>> --
>> 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/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com?utm_medium=email&utm_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/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com?utm_medium=email&utm_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%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com?utm_medium=email&u

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

[Julien Dramaix]

Thomas gets it all correct. I just want to add one thing: If you are happy
with the current GWT stack (uibinder + widget ...), stay with it. As I
mentioned during the key notes, the GWT 2.8 will be a long maintenance
release and you have now everything you need to do a great web app.

Don't try to already migrate an existing application to something that is
not there yet.

On Mon, Nov 16, 2015 at 1:51 PM Thomas Broyer  wrote:

>
>
> On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>>
>> Thanks for all the feedback. But it does not put my mind at rest right
>> now.
>>
>> It would have been much better if GWT 2.8 would have provided at
>> least the basis for the future of GUI development - because that was one of
>> its main selling points for me.
>>
>> I understand why element/widget/uibinder are going away, but right now
>> there is no low-level alternative that would allow a less painful migration
>> later on.
>>
>> I am not expecting a 100% backward compatibility with 3.0, but at least
>> some certainty that the code rewrites will be limited or easy, if we
>> restrain from using certain technologies. The only certainty we have right
>> now is that GWT 3.0 will compile Java into JavaScript, and all the rest
>> will change or will just disappear assuming that there will be 3rd party
>> extensions.
>>
>> If GWT does not offer a basis for widget and UI development then there
>> will be multiple incompatible GUI libraries or frameworks that will make it
>> difficult to mix.
>>
>
> Web Components to the rescue?
> As I just wrote above, Web Components can be written in Java with
> JsInterop, and can be consumed quite easily with GWT too (whether the
> component was written with GWT or not).
> I know that answer won't satisfies you as you have to deal with ancient
> IEs, but Google has no such need, and has, over the past year(s?),
> expressed its will to simply stop supporting them in GWT altogether (Vaadin
> and Sencha were those asking for keeping support in); so they won't invest
> in such backwards-compatibility (I'm talking about browser here).
>
>
>> I could take the approach of JsInterop with AngularJS, but Angular 2,x is
>> also not going to offer backward compatibility. So I solve one problem and
>> end up with another one.
>>
>> I guess I will be trying UiBinder with GQuery and not rely on Widget for
>> my project. The UiBinder might disappear, but we are using mostly plain
>> HTML and Bootstrap styles. So we are only interested in binding events. The
>> UiBinder templates will be easy to migrate later on.
>>
>> Any idea what is going on with Singular ? Is it also abandoned or will it
>> finally appear after GWT 2.8 is final ?
>>
>
> My impression was that they're waiting for J2CL (but I have absolutely no
> insight)
>
> --
> 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/02a9f89b-1420-4289-be10-f8094decdfe7%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/CABb_3%3D7mi3zxByYB2BK2o3M8e-adO-zgOLnG7inqd_RDo4kVcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

[Julien Dramaix]

Method overloading works in native JsType JsType(isNative=true)

On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino 
wrote:

> Seems that method overloading is not working anymore with JS_RC mode, it
> was working in JS mode though:
>
> Example:
>
>boolean validate()
>boolean validate(String foo)
>
> Is it a feature not implemented yet, or it is not in the specification?
>
> Thanks
> - Manolo
>
>
> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi 
> wrote:
>
>> Thanks Julien!!!
>>
>> This work fine!!
>>
>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>> escribió:
>>>
>>> As we are getting close to 2.8 release I wrote a new document that is
>>> concentrating on jsinterop features to be released in 2.8:
>>>
>>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>>
>>> Please share your feedback.
>>>
>>> Thanks,
>>>
>>> Goktug
>>>
>> --
>> 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/51f767f9-0afd-48fd-bef8-a9106b0d716a%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/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.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/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

[Julien Dramaix]

Create a native JsType (isNative=true)  named Promise with namespace set to
GLOBAL and define both constructors. It should work.

@JsType(isNative = true, namespace = JsPackage.GLOBAL)
public class Promise {
public Promise(PromiseFn fn){};
}


On Mon, Nov 9, 2015 at 2:57 PM Cristian Rinaldi  wrote:

> Goktug:
>Nice Work!!
>
>How can we handle constructors of native types that receive parameters?
>By Example Promise in JS:
>
>
> new Promise(*executor*);
> new Promise(function(resolve, reject) { ... });
>
>
> I resolve with a static method and JSNI:
>
> public final static native Promise createPromise(PromiseFn fn) /*-{
> return new $wnd.Promise(fn);
>  }-*/;
>
> @FunctionalInterface
> @JsFunction
> public interface PromiseFn {
> void call(ResolveFn resolve, RejectedFn rejected);
> }
>
> @FunctionalInterface
> @JsFunction
> public interface RejectedFn {
> void rejected(Object objs);
> }
>
>
> @FunctionalInterface
> @JsFunction
> public interface ResolveFn {
> void resolve(Object objs);
> }
>
> There is a more correct way to do this?
>
>
> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
> escribió:
>>
>> As we are getting close to 2.8 release I wrote a new document that is
>> concentrating on jsinterop features to be released in 2.8:
>>
>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>
>> Please share your feedback.
>>
>> Thanks,
>>
>> Goktug
>>
> --
> 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/bd13754e-f451-4de9-a763-50b571762909%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/CABb_3%3D5ORSsuxYPMi8ZXOwSafFb8BRVXaTbUtkt00tySnY5XUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Cannot build GWT anymore locally

[Julien Dramaix]

it has been updated but the new version is not deployed yet...

On Mon, Nov 2, 2015 at 11:49 AM Lars  wrote:

> Thank your for this information.
> We should update this link (
> http://www.gwtproject.org/makinggwtbetter.html#workingoncode) to share
> this with all :-)
>
> --
> 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/e9443b7e-82a2-42ec-93f7-84c466d89bc3%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/CABb_3%3D69pKy6b-9nXez7HNw8Dxb-6Nd3qVynofzJH9AKPJpi0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Submit an issue destination on Google Code

[Julien Dramaix]

Done.

Julien

On Sat, Jul 18, 2015 at 12:52 AM Brandon Donnelson 
wrote:

> Would you like to change the submit an issue link target on Google Code?
>
> https://code.google.com/p/google-web-toolkit/
>
> Thanks,
> Brandon
>
> --
> 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/ea1f006d-3a2d-4ed1-88f3-7e5e9bb2fd46%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/CABb_3%3D4Qq%3DN-PDp%2BmijxxFy_Ma-mmrgOJEcW7YUmruYG9OCZNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

> CssResources and such might be a bit more work... we were planning to
move to GssResources ... will those remain ? probably not...

CssResources will continue to work, the generator can be adapted to use APT
api instead of GWT generators.

> Widgets ... by switching to GQuery we can avoid widgets for most cases
(although I will have a dependency on Element. But here again, I am sure
there will be a replacement for Element using Elemental (and hopefully a
GQuery update to moves to something else ?)

GQuery is now supported by Arcbees and it should not be too hard to use
elemental if needed.

On Mon, Jun 15, 2015 at 11:34 AM David  wrote:

> Daniel,
>
> Thanks for the background info.
>
> In my applications (non public web apps for banking purposes)  I tend to
> use GIN, Guava, UiBinder + Widgets + GWT-RPC.
>
> - GWT-RPC has been a limitation (I filled several issues in the passed)
> and I was looking for a REST/JSON replacement but it was not available at
> the time (now it is). So I can already move away from GWT-RPC.
> - UiBinder is really fundamental, but if we need to switch to pure HTML
> then it should not be that hard to do, UiBinder files are already 80% pure
> HTML anyway. CssResources and such might be a bit more work... we were
> planning to move to GssResources ... will those remain ? probably not...
> - Widgets ... by switching to GQuery we can avoid widgets for most cases
> (although I will have a dependency on Element. But here again, I am sure
> there will be a replacement for Element using Elemental (and hopefully a
> GQuery update to moves to something else ?)
> - CellWidgets. We depend and enhance the various cellWidgets a lot (adding
> resizing, filtering, dynamic loading, custom generators to generate the
> columns, ...). These will be hard to replace at this point (I do like the
> Vaadin Grid ... who knows).
>
> Is Singular planned to be a replacement for UiBinder or is it too early to
> ask that question ?
>
> Greets,
> David
>
>
> On Mon, Jun 15, 2015 at 11:05 AM James Horsley 
> wrote:
>
>> Thanks Daniel.
>>
>> It's great that the steering committee are discussing the topic this
>> early in the process; in particular, in the context of how GWT dev's can
>> help themselves to be future proof (e.g. your Modernizing GWT talk).
>>
>> I completely understand how certain GWT generator based libraries that
>> require global knowledge don't fit with APT (e.g. GWT-RPC maybe needing the
>> transportable types explicitly listed). But, at a glance, it seems like
>> other high adoption libraries like UiBinder and the widget library (maybe
>> even just some top level pieces?) can be retrofitted and released as
>> separate projects to work with the transpiler.
>>
>> Hopefully we can leverage the opinions and contributions of the GWT
>> community to determine what are "essential" libraries to carry forward and
>> implement plans to make this happen. A few big helping points here would be:
>>
>> 1) Clearly documented ways to future proof new development. What to use,
>> what to avoid, examples, etc.
>> 2) Early access to the transpiler when you have a basic API settled, so
>> that we can start working on converting our favourite libraries that the
>> steering committee don't have time for.
>> 3) Access to Singular. This gives people a future proof view layer to
>> work with and I think it will boost confidence/morale for those concerned
>> about the 3.0 transition.
>>
>> Cheers,
>> James
>>
>> On Sunday, June 14, 2015 at 8:02:11 PM UTC+1, Daniel Kurka wrote:
>>
>>> 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 relea

[gwt-contrib] GSS and GWT 2.8

[Julien Dramaix]

Dear GWT lovers,

It has been decided not to turn GSS on by default in GWT 2.8 in order make
the migration to the new GWT release simpler and smoother for everyone and
let people migrate at their own timeline.

You will still have to use the configuration property CssResource.enableGss
to enable GSS.

A new configuration property has been added:
CssResource.gssDefaultInUiBinder. This config property allows you to enable
GSS by default in uibinder (ne need anymore to add the attribute  gss=true
in your inline style)

More information in this document:
https://docs.google.com/document/d/1vlYUDD7O5HfJ-7ctGDepUluQGM-8xjMJhV-EkOnPyQU/

Don't hesitate to comment the document or give you opinion by replying to
this mail.

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%3D6ji2so_rpOmRCUOqXSkauD9rSSxmcrmp6g5MWrObzjxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Errors during GWTTestCase and uibinder

[Julien Dramaix]

Hi Everyone,

Since yesterday, I'm not able to start any GWTTestCase using uibinder, I've
got the error below.
An idea  ?

Unexpected exception occurred while parsing HTML snippet
org.xml.sax.SAXNotRecognizedException: Feature '
http://cyberneko.org/html/features/scanner/allow-selfclosing-tags' is not
recognized.
at org.apache.xerces.parsers.AbstractSAXParser.setFeature(Unknown Source)
at
com.gargoylesoftware.htmlunit.html.HTMLParser.parseFragment(HTMLParser.java:162)
at
com.gargoylesoftware.htmlunit.html.HTMLParser.parseFragment(HTMLParser.java:129)
at
com.gargoylesoftware.htmlunit.javascript.host.html.HTMLElement.parseHtmlSnippet(HTMLElement.java:1105)
at
com.gargoylesoftware.htmlunit.javascript.host.html.HTMLElement.setInnerHTML(HTMLElement.java:1004)
at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
net.sourceforge.htmlunit.corejs.javascript.MemberBox.invoke(MemberBox.java:120)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptableObject$GetterSlot.setValue(ScriptableObject.java:295)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptableObject.putImpl(ScriptableObject.java:2796)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptableObject.put(ScriptableObject.java:521)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptableObject.putProperty(ScriptableObject.java:2479)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptRuntime.setObjectProp(ScriptRuntime.java:1569)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptRuntime.setObjectProp(ScriptRuntime.java:1564)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpretLoop(Interpreter.java:1253)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpret(Interpreter.java:798)
at
net.sourceforge.htmlunit.corejs.javascript.InterpretedFunction.call(InterpretedFunction.java:105)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$4.doRun(JavaScriptEngine.java:609)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:669)
at net.sourceforge.htmlunit.corejs.javascript.Context.call(Context.java:602)
at
net.sourceforge.htmlunit.corejs.javascript.ContextFactory.call(ContextFactory.java:507)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.callFunction(JavaScriptEngine.java:616)
at
com.google.gwt.dev.shell.HtmlUnitSessionHandler.invoke(HtmlUnitSessionHandler.java:228)
at
com.google.gwt.dev.shell.BrowserChannelClient.reactToMessages(BrowserChannelClient.java:218)
at
com.google.gwt.dev.shell.BrowserChannelClient.reactToMessagesWhileWaitingForReturn(BrowserChannelClient.java:165)
at
com.google.gwt.dev.shell.JavaObject.getReturnFromJavaMethod(JavaObject.java:61)
at com.google.gwt.dev.shell.JavaObject.call(JavaObject.java:122)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpretLoop(Interpreter.java:1531)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpret(Interpreter.java:798)
at
net.sourceforge.htmlunit.corejs.javascript.InterpretedFunction.call(InterpretedFunction.java:105)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$4.doRun(JavaScriptEngine.java:609)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:669)
at net.sourceforge.htmlunit.corejs.javascript.Context.call(Context.java:602)
at
net.sourceforge.htmlunit.corejs.javascript.ContextFactory.call(ContextFactory.java:507)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.callFunction(JavaScriptEngine.java:616)
at
com.google.gwt.dev.shell.HtmlUnitSessionHandler.invoke(HtmlUnitSessionHandler.java:228)
at
com.google.gwt.dev.shell.BrowserChannelClient.reactToMessages(BrowserChannelClient.java:218)
at
com.google.gwt.dev.shell.BrowserChannelClient.reactToMessagesWhileWaitingForReturn(BrowserChannelClient.java:165)
at
com.google.gwt.dev.shell.JavaObject.getReturnFromJavaMethod(JavaObject.java:61)
at com.google.gwt.dev.shell.JavaObject.call(JavaObject.java:122)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpretLoop(Interpreter.java:1531)
at
net.sourceforge.htmlunit.corejs.javascript.Interpreter.interpret(Interpreter.java:798)
at
net.sourceforge.htmlunit.corejs.javascript.InterpretedFunction.call(InterpretedFunction.java:105)
at
net.sourceforge.htmlunit.corejs.javascript.ContextFactory.doTopCall(ContextFactory.java:405)
at
com.gargoylesoftware.htmlunit.javascript.HtmlUnitContextFactory.doTopCall(HtmlUnitContextFactory.java:309)
at
net.sourceforge.htmlunit.corejs.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3031)
at
net.sourceforge.htmlunit.corejs.javascript.InterpretedFunction.call(InterpretedFunction.java:103)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$4.doRun(JavaScriptEngine.java:609)
at
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:669)
at net.sou

Re: [gwt-contrib] Re: GWT Meetup 2015

[Julien Dramaix]

We could also discuss about the website. Several things need to be fixed
and we could discuss how to reorganize content of the website (old articles
should be removed for instance)

On Thu, May 7, 2015 at 3:04 PM Brandon Donnelson 
wrote:

> Sounds good, I can whip something up. I'll should have some new docs,
> videos and plugin preview ready to go too.
>
> Have a good day,
> Brandon Donnelson
> +Follow Me <https://plus.google.com/u/0/111739836936169749229/posts>
>
> On Thu, May 7, 2015 at 5:05 AM, Julien Dramaix 
> wrote:
>
>> It would be nice to have a status about the Eclipse plugin indeed.  IIRC,
>> sessions are recorded so people will be able to watch your session
>> afterwards.
>>
>> On Thu, May 7, 2015 at 7:34 AM Brandon Donnelson 
>> wrote:
>>
>>> If folks are interested I could talk about the Eclipse plugin...
>>> thoughts?
>>>
>>> --
>>> 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/5b30bfc8-bd86-40b0-8910-b5cd8a72fa3d%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/5b30bfc8-bd86-40b0-8910-b5cd8a72fa3d%40googlegroups.com?utm_medium=email&utm_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/CKG8rWCN5Ok/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/CABb_3%3D7w8C1y498Da1rWgWstxkRed-Nz0dZn2wFsAu0FNHwxMQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7w8C1y498Da1rWgWstxkRed-Nz0dZn2wFsAu0FNHwxMQ%40mail.gmail.com?utm_medium=email&utm_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/CAPnsdHQNSfHyno0AERchcGn7HGSGb%3DbwVq8DwT3X9jSJLo-ZGA%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPnsdHQNSfHyno0AERchcGn7HGSGb%3DbwVq8DwT3X9jSJLo-ZGA%40mail.gmail.com?utm_medium=email&utm_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%3D7sauD7RxfE4_YL6Mm4%3D0Jpxz-RM_8jRix30HjHCBGNoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT Meetup 2015

[Julien Dramaix]

It would be nice to have a status about the Eclipse plugin indeed.  IIRC,
sessions are recorded so people will be able to watch your session
afterwards.

On Thu, May 7, 2015 at 7:34 AM Brandon Donnelson 
wrote:

> If folks are interested I could talk about the Eclipse plugin... thoughts?
>
> --
> 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/5b30bfc8-bd86-40b0-8910-b5cd8a72fa3d%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/CABb_3%3D7w8C1y498Da1rWgWstxkRed-Nz0dZn2wFsAu0FNHwxMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Upcoming overhaul to JsInterop annotations in preparation towards v1.0 release

[Julien Dramaix]

I'm really more in favor of the second options because (in addition to
Jens' arguments):
- it's more readable to have several meaningful annotations than one with
several parameters. And I think it's more Javaish. simple example :
@JsIgnore vs @Js(ignore=true)
- IMO, the option 1 won't be simpler to learn for developper and I think
instead it will be more confusing for the gwt developers. Most  of
parameters on the annotations cannot be used simultaneously and can be used
only on specific case (for instance: exports parameter has only a meaning
when the annotation is on type)




On Wed, Apr 22, 2015 at 6:06 AM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Yes and no depending what you mean.
>
> Before answering that I think there might have been some confusion the way
> I listed the options in the doc so let me try to summarize it again.
>
> There are 3 options.
>
> Option 1 uses @Js annotation everywhere. There is no other annotation. The
> @Js annotation can be applied to a class and in general it will behave
> similar to applying the annotation to all public members (if that is what
> you meant as syntactic sugar).
> This is the one that is described first in the doc and it is the direction
> we are heading right now.
>
> Option 2 uses @JsType/@JsFunction/@JsLiteral for types and @JsMember for
> members. @JsExport, @JsProperty, @JsMethod etc. are still gone (if that's
> what you meant with syntactic sugar). @JsNamespace is still used for
> setting namespaces where needed. So this is more or less the same design as
> Option 1 but separates the annotation used at class level from the one used
> at members.
> This is listed as "Alternative 1" in the doc. Originally this was the
> direction we were heading and it was described at the beginning while
> Option 1 was listed as "Alternative 1". I changed the order because John
> and Roberto both argued having single annotation (i.e. @Js) is simpler.
>
> Option 3 uses @JsImport/JsExport and it is completely separate design from
> the first two options.
> This is listed as "Alternative 2".
>
> Personally I am more towards Option 2 (see the pros and cons for the
> Option 2 in the doc) but I am getting mixed signals from outside so I need
> more feedback from developers.
>
>
> On Tue, Apr 21, 2015 at 6:21 PM, 'Ray Cromwell' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> Goktug, I though we were keeping @JsType and others as syntactic sugar?
>>
>>
>> On Tue, Apr 21, 2015 at 5:40 PM, Jens  wrote:
>>
>>> Damn it, Safari crashed. So now a shorter version of my answer:
>>>
>>> First I agree that the current design has become quite confusing.
>>> Personally I really dislike the single @Js annotation approach because:
>>> - can be applied everywhere so you throw away some compile time checks
>>> provided by Java's @Target annotation
>>> - exports vs. export is a bit misleading. One must be used with
>>> interfaces/classes the other with methods. That issue only exists because
>>> @Js alone has no real meaning.
>>> - You have to type more because it is always annotation name + property
>>> + value if you can't stick with the default "@Js".
>>> - Can't see a good use case for splitting exports in ALL,
>>> INSTANCE_MEMBERS and STATIC_MEMBERS. When I want to export a class I want
>>> to export its public API.
>>>
>>>
>>> Personally what describes JsInterop best is the alternative using the
>>> import/export concepts. So I would stick with:
>>>
>>> Import/Export types:
>>>
>>> @JsImport: can only be applied on interfaces.
>>> @JsExport: always exports all public API in a given scope (package,
>>> class, method). So no ALL, INSTANCE_MEMBER, STATIC_MEMBER distinction.
>>> @JsIgnore can be used to opt-out selectively.
>>>
>>> Configure import/export:
>>>
>>> @JsNamespace: import/export from/to namespace
>>> @JsName: workaround reserved keywords
>>> @JsProperty: mark method as JS property
>>> @JsIgnore: opt-out of export. Might even be useful for import, e.g. do
>>> not generate trampoline for annotated default method.
>>>
>>> Special constructs:
>>>
>>> @JsLiteral
>>> @JsFunction (currently it seems not to be a real function which breaks
>>> interop
>>> 
>>> )
>>>
>>>
>>> I guess that is the cleanest you can get. Not sure what @JsOpaque is
>>> good for?!
>>>
>>> -- 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/778b8f0b-8cc1-4a90-84d5-39c1b9c02afb%40googlegroups.com
>>> 

Re: [gwt-contrib] JsInterop retrofit

[Julien Dramaix]

Hi all,

Finally, did you made a decision ? 

I like very much the *native methods* approach for its simplicity and a 
test library like PowerMock seems to be able to mock native methods. But 
Ray seems to have some concerns about using class instead of Interface. So 
what was the selected approach ?

Julien

On Wednesday, November 5, 2014 at 10:37:21 PM UTC+1, Cristian Rinaldi wrote:
>
> @goktug
> Thanks for the answer!!
>
>
> El miércoles, 5 de noviembre de 2014 17:34:51 UTC-3, Goktug Gokdogan 
> escribió:
>>
>> It is compiler magic. The compiler understands from PrototypeOfJsType and 
>> assumes any methods in the class are native, hence ignores the method body.
>>
>> On Wed, Nov 5, 2014 at 4:08 AM, Cristian Rinaldi  
>> wrote:
>>
>>> @goktug I like this option, it is expressive and concise.
>>>
>>> But I have a question, 
>>> The code generated for the prototype, suppose we are extending some 
>>> existing JS functionality and want to add some function, the prototype 
>>> generated will have native code?, how this prototype generates subyasente 
>>> invoking the JS function?
>>>
>>> by example:
>>>
>>> @JsType(prototype = "Document")
>>> public interface Document {
>>>
>>> public HTMLElement createElement(String div);
>>>
>>> public HTMLElement getElementsByTagName(String body);
>>>
>>> @JsProperty
>>> public HTMLBodyElement getBody();
>>>
>>> public NodeList querySelector(String selector);
>>>
>>> public NodeList querySelectorAll(String selector);
>>>
>>> class prototype extends Prototype_Document {}
>>> 
>>> 
>>> 
>>> }
>>>
>>> @PrototypeOfJsType(Document.class) 
>>> public class Prototype_Document{
>>> 
>>> 
>>> public NodeList querySelectorAll(String selector){
>>>//The question (How will called underlying code?) 
>>> }
>>> }
>>>
>>> public class MyDocument extends Document.prototype{
>>>   
>>>   public void myMethod(){
>>>//TODO
>>>   }
>>>
>>> }
>>>
>>> Cheers :)
>>>
>>>
>>>
>>>
>>> El sábado, 1 de noviembre de 2014 13:52:46 UTC-3, Goktug Gokdogan 
>>> escribió:

 There is also a third option.

 User writes:

 @JsType(prototype = "Object")interface JsObject {

   class prototype extends Prototype_JsObject {}

   interface Static {
 String[] keys(JsObject obj);
 JsObject defineProperties(JsObject obj, JsObject props);
   }

   static Static getStatic() {
 return new Static_JsObject();
   }

   static JsObject of(Object obj) {
 return obj instanceof JsObject ? (JsObject) obj : null;
   }

   @JsConstructor
   void constructor(String param);

   boolean hasOwnProperty(String prop);
   boolean isPrototypeOf(JsObject prop);
 }

 ​
 which generates:

 @PrototypeOfJsType(JsObject.class)public class Prototype_JsObject {
JsObject constructor(String param) { return null;}
boolean hasOwnProperty(String prop) { return false; }
boolean isPrototypeOf(JsObject prop) { return false; }
 }
 public class Static_JsObject implements Static {
   JsObject newInstance(String param) {
 return js("new Object($0)", param);
   }

   public String[] keys(JsObject obj) {
 return js("Object.keys($0)", obj);
   };

   public JsObject defineProperties(JsObject obj, JsObject props) {
 ...
   }
 }

 ​
 And usage looks like:

   MyObject extends JsObject.prototype {}

   JsObject.getStatic().keys( ... );

   JsObject.getStatic().newInstance( ... );

   JsObject.of(new Object());

 ​
 And it is perfectly testable.

 On Sat, Nov 1, 2014 at 8:25 AM, Stephen Haberman >>> > wrote:

>
> > I will try to summarize my thought process and different options that
> > I have played with so that you could get a better understanding where
> > I'm coming from and I hope it will provide good documentation for
> > future.
>
> Thanks for the email; I think the format was really useful.
>
> > One may argue that if we are committing to use some kind of DSL why
> > not use something else like IDL or xml etc. There are 3 main reasons
> > to use java + APT instead of others:
>
> I really want to advocate APT, as I've used it and do generally like 
> it,
> but frankly it can be a huge PITA for Eclipse. See long-standing issues
> e.g.:
>
> https://github.com/square/dagger/issues/126
>
> Granted, maybe someone can just fix Eclipse, but, in my experience, it
> can really ruin the first impressions for a project (1000s of compile
> errors due to missing generated code, and no hints that, btw, it's
> because the APT was not on the classpath/didn't run).
>
> > All the cons are around the testability aspect. For JRE testing,
> > native methods 

Re: [gwt-contrib] JsInterop Questions

[Julien Dramaix]

FYI, I've tested this morning with the last night's build and now it works
fine with sdm.

On Wed, Apr 1, 2015 at 9:10 PM Julien Dramaix 
wrote:

>
> > If you have JsExport on a class in the first compilation, it works fine
> right?
> Nope I doesn't work. Even in the first compilation I receive a "Uncaught
> ReferenceError: jdramaix is not defined"
>
> On Wed, Apr 1, 2015 at 8:15 PM 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> [+stalcup, +cromwellian]
>>
>> If you have JsExport on a class in the first compilation, it works fine
>> right? I guess, it doesn't work only if you add JsExport after the first
>> compilation?
>>
>> Last week we were suspecting exporting might not be working properly w/
>> SDM. We need to write some incremental compilation test to make sure this
>> works properly before 2.8.
>>
>>
>> On Wed, Apr 1, 2015 at 5:27 AM, Julien Dramaix 
>> wrote:
>>
>>> Thanks Goktug !
>>>
>>> That works better with GWT 2.8 indeed.
>>>
>>> However, it seems there is a bug with @JsExport and super dev mode in
>>> the last snapshot. When I use sdm, the prototype of my JsType is correctly
>>> defined (fields and function are defined with the right name) but the
>>> constructor is not exported and I cannot instantiated my Java object from
>>> Javascript.
>>>
>>> AgeSlider.java:
>>>
>>> @JsNamespace("jdramaix")
>>> @JsType
>>> public class AgeSlider {
>>>
>>>   public int age;
>>>
>>>   @JsExport
>>>   public AgeSlider() {
>>>   }
>>>
>>>// other public methods are exported
>>> }
>>>
>>> With sdm, in javascript, I'm not able to do: var slider = new
>>> jdramaix.AgeSlider();
>>>
>>> By looking a bit in the javascript code generated by sdm, the part
>>> exporting the constructor under AgeSlider is not present:
>>> _ = provide('jdramaix');
>>> _.AgeSlider = AgeSlider;
>>>
>>> That works fine with a normal compilation.
>>>
>>> Julien
>>>
>>>
>>> On Wed, Apr 1, 2015 at 2:07 AM 'Goktug Gokdogan' via GWT Contributors <
>>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
>>>> On Tue, Mar 31, 2015 at 2:30 PM, Julien Dramaix <
>>>> julien.dram...@gmail.com> wrote:
>>>>
>>>>> Dear GWT lovers,
>>>>>
>>>>> I've finally started to play with JsInterop in GWT 2.7 and mainly I'm
>>>>> trying to use JsInterop in order to write polymer components.
>>>>>
>>>>> So far, I have two questions:
>>>>>
>>>>> 1. I'm using super dev mode and so I'm obliged to use
>>>>> the CrossSiteIframeLinker. As the javascript code generated by GWT is
>>>>> loaded in an iframe, the exported types are not accessible from the main
>>>>> window (only from the iframe). The workaround I found to expose java type
>>>>> from the main window is to prefix my namespace by *$wnd*
>>>>>
>>>>> @JsNamespace("$wnd.jdramaix")
>>>>> public class AgeSliderImpl
>>>>>
>>>>> Isn't it a better way to do that ?
>>>>>
>>>>>
>>>> Yes, in 2.7 you need to use $wnd to expose your code to main window. In
>>>> GWT 2.8 snapshot, this is the default behavior, you don't need $wnd.
>>>>
>>>>
>>>>> 2. I want to expose some java field of my class to javascript field.
>>>>> I'm trying to use @JsProperty for this purpose but it seems not to work:
>>>>>
>>>>> @JsNamespace("$wnd.jdramaix")
>>>>> public class AgeSliderImpl implements AgeSlider {
>>>>>   public int age;
>>>>>
>>>>>   @Override
>>>>>   public int getAge() {
>>>>> return age;
>>>>>   }}
>>>>>
>>>>> @JsType
>>>>> public interface AgeSlider {
>>>>>   @JsProperty
>>>>>   int getAge();
>>>>>
>>>>> }
>>>>>
>>>>> If I try to access the field in the javascript console,it is undefined:
>>>>> > var slider = new jdramaix.AgeSliderImpl()
>>>>> >

Re: [gwt-contrib] JsInterop Questions

[Julien Dramaix]

> If you have JsExport on a class in the first compilation, it works fine
right?
Nope I doesn't work. Even in the first compilation I receive a "Uncaught
ReferenceError: jdramaix is not defined"

On Wed, Apr 1, 2015 at 8:15 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> [+stalcup, +cromwellian]
>
> If you have JsExport on a class in the first compilation, it works fine
> right? I guess, it doesn't work only if you add JsExport after the first
> compilation?
>
> Last week we were suspecting exporting might not be working properly w/
> SDM. We need to write some incremental compilation test to make sure this
> works properly before 2.8.
>
>
> On Wed, Apr 1, 2015 at 5:27 AM, Julien Dramaix 
> wrote:
>
>> Thanks Goktug !
>>
>> That works better with GWT 2.8 indeed.
>>
>> However, it seems there is a bug with @JsExport and super dev mode in the
>> last snapshot. When I use sdm, the prototype of my JsType is correctly
>> defined (fields and function are defined with the right name) but the
>> constructor is not exported and I cannot instantiated my Java object from
>> Javascript.
>>
>> AgeSlider.java:
>>
>> @JsNamespace("jdramaix")
>> @JsType
>> public class AgeSlider {
>>
>>   public int age;
>>
>>   @JsExport
>>   public AgeSlider() {
>>   }
>>
>>// other public methods are exported
>> }
>>
>> With sdm, in javascript, I'm not able to do: var slider = new
>> jdramaix.AgeSlider();
>>
>> By looking a bit in the javascript code generated by sdm, the part
>> exporting the constructor under AgeSlider is not present:
>> _ = provide('jdramaix');
>> _.AgeSlider = AgeSlider;
>>
>> That works fine with a normal compilation.
>>
>> Julien
>>
>>
>> On Wed, Apr 1, 2015 at 2:07 AM 'Goktug Gokdogan' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> On Tue, Mar 31, 2015 at 2:30 PM, Julien Dramaix <
>>> julien.dram...@gmail.com> wrote:
>>>
>>>> Dear GWT lovers,
>>>>
>>>> I've finally started to play with JsInterop in GWT 2.7 and mainly I'm
>>>> trying to use JsInterop in order to write polymer components.
>>>>
>>>> So far, I have two questions:
>>>>
>>>> 1. I'm using super dev mode and so I'm obliged to use
>>>> the CrossSiteIframeLinker. As the javascript code generated by GWT is
>>>> loaded in an iframe, the exported types are not accessible from the main
>>>> window (only from the iframe). The workaround I found to expose java type
>>>> from the main window is to prefix my namespace by *$wnd*
>>>>
>>>> @JsNamespace("$wnd.jdramaix")
>>>> public class AgeSliderImpl
>>>>
>>>> Isn't it a better way to do that ?
>>>>
>>>>
>>> Yes, in 2.7 you need to use $wnd to expose your code to main window. In
>>> GWT 2.8 snapshot, this is the default behavior, you don't need $wnd.
>>>
>>>
>>>> 2. I want to expose some java field of my class to javascript field.
>>>> I'm trying to use @JsProperty for this purpose but it seems not to work:
>>>>
>>>> @JsNamespace("$wnd.jdramaix")
>>>> public class AgeSliderImpl implements AgeSlider {
>>>>   public int age;
>>>>
>>>>   @Override
>>>>   public int getAge() {
>>>> return age;
>>>>   }}
>>>>
>>>> @JsType
>>>> public interface AgeSlider {
>>>>   @JsProperty
>>>>   int getAge();
>>>>
>>>> }
>>>>
>>>> If I try to access the field in the javascript console,it is undefined:
>>>> > var slider = new jdramaix.AgeSliderImpl()
>>>> > slider.age
>>>> < undefined
>>>>
>>>> But the method getAge exists:
>>>> > slider.getAge
>>>> < function getAge_0_g$(){
>>>> <   return this.age_3_g$;
>>>> < }
>>>> Same problem if I rename the method to age(). slider.age is defined by
>>>> point to a function.
>>>>
>>>> Does @JsProperty work (at least when we export Java to Javascript) in
>>>> GWT 2.7. ? If so how to use it ?
>>>>
>>>>
>>> @JsProperty met

Re: [gwt-contrib] JsInterop Questions

[Julien Dramaix]

Thanks Goktug !

That works better with GWT 2.8 indeed.

However, it seems there is a bug with @JsExport and super dev mode in the
last snapshot. When I use sdm, the prototype of my JsType is correctly
defined (fields and function are defined with the right name) but the
constructor is not exported and I cannot instantiated my Java object from
Javascript.

AgeSlider.java:

@JsNamespace("jdramaix")
@JsType
public class AgeSlider {

  public int age;

  @JsExport
  public AgeSlider() {
  }

   // other public methods are exported
}

With sdm, in javascript, I'm not able to do: var slider = new
jdramaix.AgeSlider();

By looking a bit in the javascript code generated by sdm, the part
exporting the constructor under AgeSlider is not present:
_ = provide('jdramaix');
_.AgeSlider = AgeSlider;

That works fine with a normal compilation.

Julien


On Wed, Apr 1, 2015 at 2:07 AM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> On Tue, Mar 31, 2015 at 2:30 PM, Julien Dramaix 
> wrote:
>
>> Dear GWT lovers,
>>
>> I've finally started to play with JsInterop in GWT 2.7 and mainly I'm
>> trying to use JsInterop in order to write polymer components.
>>
>> So far, I have two questions:
>>
>> 1. I'm using super dev mode and so I'm obliged to use
>> the CrossSiteIframeLinker. As the javascript code generated by GWT is
>> loaded in an iframe, the exported types are not accessible from the main
>> window (only from the iframe). The workaround I found to expose java type
>> from the main window is to prefix my namespace by *$wnd*
>>
>> @JsNamespace("$wnd.jdramaix")
>> public class AgeSliderImpl
>>
>> Isn't it a better way to do that ?
>>
>>
> Yes, in 2.7 you need to use $wnd to expose your code to main window. In
> GWT 2.8 snapshot, this is the default behavior, you don't need $wnd.
>
>
>> 2. I want to expose some java field of my class to javascript field. I'm
>> trying to use @JsProperty for this purpose but it seems not to work:
>>
>> @JsNamespace("$wnd.jdramaix")
>> public class AgeSliderImpl implements AgeSlider {
>>   public int age;
>>
>>   @Override
>>   public int getAge() {
>> return age;
>>   }}
>>
>> @JsType
>> public interface AgeSlider {
>>   @JsProperty
>>   int getAge();
>>
>> }
>>
>> If I try to access the field in the javascript console,it is undefined:
>> > var slider = new jdramaix.AgeSliderImpl()
>> > slider.age
>> < undefined
>>
>> But the method getAge exists:
>> > slider.getAge
>> < function getAge_0_g$(){
>> <   return this.age_3_g$;
>> < }
>> Same problem if I rename the method to age(). slider.age is defined by
>> point to a function.
>>
>> Does @JsProperty work (at least when we export Java to Javascript) in GWT
>> 2.7. ? If so how to use it ?
>>
>>
> @JsProperty methods defined in @JsType that is implemented by concrete
> classes does not work with GWT 2.7 (basically the scenario in your code
> snippet), it doesn't generate the code with a javascript property
> setter/getters.
>
> In GWT 2.8 snapshot, javascript property setter/getter are still not
> implemented (yet) but instead you can use @JsType with concrete class and a
> public field, and you can skip the JsType interface completely.
>
> i.e.
>
> @JsType
> public class AgeSlider {
>   public int age;}
>
> if you want to export the constructor, don't forget to add @JsExport as
> well.
>
> Thanks
>>
>> 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%3D6WZanScYy1ZqHBR23yssh9uvDLWe%3DquGaiixcpOusBog%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6WZanScYy1ZqHBR23yssh9uvDLWe%3DquGaiixcpOusBog%40mail.gmail.com?utm_medium=email&utm_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..

[gwt-contrib] JsInterop Questions

[Julien Dramaix]

Dear GWT lovers,

I've finally started to play with JsInterop in GWT 2.7 and mainly I'm
trying to use JsInterop in order to write polymer components.

So far, I have two questions:

1. I'm using super dev mode and so I'm obliged to use
the CrossSiteIframeLinker. As the javascript code generated by GWT is
loaded in an iframe, the exported types are not accessible from the main
window (only from the iframe). The workaround I found to expose java type
from the main window is to prefix my namespace by *$wnd*

@JsNamespace("$wnd.jdramaix")
public class AgeSliderImpl

Isn't it a better way to do that ?

2. I want to expose some java field of my class to javascript field. I'm
trying to use @JsProperty for this purpose but it seems not to work:

@JsNamespace("$wnd.jdramaix")
public class AgeSliderImpl implements AgeSlider {
  public int age;

  @Override
  public int getAge() {
return age;
  }}

@JsType
public interface AgeSlider {
  @JsProperty
  int getAge();

}

If I try to access the field in the javascript console,it is undefined:
> var slider = new jdramaix.AgeSliderImpl()
> slider.age
< undefined

But the method getAge exists:
> slider.getAge
< function getAge_0_g$(){
<   return this.age_3_g$;
< }
Same problem if I rename the method to age(). slider.age is defined by
point to a function.

Does @JsProperty work (at least when we export Java to Javascript) in GWT
2.7. ? If so how to use it ?

Thanks

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%3D6WZanScYy1ZqHBR23yssh9uvDLWe%3DquGaiixcpOusBog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Snapshot repo?

[Julien Dramaix]

Couldn't we configure sonatype to keep at least the last snapshot even if
we don't update the repository (because the build failed)  ?


On Thu, Mar 19, 2015 at 5:45 PM 'Roberto Lublinerman' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> We are looking into it and will be hopefully resolved soon.
>
> On Thu, Mar 19, 2015 at 8:15 AM, Colin Alworth  wrote:
>
>> It looks like the build is failing, and has been for some days:
>> http://build.gwtproject.org/job/gwt/49/#showFailuresLink
>>
>> Test Result (26 failures / -6)
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_bridgeMethodOverrideChain
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsCascadedGenerators
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dateStampChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatePreamble
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superClassOrder
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superFromStaleInner
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_deterministicUiBinder
>>
>> com.google.gwt.dev.CompilerTest.testDeterministicBuild_Draft_StackModeStrip
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_uiBinderCssChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unstableGeneratorReferencesModifiedType
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_functionSignatureChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_compileTimeConstantChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_transitivelyFoldableConstant
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_packagePrivateDispatch
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_regularClassMadeIntoJsoClass
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unreachableIncompatibleChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_typeHierarchyChange
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_defaultMethod
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeUnchangedJso
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeString
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_multipleClassGenerator
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_singleJsoIntfDispatchChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dualJsoIntfDispatchChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_generatorInputResourceChange
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsGenerator
>>
>> com.google.gwt.dev.CompilerTest.testIncrementalRecompile_carriesOverGeneratorArtifacts
>>
>>
>> On Thursday, March 19, 2015 at 8:04:34 AM UTC-5, Ali Akhtar wrote:
>>>
>>> Hey guys,
>>>
>>> Is there a maven repo to use for getting snapshot builds? Sonatype
>>> doesn't contain .jars,
>>>
>>> https://oss.sonatype.org/content/repositories/google-
>>> snapshots/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/
>>>
>>> And https://github.com/manolo/gwt-snapshot/ doesn't appear to have been
>>> updated for 28 days.
>>>
>>> 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/ad62891f-a1f0-4c59-ac18-7c6b877f2088%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/CAC7T7gk%3DDo5V1vK0wcEZX0Gu2386NiGcax-XTTFDtMWgR5z93g%40mail.gmail.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-contributo

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

[Julien Dramaix]

Sorry for my late reply.

I'm OK to not remove the code of the old css completely. I will propose
another patch for that.

> That will the make the upgrade unnecessarily harder
I just want to mention that the upgrade can be "hard" because UiBinder's
inner style will use GSS by default. And the only way to deactivate that
will be to add the attributes gss="false" on each inner style that are not
compatible with GSS.

Julien

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  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  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
>> 
>> .
>>
>> 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
> 
> .
> 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%3D4Ab2gNROSwwO7%2Bm1N%2B%3Dxmm-gx3NjR7LJLYGeY%3DxbsdtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

Dear GWT aficionados,

It has been decided to make GSS default in GWT 2.8. I think there are two
ways to do that:

1. Simply change the configuration property *CssResource.enableGss* to true
by default.

*Pros*: People can easily disable GSS by changing the config property
*Cons*: People can easily disable GSS :) and will not be forced to migrate
to GSS

2. Remove this configuration property and make GssResourceGenerator as
default generator for CssResource interface. With this option, the current
CssResourceGenerator is useless and can be deleted. The backward
compatibility is maintained by using the in- memory auto-conversion.

*Pros*: I have the feeling this option will force people to move to GSS or
at least make their CSS compliant with GSS (ready to be converted)
*Cons*: If there is a bug in the converter, that can stop people to upgrade
to GWT 2.8. But the converter was well tested (by google) and if a bug
occurs, we can produce a GWT 2.8.1 bug fixing release.

For GWT 3.0, the old syntax will not be supported anymore.

I've already done the changes related to the option 2:
https://gwt-review.googlesource.com/#/c/11800/ But I want to have your
opinion on that. So what do you guys think ? What is the best option ?

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%3D62w6cxqCDoh-zjd9gS1f5%2B8WEHK2FBA4kpGAHD0ihjbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GSS Custom Functions

[Julien Dramaix]

Hi Jeffrey,

Indeed this is a functionality we have to add (I've talked about that in my
presentation about GSS at gwt.create) for GWT 2.8.

But  it's not a good idea to give the possibility to developers to change
the behavior of GwtGssFunctionMapProvider by extending it and giving their
own implementation.

I think the best approach is that add a configuration-property named "
*CssResource.customGssFunctionMapProvider*". This value of this property
must be the fully qualified name of a class implementing the interface
*com.google.gwt.thirdparty.common.css.GssFunctionMapProvider*

Then the GssResourceGenerator looks to this property and create an instance
of this class and pass this instance to the GwtGssFunctionMapProvider.

GwtGssFunctionMapProvider will add the functions defined in this custom
GssMapFunctionProvider at the end of its map.

If you could propose a patch for that it would be great. Don't hesitate to
contact me if you need more info.

Julien


On Thu Feb 19 2015 at 11:30:09 AM Jeffrey Kleiss 
wrote:

> I noticed in the Closure Stylesheet docs that you can define your own
> custom functions in Java when you use the *--gss-function-map-provider* flag.
>
>
> Is there this option with GWT?
>
> I did notice that GwtGssFunctionMapProvider provides extra GSS GWT
> functions, but found no way of extending this for my own custom methods.
> The GssResourceGenerator constructs it via a new.  It would be nice to
> extend GwtGssFunctionMapProvider, or create a new class that
> GwtGssFunctionMapProvider uses to add custom functions.
>
> I would propose changing GwtGssFunctionMapProvider to:
>
> public class GwtGssFunctionMapProvider extends DefaultGssFunctionMapProvider {
>   private final ResourceContext context;
>
>   public GwtGssFunctionMapProvider() {
>   }
>
>   public void setResourceContext(ResourceContext context) {
> this.context = context;
>   }
>
>   @Override
>   public Map get() {
> Map gssFunctionMap = super.get();
>
> return ImmutableMap.builder().putAll(gssFunctionMap)
> // TODO add a namespace for gwt-specific function ?
> .put(EvalFunction.getName(), new EvalFunction())
> .put(ValueFunction.getName(), new ValueFunction())
> .put(ResourceUrlFunction.getName(), new ResourceUrlFunction(context))
> .build();
>   }
> }
>
>
> This would allow it to be constructed with no arguments, which allows 
> Reflection to easily be used to construct the object.  Next we could change 
> GssResourceGenerator to look for a configuration-property to be added to the 
> gwt.xml file to define the new class that must extend 
> GwtGssFunctionMapProvider, could then add custom functions.
>
>
> If this sounds like an interesting approach, I could start coding a patch to 
> accomplish this.
>
>
> Thanks,
>
> Jeffrey
>
>  --
> 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/3135e1af-bdce-45ed-bfbf-4d3192573e25%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/CABb_3%3D4EvyE6K6pTC0poy7-fk%3D7Yt5Cq80zt_8sYdpc%3DDbhyAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Stop Leeeeroy please stop

[Julien Dramaix]

This problem already occurred last year and Thomas had explained why (See
mail below). I've just set verified:-1 on the concerned patches in order to
stop Jenkins to do the presubmit check every 1h30.

I guess Monday, Manolo or Daniel will be able to fix that.

Thomas' explanation:
> The presubmit checks are scheduled by "buildglue"'s "presubmitter" which
polls Gerrit every minute for new changes [1]
> To avoid re-checking the same change every minute, it sets a timeout at,
you guessed it, 1h30. In other words, it'll check a given change every 1h30
until it "disappears" from the Gerrit query results.
> And the check is in two parts: one that runs in "presubmitter" and posts
the "Woo hoo" message, and then one that runs in Jenkins and updates the
Verified label.
> So what happens here is that Jenkins never updated the Verified label, so
the "fast style check" continues running every 1h30.

> I see that the jobs fail in Jenkins, and it looks like the last part
which updates Gerrit with the build status is never run.

> Manolo/Daniel, did you change anything lately about the gwt.presubmit job?

> [1] the Gerrit query is "(project:gwt status:open -label:Verified=1
-label:Verified=-1 -label:Code-Review=-1 -label:Code-Review=-2
ownerin:\"Jenkins Trusted\" -age:1w) OR (project:gwt status:open
-label:Verified=1 -label:Verified=-1 label:Code-Review=2 -age:1w)", i.e.
any open change that has no Verified label and no negative Code-Review
label, and is no older than one week.

On Thu, Oct 9, 2014 at 9:42 AM, Julien Dramaix 
 wrote:

> Does someone know why Jenkins is posting the same message every 1h30 ?
>
> Looks at this patch : https://gwt-review.googlesource.com/#/c/9121/ Jenkins've
> sent several times the same message.
>
> Julien
>
> --
> You received this message because you are subscribed to the Google Groups
> "gwt-maintainers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gwt-maintainers+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thomas Broyer
/tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>


On Sat, Feb 14, 2015 at 1:25 PM, Jens  wrote:

> How can I stop Leeroy from spamming a Gerrit CL?
> https://gwt-review.googlesource.com/#/c/10243/
>
> Seems like the build server is continuously trying to execute
> gwt.presubmit for that CL.
>
> -- 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/733d15d0-9a14-40c9-9760-7d6cdee8bed1%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/733d15d0-9a14-40c9-9760-7d6cdee8bed1%40googlegroups.com?utm_medium=email&utm_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%3D5tkir5eFW1svx5iM8LV3A%3D0uDVt0Atk1b1reJBz7ajCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Documentation sources

[Julien Dramaix]

git checkout gwt-new-site

On Wed Feb 11 2015 at 8:47:39 PM Nicolas Weeger  wrote:

> Hello.
>
>
> I've updated my gwt-site repository from googlesource to github, but when
> running the site locally I don't have the same look as the one on the
> gwtproject.org site.
>
>
> I've compiled the GWT code from https://gwt.googlesource.com/
> gwt-site-webapp
> too, and it works as expected.
>
>
> Any clue what I'm doing wrong?
>
>
>
> Thanks in advance
>
>
>
> Nicolas
>
> --
> 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/201502112047.
> 32763.nicolas%40nekoko.fr.
> 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%3D78g%3D-akuewXZrMuQAzzqc9jN6%3DpEi0HssJZP6Ha_FEMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

I don't think you can read the password.

During the contributor workshop, several people have had this problem and
resetting the password using:
  https://gwt.googlesource.com/new-password
solve the issue.

Julien

On Mon Feb 09 2015 at 2:54:44 PM Richard Wallis  wrote:

> Sorry, spoke to soon.  Daniel obtain password under HTTP password also
> redirects to the create a cookie page.
>
> Can I not read the password out of the cookie somehow?
>
> On Mon, Feb 9, 2015 at 3:52 PM, Richard Wallis  wrote:
>
>> Thanks Daniel, maybe the gerrit failed authentication prompt should point
>> there:
>>
>> At the moment it reads:
>>
>> Please generate a new password at:
>>   https://gwt.googlesource.com/new-password
>>
>> Anyway thanks for the help everyone.
>>
>> On Mon, Feb 9, 2015 at 3:49 PM, 'Daniel Kurka' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> 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 
>>> 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=false&loop=false&delayms=3
>>>>>
>>>>> Julien
>>>>>
>>>>> On Mon Feb 09 2015 at 1:59:31 PM Richard Wallis 
>>>>> 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+unsubscribe@
>>>>>> 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=email&utm_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

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

[Julien Dramaix]

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=false&loop=false&delayms=3

Julien

On Mon Feb 09 2015 at 1:59:31 PM Richard Wallis  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
> 
> .
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] A little change on two http.client.Request modifiers

[Julien Dramaix]

Hi Danilo,

The best is to propose the change by submitting a CL in gerrit  and start
the discussion there.

Julien

On Mon Feb 09 2015 at 12:37:01 PM Danilo Reinert 
wrote:

> Currently I'm using the http.client.Request class without the
> RequestBuilder for a project I'm working on, and I need to change
> the access level of two members from package to public: L148
> 
>  (Ctor
> accepting a XMLHttpRequest, a timeout and a callback) and L233
> 
>  (method
> to be called when the XHR ready state changes to 4).
>
> So I don't have to override the class and relying on classpath tricks,
> considering I'm developing a public library, I wonder if there is any
> problem making this change in the original class.
>
> 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/3979ee78-9cee-
> 4ac3-bd36-7d93b72fce07%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/CABb_3%3D65BLSet%2Bv7LDd_HBc1uDugHBJw50XObfNQmLSRYPQWvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: two errors in master

[Julien Dramaix]

Jakob,

It seems that the dependency to the guava-16.0.1-rebased.jar is missing.
You can add it manually, it is located in tools/lib/guava/guava-16.0.1/

On Sat Jan 31 2015 at 9:09:55 AM Jakob Jarosch 
wrote:

> Hi,
> I've the same problems compiling the source of gwt.
>
> With the following steps (used the tips from here) I tried to fix it but
> had no luck:
> - Cloned the repository, checked out the tools
> - Downloaded the updated jdt jar file
> - Moved the jdtCompilerAdapter out of the jar
> - Deleted the two files in the META-INF folder of the jdt jar file
> - Replaced all three occurrences for the both jar files in the build.xml
> - Tried to run ant
>
> After these steps I get a similar error like everyone else:
> https://gist.github.com/foxylion/fb9cd833fe472a5d9370
>
> Would be great when someone contributes a fix. :-)
>
> - Jakob
>
> Am Sonntag, 11. Januar 2015 17:34:56 UTC+1 schrieb confile:
>
>> Actually, there are three positions of jdt-3.10.0.jar in the build file
>> and three positions of jdtCompilerAdapter-3.10.0.jar.
>>
>> If I change all but the last
>>
>> 
>>
>> then I can compile. If I change that to I get an error. I am stuck could
>> you please at least upload your build.xml file.
>>
>> Thank you
>> Michael
>>
>>
>> Am Sonntag, 11. Januar 2015 15:15:28 UTC+1 schrieb Jens:
>>>
>>> Sounds like you have deleted the classes that you should actually keep.
>>>
>>> I said you can optionally delete class files that *DO NOT* match
>>>
>>> "org/eclipse/jdt/core/compiler",
>>> "org/eclipse/jdt/internal/compiler",
>>> "org/eclipse/jdt/internal/core/util"
>>>
>>> -- 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/85d94902-7bf0-4f58-9c4d-76cfb2988216%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/CABb_3%3D6Gev%3DTAD3iF8hNq8YCNndgtNwSRHi8NhXgFN1X0tW9Mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8 SnapShot "Unexpected internal compiler error" in SDM after switching to GSS

[Julien Dramaix]

I don't know if it will solve your problem but the configurationProperty
CssResource.legacy is not needed anymore:

So remove: 

On Sat Jan 31 2015 at 12:14:40 AM confile 
wrote:

> It compiles perfectly with GWT 2.7 and GSS. So the problem must be in the
> GWT 2.8SnapShot.
>
> --
> 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/73305db8-e7cb-4107-bd17-34db51c49602%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/CABb_3%3D7qh-VuS%3DcsOyKo0m-uhEM04KTEutP%2BGYYU6pwyxH-byA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Documentation site on github

[Julien Dramaix]

Dear GWT Community,

In order to increase the number of contributions on the GWT documentation,
we've decided to move the documentation on Github and accept pull requests.

We have also spent time to convert all the documentation in markdown
syntax. In addition to that, each documentation page has now an edit
button. When you click on, you are redirected to the corresponding markdown
page on Github in edit mode. You can easily modify a page and when you save
your change Github will automatically fork the project (if needed) and
creates a pull request for you.

This is for the documentation only, the code for GWT will stay on gerrit,
simply because gerrit is a much powerful tool to do code review of code.

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%3D4TR8grR9AUvn6OVA5nN6q%3DePs%2Br%3Dh2uenWPi4ds55NHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

If you want css auto completion in gss file, you have to modify your ide
preference to add the extension .gss as css file.

If you want autocompletion for gss syntax, you should open an issue to the
Intellij issue tracker (https://youtrack.jetbrains.com/issues/IDEA) in
order that they add support for GSS in the GWT plugin. For eclipse we need
an external contribution to GPE.

On Fri Jan 02 2015 at 16:49:33 confile 
wrote:

> Is there an option to enable code completion in eclipse for gss files like
> it is done for css files?
>
>
> Michael
>
> Am Donnerstag, 23. Oktober 2014 23:40:08 UTC+2 schrieb Julien Dramaix:
>
>> Just to summarize:
>> - GSS will be available in GWT 2.7
>> - GSS will use the CssResource interface and your file needs to end with
>> the .gss extension
>> - GSS will not be enabled by default. To enable it: add
>>  > /> in your module file.
>> - Once enabled, all the CssResource interfaces will be generated by the
>> new GssResourceGenerator
>> - If your app uses still old css file compatible with the GWT-CSS syntax
>> you will need to enable the automatic conversion of these files to GSS. To
>> do that: add > value="true" /> in your module file.
>> - The GSS parser and compiler is more strict than the old one. If you
>> meet some issue in this automatic conversion, you can also enable the
>> lenient mode: > value="lenient" />
>> - When GSS is enabled, we have to use an attribute gss="true" in your
>> uibinder inline style () in order to enable GSS
>>
>> We decide to go with the memory conversion because it is the way to move
>> forward. The goal is to enable GSS (with the automatic conversion not
>> enabled by default) and remove the CssResourceGenerator in the next
>> release. So we want people test this strategy in order to fix possible
>> issue and ensure that the automatic conversion is stable.
>>
>> On Wednesday, October 8, 2014 1:49:37 AM UTC+2, Goktug Gokdogan wrote:
>>>
>>> Can you also summarize why we need in memory conversion as opposed to
>>> simpler alternative?
>>> So it is documented for the next time when we will have similar
>>> discussion :)
>>>
>>> On Tue, Oct 7, 2014 at 4:00 PM, Daniel Kurka  wrote:
>>>
>>>> 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 
>>>>> wrote:
>>>>>
>>&

Re: [gwt-contrib] Re: Official Gradle plugin

[Julien Dramaix]

Adopting gradle as the build tool for GWT will not force GWT developers to
choose Gradle for their projects.

On Wed Dec 10 2014 at 11:12:18 AM ALAA MURAD  wrote:

> Gradle is forcing Java Developers to learn Groovy ... yuk !
>
> Ant + Ivy is the best building tools, until someone build something in
> Java.
>
> On Wed, Dec 10, 2014 at 12:21 PM, Julien Dramaix  > wrote:
>
>> We have a steering committee meeting tonight and this point is on the
>> agenda. So you could expect to get feedback very soon.
>>
>>
>> On Wed Dec 10 2014 at 12:55:41 AM Jens  wrote:
>>
>>> Ping.
>>>
>>> Would be great to get some feedback. Currently, the lack of a decision
>>> regarding a new build tool for GWT and thus the potential contribution of
>>> this plugin if Gradle will be chosen blocks pull requests.
>>>
>>> I am just guessing but I think Steffen might not be sure if CLA
>>> management is required for his project once he accepts pull requests while
>>> the possibility exists to contribute the whole project to GWT.
>>>
>>> -- 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/73e78f65-a985-48a3-b763-ddc3302bd54a%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/73e78f65-a985-48a3-b763-ddc3302bd54a%40googlegroups.com?utm_medium=email&utm_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%3D7%2BH3JEOnwC1EkRyYnANjD0on_rA%2BSBNXvTd%3D%3Df2yq%3DkA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7%2BH3JEOnwC1EkRyYnANjD0on_rA%2BSBNXvTd%3D%3Df2yq%3DkA%40mail.gmail.com?utm_medium=email&utm_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/CAEJTSg%2BGMwe_2Rc4ngRJOQ4%2BrGqJpHAYj4gw%3Do6s%3D5ppE5S6hg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEJTSg%2BGMwe_2Rc4ngRJOQ4%2BrGqJpHAYj4gw%3Do6s%3D5ppE5S6hg%40mail.gmail.com?utm_medium=email&utm_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%3D4S%2Bx79J_f9W%3D3rAAHgiojPwKeVjhZK1ayh5ic050_MFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Official Gradle plugin

[Julien Dramaix]

We have a steering committee meeting tonight and this point is on the
agenda. So you could expect to get feedback very soon.

On Wed Dec 10 2014 at 12:55:41 AM Jens  wrote:

> Ping.
>
> Would be great to get some feedback. Currently, the lack of a decision
> regarding a new build tool for GWT and thus the potential contribution of
> this plugin if Gradle will be chosen blocks pull requests.
>
> I am just guessing but I think Steffen might not be sure if CLA management
> is required for his project once he accepts pull requests while the
> possibility exists to contribute the whole project to GWT.
>
> -- 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/73e78f65-a985-48a3-b763-ddc3302bd54a%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/CABb_3%3D7%2BH3JEOnwC1EkRyYnANjD0on_rA%2BSBNXvTd%3D%3Df2yq%3DkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Website documentation question

[Julien Dramaix]

I have a big patch (done by Jason Lemay from Arcbees by the way) that I
have to push for review converting every files using markdown syntax.
And indeed we use html syntax for the header:
## Related frameworks

I will push this change in a few weeks but if you want to propose a patch
for anything else don't hesitate to do it. I have to rebase my patch anyway.

Julien



On Fri Dec 05 2014 at 10:32:37 PM Nicolas Weeger  wrote:

> Hello.
>
>
> I've been poking around the documentation (patches ready, waiting for CLA-
> related tasks to be finished :)), and I got a question about the format to
> use.
>
>
> Right now, pages are mostly HTML, split in .md files, with a Markdown
> processor
> converting.
>
>
> So I guess the goal is to migrate to Markdown (the Pegdown variant at
> least),
> at least step by step or for new documentation?
>
>
> One downside, though, is that unless I'm mistaking, Markdown doesn't offer
> any
> option to set IDs on elements, like headers, or names on anchors.
>
>
> So should headers/linkable items be still put in HTML? Or should we use a
> workaround to insert a  in the header?
>
>
>
> Kind regards
>
>
> Nicolas
>
> --
> 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/ms
> gid/google-web-toolkit-contributors/201412052030.16089.nicolas%40nekoko.fr
> .
> 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%3D5BZstbFPO-wyo9c3Y_1AUtREb%2B0%2B8-UufK1R4BS3SnRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

I'm running the test via a Intellij config. The tests run fine with ant so
it's really a problem of classpath. What is weird is that this is an old
configuration and it worked fine before I synchronize my master branch one
week ago.

Anyway I'll tweak a bit the classpath in order to fine what cause that bug.

Thanks for your help,

Julien

On Sat Nov 15 2014 at 10:13:28 AM Manuel Carrasco Moñino 
wrote:

> Julien could you explain how are you trying to run tests, I mean if you
> are using ant and what parameters you are using. I have just checked out
> master and run non gwt tests, and everything went ok:
> $ ant clean buildonly; (cd user && ant test.nongwt)
>
> Can you try the same? what ant and java versions are you using?
>
>
>
> On Fri, Nov 14, 2014 at 10:46 PM, 'Roberto Lublinerman' via GWT
> Contributors  wrote:
>
>> This looks awfully a class path issue. Did you ant clean before building?
>>
>> On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix > > 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.ju

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

[Julien Dramaix]

I've deleted the unit caches and have still the issue. But now that you are
talking about unit cache I've seen this line in the log:
Could not find the GWT compiler jarfile. Serialization errors might occur
when accessing the persistent unit cache.

But I've checked my classpath and the gwt jar files (user and dev) are
there. Am I missing something for the tests ?

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

> Deleted all unit caches?
> On Nov 14, 2014 1:10 PM, "Julien Dramaix" 
> 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 
>>> 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
>>>> su

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

[Julien Dramaix]

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

[gwt-contrib] Not able to run any GWTTestCase

[Julien Dramaix]

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

Re: [gwt-contrib] Build gwtproject?

[Julien Dramaix]

I've updated the site-uploader in order to upload the dtd files. They
should be available now. I have still to modify the application in order to
set the right mime-type for the dtd files.

Julien

On Thu Nov 13 2014 at 12:14:45 AM Brandon Donnelson 
wrote:

> Ok sounds good, will get that out shortly.
>
>
> On Wednesday, November 12, 2014 12:06:17 PM UTC-8, Julien Dramaix wrote:
>
>> yep sure, every improvement is welcome !
>>
>> On Wed Nov 12 2014 at 4:41:32 PM Brandon Donnelson 
>> wrote:
>>
>>> I did an uploader rewrite a while back to upload all the files and this
>>> also serves them through the servlet if you're interested in that code I
>>> can share?
>>>
>>>
>>> On Wednesday, November 12, 2014 6:47:12 AM UTC-8, Julien Dramaix wrote:
>>>
>>>> Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I
>>>> will try to spent some time on that tonight.
>>>>
>>>> On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wednesday, November 12, 2014 11:38:44 AM UTC+1, Jens wrote:
>>>>>>
>>>>>> I'm not seeing the http://www.gwtproject.org/
>>>>>>> doctype/2.7.0/gwt-module.dtd  resources. Either they have been
>>>>>>> updated, or I configured the assembly wrong and there not getting 
>>>>>>> copied in
>>>>>>> the build to generated site.
>>>>>>>
>>>>>>
>>>>>> Ping. Still doesn't seem to be uploaded yet?
>>>>>>
>>>>>
>>>>> The patch has been merged more than a month a ago (https://gwt-review.
>>>>> googlesource.com/9478) so I think it's rather a bug in the
>>>>> packaging/deployment/file-serving that maybe filters out *.dtd files.
>>>>>
>>>>> --
>>>>> 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/6f22cf6a-d0f4-4251-81d2-
>>>>> 0b98bd21e69e%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/6f22cf6a-d0f4-4251-81d2-0b98bd21e69e%40googlegroups.com?utm_medium=email&utm_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/c917c381-15fd-
>>> 465e-9409-53604c00a1fb%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/c917c381-15fd-465e-9409-53604c00a1fb%40googlegroups.com?utm_medium=email&utm_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/507f8c0e-0f65-4a05-a786-1fe2c9ad36b5%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/507f8c0e-0f65-4a05-a786-1fe2c9ad36b5%40googlegroups.com?utm_medium=email&utm_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%3D68JPdwYAPYLnjMQENRD%3D3OkDQWXk4QTouxSEsSDhX8Mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Build gwtproject?

[Julien Dramaix]

yep sure, every improvement is welcome !

On Wed Nov 12 2014 at 4:41:32 PM Brandon Donnelson 
wrote:

> I did an uploader rewrite a while back to upload all the files and this
> also serves them through the servlet if you're interested in that code I
> can share?
>
>
> On Wednesday, November 12, 2014 6:47:12 AM UTC-8, Julien Dramaix wrote:
>
>> Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I
>> will try to spent some time on that tonight.
>>
>> On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer  wrote:
>>
>>>
>>>
>>> On Wednesday, November 12, 2014 11:38:44 AM UTC+1, Jens wrote:
>>>>
>>>> I'm not seeing the http://www.gwtproject.org/
>>>>> doctype/2.7.0/gwt-module.dtd  resources. Either they have been
>>>>> updated, or I configured the assembly wrong and there not getting copied 
>>>>> in
>>>>> the build to generated site.
>>>>>
>>>>
>>>> Ping. Still doesn't seem to be uploaded yet?
>>>>
>>>
>>> The patch has been merged more than a month a ago (https://gwt-review.
>>> googlesource.com/9478) so I think it's rather a bug in the
>>> packaging/deployment/file-serving that maybe filters out *.dtd files.
>>>
>>> --
>>> 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/6f22cf6a-d0f4-
>>> 4251-81d2-0b98bd21e69e%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/6f22cf6a-d0f4-4251-81d2-0b98bd21e69e%40googlegroups.com?utm_medium=email&utm_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/c917c381-15fd-465e-9409-53604c00a1fb%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/c917c381-15fd-465e-9409-53604c00a1fb%40googlegroups.com?utm_medium=email&utm_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%3D71e%2BaP9QmTyS3JBnN0U5CZysRT3VJeo_wAZOTHUVLZPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Build gwtproject?

[Julien Dramaix]

Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I
will try to spent some time on that tonight.

On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer  wrote:

>
>
> On Wednesday, November 12, 2014 11:38:44 AM UTC+1, Jens wrote:
>>
>> I'm not seeing the http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd
>>> resources. Either they have been updated, or I configured the assembly
>>> wrong and there not getting copied in the build to generated site.
>>>
>>
>> Ping. Still doesn't seem to be uploaded yet?
>>
>
> The patch has been merged more than a month a ago (
> https://gwt-review.googlesource.com/9478) so I think it's rather a bug in
> the packaging/deployment/file-serving that maybe filters out *.dtd files.
>
> --
> 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/6f22cf6a-d0f4-4251-81d2-0b98bd21e69e%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/CABb_3%3D5dz%2BnogJCu6YRiMfdZDQxVW2vHtoLw3z_rpPwe1PDhog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] 2.7RC1 compiles fine but recompile returns errors

[Julien Dramaix]

Koen,

Could you give us more information about the error (2) ? Does your 
BaseAdminCssResource use a .css or a .gss file ? Did you enable GSS ? Did 
you enable the auto conversion ? Could you paste the css line related with 
the warning message (line 75) ?

Thanks,

Julien

On Friday, November 7, 2014 8:49:27 PM UTC+1, Koen Maes wrote:
>
> thx for the pointers Jens and Roberto... I'll try your suggestions.
>

-- 
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/605956e2-ee35-47f8-9c96-850396e79478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Cell widgets and GSS

[Julien Dramaix]

ok. I will do that in an external third party library

On Thu Oct 30 2014 at 6:19:58 PM 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> 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 
> 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=email&utm_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=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
>> Yo

Re: [gwt-contrib] Cell widgets and GSS

[Julien Dramaix]

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 
> 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=email&utm_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=email&utm_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.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Cell widgets and GSS

[Julien Dramaix]

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

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

[Julien Dramaix]

For the time being, you have to use the converter externally, 
see https://github.com/jDramaix/gss.gwt/wiki/Migration-guide#the-converter 
(Now the support of GSS is included in GWT, you don't need any other 
dependencies than gwt-user.jar)

I've proposed to store the result of the conversion on disk id the -extra 
flag is set, but I don't have any reaction about that:
> 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.

On Friday, October 24, 2014 4:34:32 PM UTC+2, Paul Stockley wrote:
>
> Is there a way to do an explicit one-time conversion to the new gss 
> format? I would want to do this on my major css files so I can take 
> advantage of the new features.
>
> On Friday, October 24, 2014 4:37:18 AM UTC-4, Thomas Broyer wrote:
>>
>>
>>
>> On Thursday, October 23, 2014 11:40:08 PM UTC+2, Julien Dramaix wrote:
>>>
>>> Just to summarize:
>>> - GSS will be available in GWT 2.7
>>> - GSS will use the CssResource interface and your file needs to end with 
>>> the .gss extension
>>> - GSS will not be enabled by default. To enable it: add  
>>> >> name="CssResource.enableGss" value="true" /> in your module file.
>>> - Once enabled, all the CssResource interfaces will be generated by the 
>>> new GssResourceGenerator 
>>> - If your app uses still old css file compatible with the GWT-CSS syntax 
>>> you will need to enable the automatic conversion of these files to GSS. To 
>>> do that: add >> value="true" /> in your module file.
>>> - The GSS parser and compiler is more strict than the old one. If you 
>>> meet some issue in this automatic conversion, you can also enable the 
>>> lenient mode: >> name="CssResource.conversionMode" value="lenient" />
>>> - When GSS is enabled, we have to use an attribute gss="true" in your 
>>> uibinder inline style () in order to enable GSS
>>>
>>
>> Great summary! That should go into the release notes.
>>
>

-- 
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/b8776c8c-309a-440b-aba6-adc6d3ecdb84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

Just to summarize:
- GSS will be available in GWT 2.7
- GSS will use the CssResource interface and your file needs to end with 
the .gss extension
- GSS will not be enabled by default. To enable it: add  
 in your module file.
- Once enabled, all the CssResource interfaces will be generated by the new 
GssResourceGenerator 
- If your app uses still old css file compatible with the GWT-CSS syntax 
you will need to enable the automatic conversion of these files to GSS. To 
do that: add  in your module file.
- The GSS parser and compiler is more strict than the old one. If you meet 
some issue in this automatic conversion, you can also enable the lenient 
mode: 
- When GSS is enabled, we have to use an attribute gss="true" in your 
uibinder inline style () in order to enable GSS

We decide to go with the memory conversion because it is the way to move 
forward. The goal is to enable GSS (with the automatic conversion not 
enabled by default) and remove the CssResourceGenerator in the next 
release. So we want people test this strategy in order to fix possible 
issue and ensure that the automatic conversion is stable.

On Wednesday, October 8, 2014 1:49:37 AM UTC+2, Goktug Gokdogan wrote:
>
> Can you also summarize why we need in memory conversion as opposed to 
> simpler alternative?
> So it is documented for the next time when we will have similar discussion 
> :)
>
> On Tue, Oct 7, 2014 at 4:00 PM, Daniel Kurka  > wrote:
>
>> 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  
>>> 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 
>>>&

Re: [gwt-contrib] Change packaging for GSS

[Julien Dramaix]

https://gwt-review.googlesource.com/9810

On Sun, Oct 19, 2014 at 12:47 AM, Julien Dramaix 
wrote:

> I will work on that tomorrow
> On Oct 18, 2014 8:10 PM, "'Daniel Kurka' via GWT Contributors" <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> 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
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipLY9ydhxTG0__D0vVojSpuCGQAmLb1aD-rPOBz1Me62A%40mail.gmail.com?utm_medium=email&utm_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%3D4v%3Dt8WUAamukrbz%3DGU9YhXyfE7d0UK8RBg-txR2aykCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Change packaging for GSS

[Julien Dramaix]

I will work on that tomorrow
On Oct 18, 2014 8:10 PM, "'Daniel Kurka' via GWT Contributors" <
google-web-toolkit-contributors@googlegroups.com> wrote:

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

-- 
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%3D6WzhN2n4fKHeXt7%2BvY2WEUHbTiqDQgV3db3dGyPdC0vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Build gwtproject?

[Julien Dramaix]

Hi Brandon

I will do that this week end !

Just ping me monday if it doesn't work.

Julien

On Fri, Oct 17, 2014 at 4:34 AM, Brandon Donnelson 
wrote:

> Could gwtproject site be built?
>
> I'm looking for access to these:
> http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd
>
> Thanks,
> Brandon
>
> --
> 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/8f5c5e44-1543-4f64-84f8-0704507bb028%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/CABb_3%3D6gRewmZmOt14oNYSrcMjWYR%2BeWnnb3FgEzFrSGm2xwug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

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> 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  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 
> wrote:
>
>> > Hmm but still a bit of work if a library has lots of inline styles and
>> wants to use GSS stuff.
>> If you want to use GSS in all of your inline styles, you have first to
>> convert them to GSS and it will take more time than simply adding an
>> attribute that say that this inline style is using GSS.
>>
>> The problem with UiBinder is that we don't know if the developer is using
>> CSS or GSS because  the CssResource interface is generated and we cannot
>> based our logic on the file extension as we do with normal CssResource.
>>
>> I have still to investigate but I'm pretty sure that adding an attribute
>> will be the easiest way to support correctly GSS in uibinder inline style.
>>
>>
>>
>>
>>  --
>> 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%3D4gaeww%3DY4cTkvNXXKKNmig6_s1CaOpwNAAemHXemb%2BjQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4gaeww%3DY4cTkvNXXKKNmig6_s1CaOpwNAAemHXemb%2BjQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> &

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

[Julien Dramaix]

> Hmm but still a bit of work if a library has lots of inline styles and
wants to use GSS stuff.
If you want to use GSS in all of your inline styles, you have first to
convert them to GSS and it will take more time than simply adding an
attribute that say that this inline style is using GSS.

The problem with UiBinder is that we don't know if the developer is using
CSS or GSS because  the CssResource interface is generated and we cannot
based our logic on the file extension as we do with normal CssResource.

I have still to investigate but I'm pretty sure that adding an attribute
will be the easiest way to support correctly GSS in uibinder inline style.

-- 
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%3D4gaeww%3DY4cTkvNXXKKNmig6_s1CaOpwNAAemHXemb%2BjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

In fact, my question is stupid... If third party library want to use GSS,
they just have to use file with .gss extension.

For inline UiBinder styles, we can add an attribute useGss="true".



On Mon, Oct 6, 2014 at 8:41 PM, Jens  wrote:

> Oh I forgot to mention that we had decided to use only the CssResource
>> interface and not create a new GssResource interface.
>>
>> And we use the extension of the file in order to know if the file has to
>> be converted or not
>>
> Oh I see.
>
> I think a config property is better since a library might have widgets
> with inline UiBinder styles and you don't want to force them to declare a
> CssResource in their widget class just to be able to place an annotation on
> it.
>
> -- 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/84c99c30-abca-46e4-855b-c2152968ef73%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/CABb_3%3D6Hy4dNtbAoYho7LWxoPduXuLYUot5A1ZwHEh0O3PiWyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

Oh I forgot to mention that we had decided to use only the CssResource
interface and not create a new GssResource interface.

And we use the extension of the file in order to know if the file has to be
converted or not.
On Oct 6, 2014 8:24 PM, "Jens"  wrote:

> Now I think we should allow the inverse: give the ability to third party
>> libraries to use GSS in their CssResource even if the CssResource.enableGss
>> is set to false. This could be done by either using an annotation or by
>> using a configuration property in the module file.
>>
>
> You said that CssResource.enableGss means that CssResources are now
> generated using GssGenerator. If a library wants to use GSS shouldn't it
> use GssResource directly instead of CssResource? In that case GssResources
> could always be generated using GssGenerator regardless of
> CssResource.enableGss settings.
>
> I don't think libraries should take their existing CssResources and add
> CSS3 stuff to it. I would force them to use GssResource then. Wasn't the
> plan to remove CssResource (and the in-memory conversation) in GWT 3.0
> anyways?
>
> -- 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/d4cf2cb9-ddea-4ef9-a8d1-73eea1ee402e%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/CABb_3%3D4h6kyKP06_38PMVTvfhZQXTatkbYSiYnDm7eNKStFcow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Julien Dramaix]

Hi,

I've pushed the code for the so called GssResource.

The code has been split in two patches:
- The first one contains the code for the converter. The converter can be
used in order to convert the existing css files to a GSS compatible file.
- The second one contains the code for the generator that parses and
compiles the GSS file and produces the implementation of the related
CssResources.

It would be nice to get this code in GWT 2.7, so could you review the two
patches ?

The GSS support won't be enabled by default. In order to enable it, you
will have to set the configuration property named "CssResource.enableGss"
to true. When enabled, all of the CssResource will be generated by using
the GssGenerator.
If your application is using a third-party library that defines some
CssResource that aren't converted to GSS, you can also enable the in-memory
conversion (of css files with .css extension) to GSS by setting the
configuration property "CssResource.legacy" to true. This conversion can
run in strict (throw error if the original file contains some errors) or
lenient mode (does its best to fix the original file) .

Now I think we should allow the inverse: give the ability to third party
libraries to use GSS in their CssResource even if the CssResource.enableGss
is set to false. This could be done by either using an annotation or by
using a configuration property in the module file.

What do you think it would be the best ? I'm more in favor of the
annotation.

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%3D4HmWFv0V2BVi5qf3B8Jdjkt-eUXZD4hBLvuM5X_U5qxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.