Pausing or canceling native preview event handling ?

[Ed]

Please some tips/advice on the following situation (gwt version: 2.7.0):

I have a site with a Member Subscribe popup that is automatically hidden 
when you click (tap) outside the popup, that I realized through a 
NativePreviewHandler. That works well.
However, the popup has a link that opens a modal (glassPanel) popup that 
blocks any interaction with the app apart from the new popup itself. But 
when I then click somewhere the Subscribe popup behind the modal popup is 
hidden because of the preview event handling, which is undesired.
How to solve this?
The modal popup also uses a NativePreviewHandler to block any interaction 
with the display apart from the modal popup.

The solution I can think of:
Cancel/prevent the preview event being processed by the Subscribe popup 
when the modal popup is open.
But how?:
1) It's hard to inform the subscribe popup when modal popup is opened and 
closed, the are independent and get's dirty to link them together. Besides 
that, most code is generated from xml files through html5 data-* fields.

2) The modal popup adds his own NativePreviewHandler and will block/cancel 
any further Native preview event handling, such that the subscribe popup 
isn't informed. This could be possible as the NativePreviewHandler 
instances are fired in reversed order. 
But the NativePreviewHandler event has not such thing as a cancel option 
:(... I looked at overriding the gwt code, but that also gets dirty. 
I could create my own PreviewEvent that contains all NativePreviewHandlers, 
and has one NativePreviewHandler registered to the GWT event class. We then 
have control of enabling/disabling handlers

3) Not use a NativePreviewHandler in the subscribe popup, but a normal 
"Handler" on the body element that informed about 
clicks/taps/mouse-up/etc.. 
This handler can be canceled by the NativePreviewHandlers in case they 
indicate the event isn't allowed to be "normally" processed.

I don't like the solutions soo much and was wondering if anybody has some 
advice/ideas/solution that I don't see? 
Please shout ;)

Btw, you can the situation in action on leuker.nl: click "login" in the top 
menu, then click on "account aanmaken" and click on "pricacy voorwaarden" 
to show the modal popup.



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

Re: Where is GWT Elemental?

[Ming-Yee Iu]

That's the one I watched. After rooting around the GWT Elemental code over 
the past week, I think that there is no Elemental 2.0 at the moment (or, at 
least, there's no public Elemental 2.0 at the moment). None of the 
Elemental code I saw used JsInterop, Elemental still used a lot of stuff 
borrowed from Dart to generate its code, its code is generated from WebKit 
interface definitions, and it doesn't seem like anyone is really working on 
Elemental at the moment (it still has the same bugs and annoyances that 
have been there for years). As far as I can tell, Elemental 2.0 and 
JsInterop are more in the "future plans" category.




On Friday, 5 June 2015 23:12:21 UTC-4, Thad Humphries wrote:
>
> You mean this video?  *GWT.create 2015 - Deep dive in JS Interop (Ray 
> Cromwell) *
>
> If not, which one? I have the Polymer bug.
>
> On Friday, June 5, 2015 at 3:03:23 PM UTC-4, Ming-Yee Iu wrote:
>>
>> Never mind. I watched the JsInterop video and caught up.
>>
>>
>>

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

ElementalFx: GWT Elemental for the Desktop

[Ming-Yee Iu]

I finished porting GWT Elemental to JavaFx's WebView. I call it 
ElementalFx. The code is sitting in the "elementalfx" branch of my clone of 
the GWT git repository:

  https://github.com/my2iu/gwt

With ElementalFx, you can use GWT Elemental to make desktop apps. You can 
use the same UI code for both the desktop and for the web. It can be 
helpful in use cases like

1) You need to write a web-version and a PC/Mac/Linux-version of an app, 
and you don't want to write the UI code twice
2) You want to write a UI widget and share it between a HTML5 web page and 
a desktop application
3) You have an existing Swing or SWT application, and you want to migrate 
it to HTML5 by gradually replacing components and dialogs with HTML5 
versions
4) You need to write a desktop application, but you don't want to waste 
your time learning a niche desktop UI framework when you could just use 
HTML5 for everything
5) You have some legacy Java UI programmers, and you want to upgrade their 
skills to include HTML5 in a gradual manner
6) You want to debug and test a GWT Elemental application without using 
SuperDevMode or DevMode

