Friday, May 31, 2019

Re: GWT - Still Active ?

On Fri, May 31, 2019 at 10:44 AM Craig Mitchell <mail@craig-mitchell.com> wrote:
Off topic:  I do wonder how web assembly (WASM) is going to impact GWT, especially if it gets garbage collection, and therefore makes Java to WASM compilation possible.

That is the biggest risk IMO. When we did our analysis to decide on whether to commit to J2CL/GWT3.x for the next 10 years or not this was the only real risk that we found (or that Typescript gets a lot better backend).

WebAssembly is still a way off but projects like https://github.com/i-net-software/JWebAssembly do seem to be something to watch


--
Cheers,

Peter Donald

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

Re: Is this project active?



On Fri, May 31, 2019 at 10:55 AM Rob Newton <robn10101@gmail.com> wrote:
A contributor may develop something new or port something, and then announce it to the community that it is available for use, but there is no central site listing/promoting these wares.

A central place would be nice and has been tried before but it takes a lot of effort to establish it and keep it going.
Perhaps things are in too much flux to attract new developers to using GWT.  Perhaps the goal should be to retain existing GWT users?  The more users there are, the more contributors there will be, and the better GWT will be for all of us.  Conversely, the fewer users there are, ... .

I think that is the point porting the GWT2.x modules to jsinterop. To help retain existing users.

There is also a lot of companies that have abandoned all of those framework libraries and just use jsinterop and java to js compiler. Vue-GWT seems successful. We use react+GWT and find it invaluable. I think all of googles stuff probably does this.
 
