date:20160702

Hi all,

Current snapshots fail with JDK 7:
[INFO] [INFO]Tracing compile failure path for type 
'java.util.Comparator'
[INFO] [INFO]   [ERROR] Errors in 
'jar:file:/home/travis/build/tbroyer/gwt-maven-plugin/target/it-repo/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/gwt-user-2.8.0-SNAPSHOT.jar!/com/google/gwt/emul/java/util/Comparator.java'
[INFO] [INFO]  [ERROR] Line 1: The type 
java.lang.invoke.SerializedLambda cannot be resolved. It is indirectly 
referenced from required .class files

(see https://travis-ci.org/tbroyer/gwt-maven-plugin/jobs/141919077#L410)

Is this because the snaphots are built with JDK 8 
(see http://www.draconianoverlord.com/2014/04/01/jdk-compatibility.html for 
instance) or that we actually no longer support JDK 7 (without noticing it) 
?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/bb56d241-c198-4bb6-9612-c5bd3ccfd6cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Bean Validation

On Saturday, July 2, 2016 at 11:40:56 PM UTC+2, ManfredTremmel wrote:
>
> I've read in the 2.8rc1 release notes 
>  that JSR 303 Bean 
> Validation in GWT is unmaintaned and marked as deprecated. For me, the 
> client and server side validation is a killer feature and 
> I've already solve the problems I had and also improved the client side 
> bean validation in my gwt-bean-validators 
>  project on 
> github. In three weeks I can invest some time in working into the gwt 
> implementation of bean validation and try to port it to 1.1 api. If you are 
> interested I would also include the improvements of my project into GWT.
> Let me know if you are interested in my help or have any question.
>

We decided (a long time ago) that we wanted to modularize GWT, and move to 
side-projects what could be decoupled. The goal is to spread maintenance to 
more people (hopefully) by reducing the scope of each project, and allowing 
those side-projects to have different release cycles than GWT. This means 
that GWT does not need to wait for some bugs to be fixed or features to be 
added to some parts of the code before a release can be cut, concentrating 
on the compiler and core (emulation, etc.), and projects can release 
without waiting for a GWT release either.

So, if you can contribute some time, it'd be great to be able to move Bean 
Validation to its own project and out of GWT proper (there'd still be some 
javax.validation emulation in GWT proper, at least some interfaces; but 
there may be some work needed to make other GWT features independent of the 
Bean Validation version being used; I think there's some code in Editors or 
Request Factory that implements a javax.validation interface). Then the 
project can live its own life and update to a newer Hibernate Validator, 
etc.
FWIW, JBoss has interest in Bean Validation too, so you may want to get in 
touch with Christian Sadilek.
See https://github.com/gwtproject/gwt/issues/9367 for more on the matter.
FWIW, Putnami PWT also has some form of JSR 303 support, so I suppose 
they'd be interested in, at least, following the changes made to GWT on the 
subject.

In any case, all help is welcome. So, welcome, and thank you in advance for 
your 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/3e8bdbe1-04dd-4c34-a73c-9658b36e6ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2016-07-02 Thread Ignacio Baca Moreno-Torres

+1 to add some type-safe, in my current mini-project (almost 50 lines of
code) there are 5 cast! 2 elements, 2 events and 1 event target... the
event target is mandatory, but the events and elements will be nice to be
type-safe.

On Sat, Jul 2, 2016 at 11: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 (<
> 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/CAM28XAsU1UZgkh3cjG1HPkpRBJfaiEh631fq9WdS_RQg8Z_Leg%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

[gwt-contrib] Bean Validation

2016-07-02 Thread ManfredTremmel

I've read in the 2.8rc1 release notes 
 that JSR 303 Bean 
Validation in GWT is unmaintaned and marked as deprecated. For me, the 
client and server side validation is a killer feature and 
I've already solve the problems I had and also improved the client side 
bean validation in my gwt-bean-validators 
 project on github. 
In three weeks I can invest some time in working into the gwt 
implementation of bean validation and try to port it to 1.1 api. If you are 
interested I would also include the improvements of my project into GWT.
Let me know if you are interested in my help or have any question.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/886a4ff5-80a0-4cc1-ae7c-6def9d781fdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2016-07-02 Thread Manuel Carrasco Moñino

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

[gwt-contrib] Re: Compile specific files only

2016-07-02 Thread Ethan Hon



Without any background, the question is how can I add a compiler option so 
>> that the source inside a module is compiled without resolving its 
>> dependency? For example, a module as simple as below
>>
>> 
>>   
>>   
>> 
>>
>> Only the .java files inside utils folder are translated into javascript.
>>
>
>
> Not sure if I understand you. If the code inside the utils folder 
> references a GWT button then the code of the GWT button must be available 
> somehow, otherwise your utils code simply won't work. Given that GWT 
> requires whole world knowledge during compilation the GWT button code is 
> pulled in from the inherited User module (or more specific the indirectly 
> inherited UI module). If you are saying you want to link against some 
> pre-existing GWT button code, then thats not possible and I would assume 
> you would need to write a new compiler instead of just adding a compiler 
> option.
>
> The code for GWT button (using your example) is already available on the 
web (AppInventor site) so that when the code inside utils is plugged in, 
the button should work. This is what I hope to achieve. 

Ok so the compilation requires whole world knowledge. But can we somehow 
(e.g. as simply as adding a compilation option) restrict the output to just 
the javascript of utils? Then the permutations only store the code for 
utils only. I know time may be wasted but let's see if it's even possible.

 

> From what I understand you want some plugin system for AppInventor to 
> circumvent the mentioned "whole world knowledge" requirement of GWT. The 
> usual way to solve this is to have AppInventor publish a JavaScript API 
> using GWT JSNI or JsInterop and then let 3rd party developers write their 
> component mocks against this stable JavaScript API. In general this would 
> also allows 3rd party developers to use something different than GWT to 
> build their component mocks. If done correctly the AppInventor app can then 
> import these 3rd party component mocks at runtime by adding an additional 
>

Re: What is happening to GWT???


>
> But it also takes some time to write release notes for every release.
> So again, mostly a problem of time to spend.
>

I think if we take care on good commit messages and bug tracking we could 
automate releases including good enough release notes on Github using their 
API.

-- J.

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

Re: What is happening to GWT???



On Saturday, July 2, 2016 at 4:22:28 PM UTC+2, Jens wrote:
>
>
> As said above, Google doesn't really care about "releases", except for 
>> that they care enough about the community "outside" who, they know, do care 
>> about releases.
>>
>
> @Thomas: And thats exactly why I think GWT will have a better life if we 
> would do fixed, automated monthly / quarterly releases directly from master 
> after they have run through Google testing to ensure a high degree of 
> stableness. People don't like using SNAPSHOTs so just lets just "rename" 
> some SNAPSHOTs as releases on a regular basis.
>

+1, though it needs more testing than "Google testing", because Google 
doesn't use 100% of GWT, and don't use it the way we use it externally 
(whether the "SDK" or Maven artifacts).
Because it takes some time to test, it cannot be too frequent; unless maybe 
we only "stage" artifacts and ask the community to test them and vote for 
whether to release them (like Apache does)
But it also takes some time to write release notes for every release.
So again, mostly a problem of time to spend.

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

Re: What is happening to GWT???

On Saturday, July 2, 2016 at 5:36:58 PM UTC+2, Gilberto wrote:
>
> Guys, threads asking if GWT is dead/dying shouldn't appear as often as it 
> does. Actually they shouldn't appear at all. But they do. Something is 
> definitely wrong. As community we should do something.
>

Glad you're using "we" here! ;-)

> In my opinion the communication is pretty poor and should be improved. GWT 
> is "too blackbox" in my opinion, because of the reasons I stated before.
>
> But if the communication is fine, it's just a matter of the interest of 
> the developer in viewing commit logs, so what's the problem then? Don't 
> tell me everything is fine - a forum with threads asking if the framework 
> is dead isn't a sign that everything is fine.
>

I'm not saying everything's fine; I'm asking for the community to:
 * have "responsible behavior" when those threads happen, and rather answer 
with "yeah, we know communication is rather bad, but GWT is not dead" than 
with "GWT is not really open source, Google is leading and doing what they 
want to do without care for the community" etc. many more "arguments" 
implying you'd rather think about switching to something else. If you don't 
have information, ask, reply with "I too wonder, anyone knows better?", 
don't spread FUD.
 * help fixing those communication issues by investing the time it takes to 
be the "link" between the developers who don't have enough time to 
communicate broadly and the rest of the community who ask for more 
information/communication.

I've just spent a day working on finally unbundling third-party 
dependencies from gwt-dev and gwt-user (testing this is such a time sink) 
and a few hours reading and answering here, on stack overflow and on the 
issue tracker. And I do that primarily on my free time; I'm not paid for 
working on GWT (though my employer is OK with me spending a little work 
time on it, which I just did yesterday).

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

Re: What is happening to GWT???

2016-07-02 Thread Vassilis Virvilis

Hi,

+1 on the regular releases. I am perfectly aware that this is an open
source project so nobody is entitled in asking anything. However with long
standing releases it is getting difficult to justify use of GWT in my
organization. It is much easier to carry custom patches or skip a buggy
release in a fast pacing schedule.

@Jens thanks for the links. I always assumed you were an insider in GWT
development.

I am sure there must be a better way of documenting the GWT development
than Jen's mail though... :-)


On Sat, Jul 2, 2016 at 5:22 PM, Jens  wrote:

>
> As said above, Google doesn't really care about "releases", except for
>> that they care enough about the community "outside" who, they know, do care
>> about releases.
>>
>
> @Thomas: And thats exactly why I think GWT will have a better life if we
> would do fixed, automated monthly / quarterly releases directly from master
> after they have run through Google testing to ensure a high degree of
> stableness. People don't like using SNAPSHOTs so just lets just "rename"
> some SNAPSHOTs as releases on a regular basis.
>
> @Others: I am not on the steering group and I am not an official
> maintainer for any of GWT's features. But still I think I am pretty good
> informed about whats going on with GWT. How, do you ask? Exactly as Thomas
> said.
>
> I am reading posts in
>
> https://groups.google.com/forum/#!forum/google-web-toolkit-contributors
> https://groups.google.com/forum/#!forum/gwt-steering
>
> I regularly look at upcoming commits to see whats in the pipeline
>
> https://gwt-review.googlesource.com/#/dashboard/self
>
> You can even get notified via email of changes to upcoming commits by
> either registering on https://gwt-review.googlesource.com and configure
> email notification or by joining
> https://groups.google.com/a/gwtproject.org/forum/#!forum/gwt-reviews
>
>
> GWT does not do public relations work, if you want to stay informed you
> need to gather information using the above sources.
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vassilis Virvilis

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

Re: What is happening to GWT???

 

> As community we should do something. In my opinion the communication is 
> pretty poor and should be improved. GWT is "too blackbox" in my opinion, 
> because of the reasons I stated before.
>

Its as open as any other open source project.

 

But if the communication is fine, it's just a matter of the interest of the 
> developer in viewing commit logs, so what's the problem then? Don't tell me 
> everything is fine - a forum with threads asking if the framework is dead 
> isn't a sign that everything is fine.
>

These threads appear because GWT has communicated release dates in the past 
and did not meet them for a long time. So these people then think nobody is 
working on GWT anymore and they don't take a look at the sources I have 
linked above to rethink their statement. Personally I believe these threads 
will instantly disappear if GWT would do automated, regular releases from 
master branch for the people relying on releases. The rest probably uses 
master branch of GWT anyway because its very stable (as Thomas said, Google 
continuously builds software from master branches).


 

> What makes a framework live, the commits on a repository or the community 
> behind it?
>

Actually the commits, because I would never use a framework nobody is 
working on to improve it.


-- J.

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

Re: Any elegant approach to integrate Spring security with GWT RPC based application?

2016-07-02 Thread Juan Pablo Gardella

See
https://groups.google.com/forum/m/?fromgroups#!topic/google-web-toolkit/fkbowz5-5do
it's old but maybe ir is still useful for your needs

El sáb., jul. 2, 2016 7:52, Gilberto  escribió:

> Not the answer you would like to hear, but...
>
> In my humble opinion, the elegant solution would be not using GWT RPC at
> all. Go RESTful.
>
> For the annotation problem, I don't know if there's a way to escape...
> maybe you could try code generation (which usually also relies on
> annotations... so...).
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: What is happening to GWT???

Guys, threads asking if GWT is dead/dying shouldn't appear as often as it 
does. Actually they shouldn't appear at all. But they do. Something is 
definitely wrong. As community we should do something. In my opinion the 
communication is pretty poor and should be improved. GWT is "too blackbox" 
in my opinion, because of the reasons I stated before.

But if the communication is fine, it's just a matter of the interest of the 
developer in viewing commit logs, so what's the problem then? Don't tell me 
everything is fine - a forum with threads asking if the framework is dead 
isn't a sign that everything is fine.

It hurts to ask other developers about GWT and hear "GWT? Never heard of 
it". Is it just their fault? What makes a framework live, the commits on a 
repository or the community behind it?


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

Re: What is happening to GWT???



> As said above, Google doesn't really care about "releases", except for 
> that they care enough about the community "outside" who, they know, do care 
> about releases.
>

@Thomas: And thats exactly why I think GWT will have a better life if we 
would do fixed, automated monthly / quarterly releases directly from master 
after they have run through Google testing to ensure a high degree of 
stableness. People don't like using SNAPSHOTs so just lets just "rename" 
some SNAPSHOTs as releases on a regular basis.

@Others: I am not on the steering group and I am not an official maintainer 
for any of GWT's features. But still I think I am pretty good informed 
about whats going on with GWT. How, do you ask? Exactly as Thomas said. 

I am reading posts in

https://groups.google.com/forum/#!forum/google-web-toolkit-contributors
https://groups.google.com/forum/#!forum/gwt-steering

I regularly look at upcoming commits to see whats in the pipeline

https://gwt-review.googlesource.com/#/dashboard/self

You can even get notified via email of changes to upcoming commits by 
either registering on https://gwt-review.googlesource.com and configure 
email notification or by 
joining https://groups.google.com/a/gwtproject.org/forum/#!forum/gwt-reviews


GWT does not do public relations work, if you want to stay informed you 
need to gather information using the above sources.

-- J.

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

Re: What is happening to GWT???

On Saturday, July 2, 2016 at 12:29:32 PM UTC+2, Gilberto wrote:
>
> ... and that's a problem, at least the way it is developed now.
>
> GWT is a more-or-less open-source project. While it is indeed open-source 
> (you can look at the code), the process of developing it depends heavily on 
> closed-source, blackbox projects made by Google, that nobody really knows 
> about or aren't allowed to say about.
>
> For example: it was said that "Google uses GWT 2.8 beta internally, so it 
> is pretty stable". Which projects? Who are the folks involved in those 
> projects? How deep in the usage of GWT on those projects? Nobody knows, and 
> yet the development cycle of GWT is tied to it.
>

That's not true.
Google mirrors GWT code internally so "their GWT" is pretty close to "our 
GWT" (AFAIK there's one single commit that differs, the one that upgrades 
Jetty and HTMLUnit)
Google uses a "monorepo", where everything is in a single source 
repository, including GWT. This means there's no "release", every 
dependency is a "snapshot"; so Google does not use "2.8 beta", it uses 
"master" (at the point they synchronized with the open-source repo, modulo 
internal changes, like the commit I mentioned above that they didn't sync 
internally –if you want the details, that's because they can't depend on 
Servlet API 3.1, so they have to keep the older Jetty–, and they also 
already deleted legacy devmode).

What we do not know for sure is what parts of GWT they're using and which 
ones they're not. We know they're using widgets and GWT-RPC, because Google 
Groups, the very webapp I'm typing this message in, is built with GWT and 
uses widgets and GWT-RPC (other GWT-based webapps, such as Google Flights, 
also use widgets BTW). And we know they don't use Request Factory, the 
Editor Framework, or JSR 303 Bean Validation. We also know they don't use 
com.google.gwt.dev.DevMode to run their apps, their only dependency on 
Jetty (for example) is the "internal" use in JUnitShell and CodeServer, but 
they're not using it to run webapps: they don't rely on web.xml, webapp 
classloader specific behavior, JSPs, etc. Rather, they (apparently) use 
CodeServer and run their webapps separately.

> So GWT is not only internal to Google since the creation of the steering 
> group, but still it depends heavily on Google - and it is not advertised as 
> it used to be (like on Google I/O and other presentations).
>
> And by being tied to blackbox projects from Google, and since the policy 
> of Google for release dates is "release when it's done", we, members of the 
> GWT community outside Google, stay with little-to-no information about how 
> and when the things will be done.
>

As said above, Google doesn't really care about "releases", except for that 
they care enough about the community "outside" who, they know, do care 
about releases.
It's not much "the policy of Google" than "the policy of the GWT Steering 
Committee", and because Google are the ones doing the heavy development 
work (though non-Googlers deserve recognition for their hard work, mostly 
recently for emulating new Java 8 APIs), it happens that we're all waiting 
for them; but anyone can step in and get involved to help speed the process 
(if only by testing snapshots, and not only new features but also ensuring 
there's no regression).

I've said it many times, but apparently it bears repeating: complaining 
doesn't help, it only spreads FUD. Development is made publicly, so if you 
want to know what's happening, start by having a look at the issue tracker 
and commit history, then possibly code reviews to see what's coming, and 
test snapshots (if only for non-regression). And anyone is free to 
transform this form of communication into another one (posts to the forums, 
blog articles, etc.) But it takes time, and most of the contributors prefer 
spending their time differently (contributing code, triaging issues, 
answering on the forums and stack overflow, trying the new features and 
give feedback, working on build-tools integrations/plugins, etc.)

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

[gwt-contrib] Re: Compile specific files only



> Without any background, the question is how can I add a compiler option so 
> that the source inside a module is compiled without resolving its 
> dependency? For example, a module as simple as below
>
> 
>   
>   
> 
>
> Only the .java files inside utils folder are translated into javascript.
>


Not sure if I understand you. If the code inside the utils folder 
references a GWT button then the code of the GWT button must be available 
somehow, otherwise your utils code simply won't work. Given that GWT 
requires whole world knowledge during compilation the GWT button code is 
pulled in from the inherited User module (or more specific the indirectly 
inherited UI module). If you are saying you want to link against some 
pre-existing GWT button code, then thats not possible and I would assume 
you would need to write a new compiler instead of just adding a compiler 
option.

>From what I understand you want some plugin system for AppInventor to 
circumvent the mentioned "whole world knowledge" requirement of GWT. The 
usual way to solve this is to have AppInventor publish a JavaScript API 
using GWT JSNI or JsInterop and then let 3rd party developers write their 
component mocks against this stable JavaScript API. In general this would 
also allows 3rd party developers to use something different than GWT to 
build their component mocks. If done correctly the AppInventor app can then 
import these 3rd party component mocks at runtime by adding an additional

[gwt-contrib] Compile specific files only

2016-07-02 Thread Ethan Hon

Hi guys,

Without any background, the question is how can I add a compiler option so
that the source inside a module is compiled without resolving its
dependency? For example, a module as simple as below

Only the .java files inside utils folder are translated into javascript.

*Background*I am working on supporting mock components for AppInventor
's component development kit (aka CDK, link
).
Basically, I need to inject javascript representing a mock on-the-fly. But
before injecting, I need to get hold of what to inject.

*AppInventor and components*
AppInventor is written with GWT enabling users to edit their apps on the
web before running on android. What they edit on the web is actually mock
components, mocking the genuine visible components (e.g. TextBox, Spinner,
etc) on android. So the mocks are developed with GWT.

*AppInventor and CDK*
Before CDK, all components are developed by the team. CDK allows other
developers to make and use components. This requires loading necessary code
at runtime. Currently, only the code of the component on the android side
can be done so but not the code for the mock. In other word, it now only
supports components without a mock (aka non-visible components).

*Goal*
To support mocks, we need to know the part of the GWT code that is written
by the author which will then be injected on-the-fly. So I need to only
compile those specific files but not all files. That's why I post this
question. And I want to make use of GWT's compiler for this purpose.

The info above may be over-simplified but it may take very long to explain
every detail. Let's see if it's already enough.

Thank you very much. Any direction or advice would be appreciated. I am
running out of solutions. Hope this is the right one.

--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/abdde01f-8c0e-45fd-909d-eaa4ae419fcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any elegant approach to integrate Spring security with GWT RPC based application?

Not the answer you would like to hear, but...

In my humble opinion, the elegant solution would be not using GWT RPC at 
all. Go RESTful.

For the annotation problem, I don't know if there's a way to escape... 
maybe you could try code generation (which usually also relies on 
annotations... so...).

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

Re: gwt material and uibinder

Hi Pierre!

Welcome to GWT and GWT Material =)

If you want a faster, direct communication with the developers from GWT 
Material, join us at the Gitter chat: 
https://gitter.im/GwtMaterialDesign/gwt-material

Also, I advise you to really try to use Maven. I know it's hard and 
sometimes frustrating, but when you finally get it working, can save you a 
lot of time when using continuous integration, and allows your project to 
be IDE independent (which is really important to have - you'll never know 
when a vi expert will join your team).

About your problem with the waves, I imagine it's something related to the 
layout of your entire view. I'd have to test. Do you have a complete 
working example so I can copy-paste-and-test ?

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

Re: What is happening to GWT???