In the future, I would like to port Elemental to Android and iOS too, then 
you could reuse your UI code across web, mobile, and desktop. I don't have 
the cycles to take that on in the near future though. My initial look at 
the Android WebView suggested that it didn't export the right interface 
needed to support something like Elemental, so doing the port would involve 
creating a custom WebView that can be embedded in apps, which is a lot of 
work.

Just thought some of you might be interested,
Ming

p.s. As a demonstration of it working, I took a game I wrote for a game jam 
in Elemental and adapted it to run in ElementalFx. Here's a screenshot of 
it running in Linux:

  http://www.jinq.org/elementalfx-screen.png

The game uses 2 Canvas elements, several DIVs that are updated using 
innerHTML, JSON processing, a timer, and keyboard events.

In order to get things to work, I had to do these things:

1) Using XMLHttpRequest would cause the JVM to crash (I think it's a bug in 
JavaFx). Since this was now a desktop Java program, it was fairly easy just 
to replace that code with something that used real Java instead

2) All my sound effects using HTML5 Audio caused 
IllegalThreadStateException errors. I imagine JavaFx probably doesn't 
properly support audio in its WebView or something.

3) The original code used Browser.getWindow() and Browser.getDocument() a 
lot to get at the window and document objects. This doesn't make sense in 
ElementalFx because the Java code does not run in the context of a web 
page. In fact, a desktop Java application can have multiple WebViews with 
multiple windows and documents. I had to change my code to pass in the 
window/document to use when doing UI stuff

4) I had to remove the script tag that would run the compiled GWT JS code 
from the HTML. Instead, my Java code would just run itself after it had 
loaded the HTML.

5) I needed to write my own bootstrap code to start the application. Here 
is what it looks like:

@GwtIncompatible
public class FxMain extends Application
{
  public static void main(String[] args) 
  {
launch(args);
  }

  @Override
  public void start(Stage stage) throws Exception {
// Create the WebView
VBox region = new VBox();
WebView webView = new WebView();
final WebEngine engine = webView.getEngine();
region.getChildren().add(webView);

Scene scene = new Scene(region);
stage.setScene(scene);
stage.show();

// Redirect the alert handler to send output to stderr
engine.setOnAlert(new EventHandler>() {
  @Override
  public void handle(WebEvent msg) {
System.err.println(msg.getData());
  }});

// Start up the Gwt module when the page has finished loading. Grab the 
window
// and document objects and stash them somewhere for use later.
engine.getLoadWorker().stateProperty().addListener(
new ChangeListener() {
  @Override
  public void changed(ObservableValue ov,
  State oldState, State newState) {
if (newState == Worker.State.SUCCEEDED) {
  Module.win = 
(Window)GwtFxBridge.wrapJs(engine.executeScript("window"));
  Module.doc = Module.win.getDocument();
  new Module().onModuleLoad();
}
  }
});

// Load the main Gwt application web page
engine.load(new File("index.html").toURI().toURL().toExternalForm());
  }
}

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

Re: Important videos from GWT Meet-up 2015

[jchimene]

Thanks, Jens!

@Brandon: would you please check your slides? The "Copy of ..." isn't 
loading, and I don't see the slides for the "Contributing to Eclipse..." 
presentation.

tia,
jec

On Friday, June 12, 2015 at 7:55:05 AM UTC-7, Jens wrote:
>
>
> To those who've generously uploaded the videos: any possibility of also 
>> uploading the slides? The technical presentations are pretty much useless 
>> w/o the slides.
>>
>
> The Youtube playlist has a link at the top pointing to a Google Drive 
> containing the slides.
>
> -- J.
>

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

Re: Important videos from GWT Meet-up 2015

[Jens]

> To those who've generously uploaded the videos: any possibility of also 
> uploading the slides? The technical presentations are pretty much useless 
> w/o the slides.
>