(It's easy for me (a non-contributor) to list some shortcomings, but am I going to volunteer my personal time to improve things?  Or do I expect Google to do everything, and I just use it and give nothing back?)

I don't think Google is really responsible. I expect that in time that the jre layer + jsinterop library will probably move out of GWT and into their own repositories so they can be more easily used by J2CL (googles replacement java-to-js compiler) at which point I am not sure how much work will go on in the current GWT repo. However I expect work in the elemental2, j2cl and other repos to continue.

--
Cheers,

Peter Donald

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

Re: GWT - Still Active ?

Even though it is still working for us SDM works perfectly in large projects long as your code isnt really too coupled, and regarding RPC you might take a look here 
https://www.slideshare.net/gwtcon/in-defense-of-gwtrpc-by-colin-alworth/

currently i am using domino-rest which works for me.

I am really not sure what dead means these days.

On Friday, May 31, 2019 at 4:23:16 PM UTC+3, Edson Richter wrote:
Yep. Seems dead since we could not debug anymore. Superserver never worked - and previous "classical" debug stopped working. Even Google is migrating projects out of gwt.
Rpc is a nightmare in large apps.
So we are hiring developers to rewrite ui into Angular2+.
Hoping for a better future.
Just my -2c.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1fe3ea39-17c0-45a7-b7c4-ed0233488a73%40googlegroups.com.

Re: GWT - Still Active ?

Out of curiosity, what would prevent someone still build projects based on current GWT 2.8.2 and keep using all the goodies? I think as of 2.8.2 it is future proof especially with a shift to jsinteop included in current release version? People even with current version took their own path and modernized part of GWT like the excellent gwt material & domino ui kit.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/bd8a7dcd-e947-46a6-9072-2a972becc511%40googlegroups.com.

Re: GWT - Still Active ?

Yep. Seems dead since we could not debug anymore. Superserver never worked - and previous "classical" debug stopped working. Even Google is migrating projects out of gwt.
Rpc is a nightmare in large apps.
So we are hiring developers to rewrite ui into Angular2+.
Hoping for a better future.
Just my -2c.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f8509e0c-6002-4c70-acd5-03ec3a065281%40googlegroups.com.

Re: GWT - Still Active ?

I also posted a reply here for anyone reading this thread instead of the other one

https://groups.google.com/d/msg/google-web-toolkit/-6KuZjHFD5c/yxouo-PHAwAJ

On Thursday, May 30, 2019 at 10:33:30 PM UTC+3, Bob Lacatena wrote:
I just posted this elsewhere, but as this thread has more current responses, I'm reposing it in the hopes that someone will read it:


GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Wednesday, May 29, 2019 at 8:54:05 PM UTC-4, Craig Mitchell wrote:

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/685b42f9-045e-44ea-8889-71c6af5e6ea8%40googlegroups.com.

Re: GWT - Still Active ?

This is one of the things that are preventing us from releasing 2.9 
https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/VN4ATVrLrTA

any help here will be appreciated.

On Thursday, May 30, 2019 at 11:32:22 PM UTC+3, Michael Joyner wrote:
Ideally, twice yearly release of "stable", with most recent appropriate patches applied, such as "2.201904" and "2.201910" or similar tagged releases would definitely help there.

On 5/30/19 3:33 PM, Bob Lacatena wrote:
I just posted this elsewhere, but as this thread has more current responses, I'm reposing it in the hopes that someone will read it:


GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Wednesday, May 29, 2019 at 8:54:05 PM UTC-4, Craig Mitchell wrote:
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/aa688813-7e77-454e-af26-4b06ad2b1b06%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5a603a32-6bf4-4f94-b8dc-638453c05dad%40googlegroups.com.

Re: Is this project active?

@Bob
We do really understand how you feel, we were there at some point. BUT


On Thursday, May 30, 2019 at 10:31:38 PM UTC+3, Bob Lacatena wrote:
GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Who are the developers we are talking about here?! GWT is an open source project now managed and maintained by the community, it is not like that we have a team with named members, We are a few who volunteered to do the work in our spare time, and even while we were low in numbers in past year we managed to make a big progress :

  • Most of the GWT2 modules ported to GWT3.0.
  • Built lots of libs that works in both GWT2 and GWT3.
  • Built small apps and samples to test with j2cl.
  • Contributing to elemental2 and Closure for a better elemental2 API.
  • We now have a working j2cl maven plugin.
 

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

We would love to do this, currently all the news, discussions, and announcements are all in the gitter channels mentioned in frank reply or in these groups, Which are not really bad for a work that is not yet 100% complete and being done by very few in our spare time. We welcome and Volunteer(s) who would step up to maintain a page in the gwtproject site for such purpose, but it is not something we can handle with the current man and time power we have.
 

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

In general if expect ZERO breaking changes in GWT3.0 it will mean that we are not actually changing anything, which is not useful, what we are doing for porting from GWT2 is make sure that we introduce the minimum breaking changes most are in the imports, and gwt widgets were made when we had old IE browsers and HTML5 was not yet getting enough browsers support, still even now gwt widgets are being migrated for backward compatibility, yet there is nothing prevent any of us from using HTML5 in our gwt2 apps right now, we have many libs that leverage html5 for gwt2 and of course working in gwt3 too, we have elemental2, elemento, Nalu, and a set of tools from dominokit including domino-ui.

With that said and knowing that GWT2 is being ported and some new libs are being made to work with GWT3, we should not expect every old gwt lib out there to work out of the box with gwt3.0, those libs will also needs to migrate, and this is another area for volunteers to offer help.

 

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

We welcome any suggestions and ideas here, we currently use gitter and these groups, if any one is suggesting a better alternatives we dont mind, any volunteer wants to manage this we also dont mind, actually we are seeking help with and would love to communicate in a way that is more public than what we currently do.
 

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume. 

- Bob

With all that said, i would like to add that there is nothing today that prevent us from writing apps or updating existing ones to work with GWT3, we already build for GWT3 in mind, you can use the ported modules, yo can use elementa2, and you can use any of the new libs being made, this will also help us with testing and fixing bugs early and even taking decisions.


those works on both gwt2 and gwt3/j2cl, and i am alreay using them in one of our big applications at work.


I will be honest here and SHOUT for help, we need more people to help us move faster, we need more people to publish our work, we need more people to help us testing

 

On Thursday, March 28, 2019 at 2:58:47 AM UTC-4, carl.hos...@gmail.com wrote:
Hello all!  I am wondering how active this project is?  Don't see much action on the releases and comments. 

Another question I have is if this project is still active, when will Java 11 support be released?

Thanks  in advance,

Carl

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/3518dbba-f625-4333-93ae-d5942741c9b3%40googlegroups.com.

Thursday, May 30, 2019

Re: Is this project active?

Bob, you are right! At the moment, there is no communication, so GWT might look dead. 

The only way to get informations for now  is to visit the Gitter rooms for gwtproject https://gitter.im/gwtproject/gwt and j2cl https://gitter.im/vertispan/j2cl.  

Many contributors are working on GWT 3 to get it work. 

* create gwt modules that work with j2cl (remove JSNI, replace generators, etc)
* Colin and Dimitrii (I think) are working on maven j2cl plugins
* Ahmad has written a really nice widget lib which will be j2cl ready (https://github.com/DominoKit/domino-ui)

Many others are working on frameworks that will work with j2cl like:

* Elemento 
* autorest
* Nalu 
* mvp4g2
* etc.

and many more (sorry, if I missed something and for sure I will, there are a lot more). All these libs need to be tested with j2cl, needs docs, etc. This is a lot of work, that the contributors are doing in their rare free time.

Once, we got more things working, we will move the migrated modules to maven central and do announce them. 

And of course we need to update gwtproject.org. But, this is only reasonable once we got things working and know, what to write.

For all of you, who are missing more informations, visit the Gitter rooms. 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8d8e9db0-5af9-4567-b86b-ad905d5a6cca%40googlegroups.com.

Re: Is this project active?

Bob, you are right! At the moment, there is no communication, so GWT might look dead. 

The only way to get informations for now  is to visit the Gitter rooms for gwtproject https://gitter.im/gwtproject/gwt and j2cl https://gitter.im/vertispan/j2cl.  

Many contributors are working on GWT 3 to get it work. 

* create gwt modules that work with j2cl (remove JSNI, replace generators, etc)
* Colin and Dimitrii (I think) are working on maven j2cl plugins
* Ahmad has written a really nice widget lib which will be j2cl ready (https://github.com/DominoKit/domino-ui)

Many others are working on frameworks that will work with j2cl like:

* Elemento 
* autorest
* Nalu 
* mvp4g2
* etc.

and many more (sorry, if I missed something and for sure I will, there are a lot more). All these libs need to be tested with j2cl, needs docs, etc. This is a lot of work, that the contributors are doing in their rare free time.

Once, we got more things working, we will move the migrated modules to maven central and do announce them. 

And of course we need to update gwtproject.org. But, this is only reasonable once we got things working and now, what to write.

For all of you, who are missing more informations, visit the Gitter rooms and offer your help. 



--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4f83b79e-d040-460a-9659-e1ac1a46a257%40googlegroups.com.

Re: Is this project active?

I can sympathise with some of what Bob is saying.

From what I can gather there is actually a great flux of activity going on behind the scenes by parts of the community.  The main players in moving GWT forward appear to be half-a-dozen or so companies who use GWT greatly, and some individuals, often doing it on their own personal time.

As Bob says, the gwtproject.org site makes it appear that GWT is in limbo.  If a newcomer or existing user puts some time into searching posts in this group and the contributors one, or the occasional blog post somewhere, they start to see a rough roadmap, and some progress is being made towards it by the community.  But as he says, there needs to be some defacto site explaining the roadmap, and make some recommendations on what parts of traditional GWT 2 to keep using or not, and what new stuff is available (elemental2, jsinterop, etc), and some basics on how to use the new stuff.

It was only by searching the newsgroups that I learnt about the existance of jsinterop-base, and only through more searching that I saw a few examples of using it (and also looking at the API).  This is a pretty important/useful package.

Further research uncovers that much of the gwt-user package is being split out into individual packages, org.gwtproject.* , to not depend on JSNI and generators.  Quite a few are done, according to https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o .  They are scattered all around github it seems, not ready for maven central?

A contributor may develop something new or port something, and then announce it to the community that it is available for use, but there is no central site listing/promoting these wares.

Perhaps things are in too much flux to attract new developers to using GWT.  Perhaps the goal should be to retain existing GWT users?  The more users there are, the more contributors there will be, and the better GWT will be for all of us.  Conversely, the fewer users there are, ... .

(It's easy for me (a non-contributor) to list some shortcomings, but am I going to volunteer my personal time to improve things?  Or do I expect Google to do everything, and I just use it and give nothing back?)


On Friday, May 31, 2019 at 5:31:38 AM UTC+10, Bob Lacatena wrote:
GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Thursday, March 28, 2019 at 2:58:47 AM UTC-4, carl.hos...@gmail.com wrote:
Hello all!  I am wondering how active this project is?  Don't see much action on the releases and comments. 

Another question I have is if this project is still active, when will Java 11 support be released?

Thanks  in advance,

Carl

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/157d7179-afbb-4cd3-881a-1edda8af0427%40googlegroups.com.

Re: GWT - Still Active ?

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

Personally, I love GWTs Java to JS compiler, and its seamless RPC ability.  As you mentioned, its widget library is now dated, and not great to work with.  I usually keep my use of it to a minimum, instead, creating my own components, or using an off the shelf solution.  Eg:  https://gwtmaterialdesign.github.io/gwt-material-demo/


Put some effort into communication! 

Yes.  That would be nice.  :-)

Good rant.  I love GWT, and still hold out a lot of hope for GWT 3.0.

Off topic:  I do wonder how web assembly (WASM) is going to impact GWT, especially if it gets garbage collection, and therefore makes Java to WASM compilation possible.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8a29b7e1-74fa-4715-a03f-0a6f57bc9aa3%40googlegroups.com.

Re: GWT - Still Active ?

Ideally, twice yearly release of "stable", with most recent appropriate patches applied, such as "2.201904" and "2.201910" or similar tagged releases would definitely help there.

On 5/30/19 3:33 PM, Bob Lacatena wrote:
I just posted this elsewhere, but as this thread has more current responses, I'm reposing it in the hopes that someone will read it:


GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Wednesday, May 29, 2019 at 8:54:05 PM UTC-4, Craig Mitchell wrote:
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/aa688813-7e77-454e-af26-4b06ad2b1b06%40googlegroups.com.

Re: GWT - Still Active ?

I just posted this elsewhere, but as this thread has more current responses, I'm reposing it in the hopes that someone will read it:


GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Wednesday, May 29, 2019 at 8:54:05 PM UTC-4, Craig Mitchell wrote:

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/aa688813-7e77-454e-af26-4b06ad2b1b06%40googlegroups.com.

Re: Is this project active?

GWT is suffering from a very serious publicity debacle.  I'm actively doing GWT development, and regretting every moment of it right now.  Years ago I loved GWT.  Today, I'm dreading it.

My biggest problem for the past year has been the fact that unless one hunts for threads like this, GWT does appear to be dead.  I don't know what the developers are doing.  I just know there were occasional hints that something was coming (a year ago), with not a sound since then.

Update gwtproject.org!  Put a few news items on it a month, at least.  Let people know you are working.  No matter how good your work is, more and more developers like me are going to abandon it as time drags on.

Or create a GWT 3.0 blog.  Something.  Anything other than the black hole of silence you have now.

I'm also very concerned that with the rewrite, every bit of code I'm working on now will be useless.  GWT before 3.0, from a developer who uses it, was and still is a nightmare if you don't want to use every widget, as it exists, out of the box, because too many of the classes use private members and methods, making them completely impossible to extend (which, I believe, is sort of the point of a lot of OOP concepts).

With GWT getting old, this is becoming painful, because GWT did cool things, like animation and date pickers and rich text editors, by brute force back when that was necessary.  Now, however, HTML5 and other things have evolved to offer better, cleaner solutions, but often it's difficult to impossible to make GWT work with those solutions, because of the private members.

I've even gotten into vicious cycles; copy the source for class X, to be able to fix it, but that requites a copy of private class Y, which requires a copy of private class Z, and on and on until I give up.

Instead, I have to "roll my own", which takes too much effort that could be spend on more productive pursuits.  I'd rather use a framework with working widgets.

I didn't start out intending this to be a rant, but the bottom line is that I like GWT, I like being able to work exclusively in one language/framework instead of four at one time (Java + Angular + TypeScript + JQuery), but as a professional who is paid to make decisions that will have a decade-long impact on my company, I am very hard-pressed not to advise my company to immediately abandon all efforts using GWT.

Put some effort into communication!  [Which should be tattooed on the backs of every software engineer's hands, because as a species they seem to be oblivious to the concept.]

I am somewhat heartened by the existence of this thread, but I can't wait 6 months for GWT 3.0, only to find out it's not backwards compatible with much of our efforts, and it's lost so much popularity in the wild that it's considered a death-mark on one's resume.

- Bob

On Thursday, March 28, 2019 at 2:58:47 AM UTC-4, carl.hos...@gmail.com wrote:
Hello all!  I am wondering how active this project is?  Don't see much action on the releases and comments. 

Another question I have is if this project is still active, when will Java 11 support be released?

Thanks  in advance,

Carl

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/11671aa6-f1c9-44ee-a8d3-1e584d2d953d%40googlegroups.com.

Wednesday, May 29, 2019

Re: GWT - Still Active ?

It would be good to have an approximate public release window for GWT 3.0 from the community. Will it happen in 2019?

Also any plans to move release cadence for GWT to match Java's 6-monthly cycles?

-Nick

On 30 May 2019, at 10:54, Craig Mitchell <mail@craig-mitchell.com> wrote:

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/7ab94297-5dd1-4990-88ee-3bac2fbaec94%40googlegroups.com.

Re: GWT - Still Active ?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/7ab94297-5dd1-4990-88ee-3bac2fbaec94%40googlegroups.com.

Re: GWT project data grid double scroll issue in edge browser

This is a known issue, I have encountered it in past. See: https://groups.google.com/forum/#!topic/google-web-toolkit/xxeS6LETdBs

The way I fix it is by adding the following css to the page:

/*Fix for extra scroll bar in celltables*/
::-webkit-scrollbar {
    width
: 10px;
}

::-webkit-scrollbar-thumb {
    width
: 10px;
   
-webkit-border-radius:3px;
    border
-radius:3px;
    background
:rgba(0,0,0,0.3);
}
/*End Fix for extra scroll bar in celltables*/




On Wednesday, May 29, 2019 at 5:17:35 AM UTC-4, Thomas Broyer wrote:
As you can see in your screenshots, columns are not aligned with their headers. This is the reason GWT (tries to) hide the native scrollbars, and "replaces" them with translucent ones (the one you've hidden).


I don't remember how all of this is done, so can't tell if it's a bug in GWT (well, it is indeed, but possibly caused by:) or a bug in MSEdge; as it doesn't happen in Chrome or Firefox.

On Wednesday, May 29, 2019 at 10:27:23 AM UTC+2, Sanoob V wrote:
Hi All,

I am getting two scrollers in datagrid edge browser.

Two scroll.png


and when check inspect code i can see two GWT generated CSS if i remove that one scroll is hiding but I don't know from where it is coming 
please advice me.


css class.png




Hidind class.png







--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/3762be62-05e9-46ca-8157-9a9f3c945c26%40googlegroups.com.

Re: GWT project data grid double scroll issue in edge browser

As you can see in your screenshots, columns are not aligned with their headers. This is the reason GWT (tries to) hide the native scrollbars, and "replaces" them with translucent ones (the one you've hidden).


I don't remember how all of this is done, so can't tell if it's a bug in GWT (well, it is indeed, but possibly caused by:) or a bug in MSEdge; as it doesn't happen in Chrome or Firefox.

On Wednesday, May 29, 2019 at 10:27:23 AM UTC+2, Sanoob V wrote:
Hi All,

I am getting two scrollers in datagrid edge browser.

Two scroll.png


and when check inspect code i can see two GWT generated CSS if i remove that one scroll is hiding but I don't know from where it is coming 
please advice me.


css class.png




Hidind class.png







--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/e219e7a8-c32f-44ae-923b-315a49a19193%40googlegroups.com.

Tuesday, May 28, 2019

GWT project data grid double scroll issue in edge browser

Hi All,

I am getting two scrollers in datagrid edge browser.

Two scroll.png


and when check inspect code i can see two GWT generated CSS if i remove that one scroll is hiding but I don't know from where it is coming 
please advice me.


css class.png




Hidind class.png







--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1f6b0d01-698c-46aa-8a1b-9323c5cf9d18%40googlegroups.com.

Monday, May 27, 2019

Re: GWT - Still Active ?

we had this question the other day but it was in the other form `Is GWT dead`

TLDR: Yes it is still active and we made huge progress as a community toward GTW 3.0, we now have a working j2cl maven plugin, and we have lots of GWT2 ported modules working already in j2cl/gwt3. the ecosystem is growing really nicely.

answers can be found here

On Tuesday, May 28, 2019 at 9:03:01 AM UTC+3, Learner 1980 wrote:
hi guys,
i don't see or hear much about GWT.
Google has also come up with Flutter which I believe would compete with React.

With all these new frameworks coming up and for which the community seems quite active, is GWT still alive?
Is there any plan to release any new versions of GWT?

thanks!

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d6f444eb-2d1d-40e1-abbb-36a349a26014%40googlegroups.com.

A set of libs working in both j2cl and gwt2

Dears

DominoKit is glad to announce a set of small libs that works for both gwt and j2cl :

  •  - domino-slf4j-logger : use slf4j logging on gwt/j2cl client side, good for code portability over the JVM.

 https://github.com/DominoKit/domino-slf4j-logger

  •   domino-aggregator : wait for set of sync operations or events to be completed before executing some code, works perfectly in single thread environment, will be updated to use Futures or Rx later.

 https://github.com/DominoKit/domino-aggregator

  •  domino-history : for working with the browser history state api listening to token changes, filter token, parsing token, updating token, use variable token parameters, good for routing implementations.

 https://github.com/DominoKit/domino-history

  •  domino-jackson : Jackson based JSON mappers using annotation processing, same mapper works on client side and JVM.

 https://github.com/DominoKit/domino-jackson

  •  domino-rest : Brings JaxRs support to the client side, define the Service interface and use JaxRs to generate a client to make REST calls to the server, easy to use and easy to configure.

 https://github.com/DominoKit/domino-rest


 And next we are going to also make both **domino-ui** and **domino-mvp** works on both j2cl and gwt from master branches, and with this we aim to provide a full stack of libs for building apps using GWT/J2CL.

Ported GWT libs used in our libs stack

  •  gwt-cldr
  •  gwt-datetimeformat
  •  gwt-timer
  •  gwt-regexp
  •  gwt-event
  •  gwt-core
  •  typedarrays
 
 happy GWTing, Happy J2CLing. :smile:

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/12d423a8-84b7-4895-875e-48e48bb6799a%40googlegroups.com.

GWT - Still Active ?

hi guys,
i don't see or hear much about GWT.
Google has also come up with Flutter which I believe would compete with React.

With all these new frameworks coming up and for which the community seems quite active, is GWT still alive?
Is there any plan to release any new versions of GWT?

thanks!

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a2dcde72-af4e-4d2e-b7d0-0c38a08092d4%40googlegroups.com.

Thursday, May 23, 2019

Looking for gwt contributors

Hello, I have a fairly large open-source java / gwt project. I'm looking for contributors who would be willing to contribute in order to come-up with new modern layout.

If I'm permitted, I would like to provide github link.

Thanks

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/fd62c527-165f-433c-8229-7968e3f48cb5%40googlegroups.com.

Wednesday, May 22, 2019

Re: GWT MVP Frameworks

I forget to mention:

Another intresting MVP framework is 


and 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/46d6b458-196c-4785-9ba3-b955aa7b1e42%40googlegroups.com.

Re: GWT MVP Frameworks

I forget to mention:

Another intresting MVP framework is Nalu: https://github.com/NaluKit/nalu 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/63d2bf9c-44cd-4e7f-97ef-c43d9238569b%40googlegroups.com.

Sporadic 404 error. Sporadic Black Screen

I am using GWT client 2.7 in my application for window handling. We are having 2 issues.

1. Some users getting sporadic 404 error. After closing the window,clearing cache and cookies, and open the new instance will clear the issue.

seems like its not registering base url. 
We are using ie browser running compatibility view mode. 

2. Another issue we are getting is black screen. It looks like after working for some time window getting black screen,it looks like GWT client not ready.

I appreciate any help on this. 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b087a938-d615-47ea-a31b-43b58129dfbe%40googlegroups.com.

Tuesday, May 21, 2019

Re: DisclosurePanel

When you create the DisclosurePanel you can provide the text for the header:

DisclosurePanel(java.lang.String headerText)




On Wednesday, May 22, 2019 at 3:59:16 PM UTC+10, naaser ahmed wrote:
Hello, 

I am trying to make my website compatible with Accessibility and running into "Links must have discernible text" error. On inspecting, the error is being generated by Links being generated by Disclosure Panel. The link being created is this -- "<a href="javascript:void(0);" style="display: block;" class="header"></a>". Can someone please let me know how I can add title to the link. 

I appreciate all the help. 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/e921ddc3-d6d8-4e6c-af19-497f62981984%40googlegroups.com.

DisclosurePanel

Hello, 

I am trying to make my website compatible with Accessibility and running into "Links must have discernible text" error. On inspecting, the error is being generated by Links being generated by Disclosure Panel. The link being created is this -- "<a href="javascript:void(0);" style="display: block;" class="header"></a>". Can someone please let me know how I can add title to the link. 

I appreciate all the help. 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9b23e5fc-b743-425f-8b52-5f40168a69cb%40googlegroups.com.

Slow Thinking: Unbundling Professional Support

Slow Ventures Snail Mail

Stop Employee Performance Management


Tuesday, May 21, 2019

Welcome to another edition of Snail Mail! Today we are featuring podcast with the Co-Founder & CEO of Enrich, Jordana Stein, focused on professional support.

Got forwarded this and want to subscribe? Go to https://slow.claims. 
🎙 Slow Thinking: Unbundling Professional Support

Click here for full podcast!

At Slow, we have been doing a lot of thinking about how to best unbundle services for employees that used to be provided by corporations. We think there is a strong argument that as technology makes the job market more liquid and careers become a series of discrete episodes, individuals will be taking more and more personal responsibility for the career guidance, support, and learning that they need to keep growing professionally.

Recently, Alex sat down with the Founder & CEO of enrich, Jordana Stein, to get her perspective. 

enrich is a private network for knowledge sharing amongst professionals. Currently, enrich provides C-suite and senior leaders across companies a platform to share best practices and insider tips on how to best grow their companies to scale. Members are matched based on similar functions into small groups (6-8) for IRL or offline guided discussions on topics that range from marketing to product design to how to best manage remote teams.  It's kind of like a YPO for everyone else. 

Highlights:

0:20 — What is Enrich?

4:02 — Trust! How do you enable authentic content and dialog?

9:17 — the employee lifecycle: what are employee's biggest challenges and how can they get support?

12:00 — How to work with companies to make sure they are focused on developing employee talent?


If you are interested in learning more about Enrich, please email their team at memberinvites@joinenrich.com!
🌮 Food for thought

Want moar? Check us out on:
Facebook, Twitter, Medium or our Website

Signup for Snail Mail Newsletters at  http://slow.claims
Our mailing address is:
1006 Kearny St, San Francisco, CA 94133

Don't Want These Emails?
unsubscribe from this list
 

Donate BTC: 3BJW4B6GGpoQrjeom6RpVtkza3XPw2qjoK
Donate ETH: 0xD7599b3D15805aDF3144676914964e8fff53C925