The Youtube playlist has a link at the top pointing to a Google Drive 
containing the slides.

-- J.

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

Re: Important videos from GWT Meet-up 2015

[James Horsley]

Someone in the video commented that there needs to be a very clear
messaging around how to best protect/"future proof" yourself. The
Modernizing GWT video was obviously a step in that direction but I'd love
to see something more concrete e.g. if UiBinder won't be supported, what
should we be using?

I had a specific question regarding the recommendation to use Elemental. My
understanding was that Elemental 2.0 was going to be released with GWT 3.0.
Is it safe to use Elemental in it's current state or will there be
significant enough changes that we should wait?

On 12 June 2015 at 15:29, jchimene  wrote:

> Thanks for the link .
>
> To those who've generously uploaded the videos: any possibility of also
> uploading the slides? The technical presentations are pretty much useless
> w/o the slides.
>
> TIA,
> jec
>
>
> On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote:
>>
>> I thought I'd share this link to a series of important videos from the
>> recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors
>> group:
>>
>> https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>>
>> *Summary:*
>>
>> For anyone who wasn't already aware, there are seismic changes coming for
>> GWT. Basically, gwt-user and everything in it will be gradually mothballed,
>> so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT
>> compiler will probably go too. If the plan stays as presented, everything
>> is going, sooner or later. It looks as though a much simpler and faster
>> Java to JS transpiler is proposed, maybe under a different project name,
>> with optimizations handled by Closure. I welcome corrections if I've got
>> something wrong here.
>>
>> *Editorial:*
>>
>> Having used GWT for a number of years, I think this is a massive but
>> needed change. It looks like a great direction, that maybe could have been
>> taken even sooner. But personally, I now can't see using GWT for new
>> projects until it appears in its new form. We're in a kind of purgatory now
>> where anything you write in GWT may not be easy to maintain, but the new
>> vision is currently just a hope for the future.
>>
>> As for myself, since I've got a project in its early stages, I'll
>> probably be porting everything I have to JavaScript, until I can count on a
>> stable Java to JS transpiler. At that point, I can decide to move some of
>> the code back to Java, if it's not too painful and the benefits to doing so
>> are clear. At the same time, even with years of Java experience, I have to
>> ask myself, why Java? If it's a better language that compiles to JavaScript
>> that we want, there are many: Dart is coming along, and there are more
>> options than there were before. It's speculation to say what an open source
>> Swift will mean, but the external forces affecting these options can play
>> themselves out while JavaScript will likely continue to be stable for years
>> to come.
>>
>> So rather than drag it out, I'd like to see these changes happen ASAP. As
>> it's sometimes said, "if you find yourself in a hole, stop digging." I
>> believe that if a stable and fast Java to JS transpiler were released, the
>> community would chip in to help complete JRE emulation or other needed
>> projects, and I'm glad to hear that much of the GWT team is being diverted
>> to compiler work.
>>
>> Thanks to the GWT team for sharing these plans with the community!
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Important videos from GWT Meet-up 2015

[jchimene]

Thanks for the link .

To those who've generously uploaded the videos: any possibility of also 
uploading the slides? The technical presentations are pretty much useless 
w/o the slides.

TIA,
jec

On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote:
>
> I thought I'd share this link to a series of important videos from the 
> recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors 
> group:
>
> https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>
> *Summary:*
>
> For anyone who wasn't already aware, there are seismic changes coming for 
> GWT. Basically, gwt-user and everything in it will be gradually mothballed, 
> so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT 
> compiler will probably go too. If the plan stays as presented, everything 
> is going, sooner or later. It looks as though a much simpler and faster 
> Java to JS transpiler is proposed, maybe under a different project name, 
> with optimizations handled by Closure. I welcome corrections if I've got 
> something wrong here.
>
> *Editorial:*
>
> Having used GWT for a number of years, I think this is a massive but 
> needed change. It looks like a great direction, that maybe could have been 
> taken even sooner. But personally, I now can't see using GWT for new 
> projects until it appears in its new form. We're in a kind of purgatory now 
> where anything you write in GWT may not be easy to maintain, but the new 
> vision is currently just a hope for the future.
>
> As for myself, since I've got a project in its early stages, I'll probably 
> be porting everything I have to JavaScript, until I can count on a stable 
> Java to JS transpiler. At that point, I can decide to move some of the code 
> back to Java, if it's not too painful and the benefits to doing so are 
> clear. At the same time, even with years of Java experience, I have to ask 
> myself, why Java? If it's a better language that compiles to JavaScript 
> that we want, there are many: Dart is coming along, and there are more 
> options than there were before. It's speculation to say what an open source 
> Swift will mean, but the external forces affecting these options can play 
> themselves out while JavaScript will likely continue to be stable for years 
> to come.
>
> So rather than drag it out, I'd like to see these changes happen ASAP. As 
> it's sometimes said, "if you find yourself in a hole, stop digging." I 
> believe that if a stable and fast Java to JS transpiler were released, the 
> community would chip in to help complete JRE emulation or other needed 
> projects, and I'm glad to hear that much of the GWT team is being diverted 
> to compiler work.
>
> Thanks to the GWT team for sharing these plans with the community!
>
>

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

Re: Important videos from GWT Meet-up 2015

[Phineas Gage]

One thing I may have overstated is that there's a slide discussing what 
*may* be ported forward (Modernizing GWT Applications 
,
 
around 18:45), which *may* include GSS and ClientBundles, i18n (since 
that's in a different module from gwt-user), UiBinder, SafeHtmlTemplates 
and PlaceHistoryMapperGenerator. But then at 32:30 in the same video a 
mention of "probably not with UiBinder", so UiBinder may not stay, 
particularly if Singular is available which looks like be a much better 
solution (and they're looking for contributions to that).

A name change for GWT is discussed in GWT 2.8 and Beyond 
,
 
30:35. Not clear what the result of that will be, but if so much changes, a 
name change would probably be good to shed the baggage. I also like 32:35 
in the same video: "Any other questions? Is anybody like scared, or, uh, 
shocked?" :)

At some point someone discussed making a table of what will and will not be 
brought forward, so that would be useful for the community to see.

And again, I'm really looking forward to seeing the evolution, but it feels 
like we're still a ways away from that, so knowing what to do in 
development now is challenging.

On Friday, June 12, 2015 at 3:40:59 PM UTC+2, Phineas Gage wrote:
>
> I'd also like to hear if I misstated or misunderstood something. I 
> listened to all of the videos and in the discussion I heard more about 
> re-writing and renaming than keeping much of anything.
>
>

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

Re: Important videos from GWT Meet-up 2015

[Phineas Gage]

First video, "GWT 2.8 and Beyond", starting around 17:20...

I'd also like to hear if I misstated or misunderstood something. I listened 
to all of the videos and in the discussion I heard more about re-writing 
and renaming than keeping much of anything.

On Friday, June 12, 2015 at 3:20:03 PM UTC+2, Thomas Lefort wrote:
>
> Is the phasing out of gwt-user something you heard when attending the 
> meetings? It may be a question of interpretation but I don't read the same 
> from the slides. Sounds more like a fork of GWT to me. Of course if all 
> efforts go to the new project, then it is in effect the same thing ;-) may 
> be some clarifications from the GWT contributors would help.
>
>

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

GWT Meet-up 2015 : which technologies for new project

[maticpetek]

He,
   I watch videos from GWT Meet-up 2015 and we will start some new projects 
with GWT. I would like to prepare them for GWT 3.0, so please advice us 
which technologies should we take.
1) HTML templates
For now, my reference was talk from Julien on GWT.create 2015 - Best 
development practice for GWT web application (https://goo.gl/q6WDje). We 
are using UiBinder (with only HTMLPanel) + GSS Resources + gQuery. 
As I can see from videos, UIBinder will be drop. 

2) CellWidget, CellCell, CellTable
Are they part of Widget system and they should be avoided?

3) DOM 
Right now we really like gQuery. Should be stick with it?

4) i18n (Localization)
Probably nothing right now. I expect GWT team will provide alternative with 
GWT 3.0.

5) we are using GWT.create for web / mobile GUI component presentation. 
Should we migrate on getProperties + Class Factory design pattern? Will 
this also benefit SDM in GWT 2.8?

Thank you,
Regards,
  Matic

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

Re: Important videos from GWT Meet-up 2015

[Thomas Lefort]

Is the phasing out of gwt-user something you heard when attending the 
meetings? It may be a question of interpretation but I don't read the same 
from the slides. Sounds more like a fork of GWT to me. Of course if all 
efforts go to the new project, then it is in effect the same thing ;-) may 
be some clarifications from the GWT contributors would help.


On Friday, 12 June 2015 11:21:49 UTC+2, Phineas Gage wrote:
>
> I thought I'd share this link to a series of important videos from the 
> recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors 
> group:
>
> https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>
> *Summary:*
>
> For anyone who wasn't already aware, there are seismic changes coming for 
> GWT. Basically, gwt-user and everything in it will be gradually mothballed, 
> so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT 
> compiler will probably go too. If the plan stays as presented, everything 
> is going, sooner or later. It looks as though a much simpler and faster 
> Java to JS transpiler is proposed, maybe under a different project name, 
> with optimizations handled by Closure. I welcome corrections if I've got 
> something wrong here.
>
> *Editorial:*
>
> Having used GWT for a number of years, I think this is a massive but 
> needed change. It looks like a great direction, that maybe could have been 
> taken even sooner. But personally, I now can't see using GWT for new 
> projects until it appears in its new form. We're in a kind of purgatory now 
> where anything you write in GWT may not be easy to maintain, but the new 
> vision is currently just a hope for the future.
>
> As for myself, since I've got a project in its early stages, I'll probably 
> be porting everything I have to JavaScript, until I can count on a stable 
> Java to JS transpiler. At that point, I can decide to move some of the code 
> back to Java, if it's not too painful and the benefits to doing so are 
> clear. At the same time, even with years of Java experience, I have to ask 
> myself, why Java? If it's a better language that compiles to JavaScript 
> that we want, there are many: Dart is coming along, and there are more 
> options than there were before. It's speculation to say what an open source 
> Swift will mean, but the external forces affecting these options can play 
> themselves out while JavaScript will likely continue to be stable for years 
> to come.
>
> So rather than drag it out, I'd like to see these changes happen ASAP. As 
> it's sometimes said, "if you find yourself in a hole, stop digging." I 
> believe that if a stable and fast Java to JS transpiler were released, the 
> community would chip in to help complete JRE emulation or other needed 
> projects, and I'm glad to hear that much of the GWT team is being diverted 
> to compiler work.
>
> Thanks to the GWT team for sharing these plans with the community!
>
>

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

Re: Important videos from GWT Meet-up 2015

[Phineas Gage]

There's no technical reason why not Java the language, but as for the 
infrastructure available for compiling Java to JavaScript and getting 
convenient bidirectional access to the JavaScript universe for use in a web 
application, there are more questions now.

Let's say you want to use GWT 2.8 and JsInterop with Polymer. You still 
have to use JSNI to instantiate JavaScript objects, but that's now 
discouraged because it will go away. Even when GWT 2.8 is released, the 
implementation of JsInterop itself will change if the GWT compiler is 
abandoned in favor of the transpiler. JsInterop annotations may then have 
to change again due to unforeseen circumstances, but that is speculation.

Meanwhile, what do you do about RPC, or i18n, for example? You can push 
more and more functionality into JavaScript, but then you lose some of the 
benefits of Java. Anything that depends on gwt-user is to be avoided. There 
is a nice video suggesting what direction to take 
(https://www.youtube.com/watch?v=0flgI0AMJjk&index=8&list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE),
 
but it's worth thinking through just how different applications will look 
that are written to these recommendations vs a standard GWT application 
today.

On Friday, June 12, 2015 at 11:42:37 AM UTC+2, Alain wrote:
>
> Well the question  could also be  why not  java ? 
>

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

Re: Important videos from GWT Meet-up 2015

[Alain Ekambi]

Well the question  could also be  why not  java ?

On 12 June 2015 at 11:21, Phineas Gage  wrote:

> I thought I'd share this link to a series of important videos from the
> recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors
> group:
>
> https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>
> *Summary:*
>
> For anyone who wasn't already aware, there are seismic changes coming for
> GWT. Basically, gwt-user and everything in it will be gradually mothballed,
> so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT
> compiler will probably go too. If the plan stays as presented, everything
> is going, sooner or later. It looks as though a much simpler and faster
> Java to JS transpiler is proposed, maybe under a different project name,
> with optimizations handled by Closure. I welcome corrections if I've got
> something wrong here.
>
> *Editorial:*
>
> Having used GWT for a number of years, I think this is a massive but
> needed change. It looks like a great direction, that maybe could have been
> taken even sooner. But personally, I now can't see using GWT for new
> projects until it appears in its new form. We're in a kind of purgatory now
> where anything you write in GWT may not be easy to maintain, but the new
> vision is currently just a hope for the future.
>
> As for myself, since I've got a project in its early stages, I'll probably
> be porting everything I have to JavaScript, until I can count on a stable
> Java to JS transpiler. At that point, I can decide to move some of the code
> back to Java, if it's not too painful and the benefits to doing so are
> clear. At the same time, even with years of Java experience, I have to ask
> myself, why Java? If it's a better language that compiles to JavaScript
> that we want, there are many: Dart is coming along, and there are more
> options than there were before. It's speculation to say what an open source
> Swift will mean, but the external forces affecting these options can play
> themselves out while JavaScript will likely continue to be stable for years
> to come.
>
> So rather than drag it out, I'd like to see these changes happen ASAP. As
> it's sometimes said, "if you find yourself in a hole, stop digging." I
> believe that if a stable and fast Java to JS transpiler were released, the
> community would chip in to help complete JRE emulation or other needed
> projects, and I'm glad to hear that much of the GWT team is being diverted
> to compiler work.
>
> Thanks to the GWT team for sharing these plans with the community!
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.com/ 

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

Important videos from GWT Meet-up 2015

[Phineas Gage]

I thought I'd share this link to a series of important videos from the 
recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors 
group:

https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE

*Summary:*

For anyone who wasn't already aware, there are seismic changes coming for 
GWT. Basically, gwt-user and everything in it will be gradually mothballed, 
so widgets, GWT-RPC, UiBinder, CssResource, etc. While we're at it, the GWT 
compiler will probably go too. If the plan stays as presented, everything 
is going, sooner or later. It looks as though a much simpler and faster 
Java to JS transpiler is proposed, maybe under a different project name, 
with optimizations handled by Closure. I welcome corrections if I've got 
something wrong here.

*Editorial:*

Having used GWT for a number of years, I think this is a massive but needed 
change. It looks like a great direction, that maybe could have been taken 
even sooner. But personally, I now can't see using GWT for new projects 
until it appears in its new form. We're in a kind of purgatory now where 
anything you write in GWT may not be easy to maintain, but the new vision 
is currently just a hope for the future.

As for myself, since I've got a project in its early stages, I'll probably 
be porting everything I have to JavaScript, until I can count on a stable 
Java to JS transpiler. At that point, I can decide to move some of the code 
back to Java, if it's not too painful and the benefits to doing so are 
clear. At the same time, even with years of Java experience, I have to ask 
myself, why Java? If it's a better language that compiles to JavaScript 
that we want, there are many: Dart is coming along, and there are more 
options than there were before. It's speculation to say what an open source 
Swift will mean, but the external forces affecting these options can play 
themselves out while JavaScript will likely continue to be stable for years 
to come.

So rather than drag it out, I'd like to see these changes happen ASAP. As 
it's sometimes said, "if you find yourself in a hole, stop digging." I 
believe that if a stable and fast Java to JS transpiler were released, the 
community would chip in to help complete JRE emulation or other needed 
projects, and I'm glad to hear that much of the GWT team is being diverted 
to compiler work.

Thanks to the GWT team for sharing these plans with the community!

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