GWT 3.0 - question

393 views
Skip to first unread message

Frank Hossfeld

unread,
Aug 24, 2015, 9:21:08 AM8/24/15
to GWT Contributors

In connection with the upcomming GWT release 3.0 I have started playing around with annotation processors in one of my GWT project (mvp4g). I generated some GWTEvent and EventHandler classes and generated the code to fire the events. All works fine. But thinking about GWT 3.0 I am not sure, if GWTEvent and SimpleEventBus classes will be part of GWT 3.0.  Same question about classes like UiObject, Widget, IsWidget, etc. 


It would be good if someone from GWT team can point out ,which classes will survive and can be used in new project, so that the project will work with GWT 3.0 with less (or no) changes.


Thanks

Jens

unread,
Aug 24, 2015, 9:45:46 AM8/24/15
to GWT Contributors
Event/GwtEvent and EventBus/SimpleEventBus is plain Java and should just work. 

Only stuff that relies on GWT.create() and/or JSO/JSNI would need to be ported to be compatible to GWT 3.0, e.g. the DOM/Widget system.

-- J.

Frank Hossfeld

unread,
Aug 24, 2015, 9:47:51 AM8/24/15
to GWT Contributors
The question is: will this classes be part of GWT 3.0?

Jens

unread,
Aug 24, 2015, 11:34:30 AM8/24/15
to GWT Contributors

The question is: will this classes be part of GWT 3.0?

In one way or another they should be available for GWT 3.0. But don't expect most 2.x library code to be available when GWT 3 is release. I could imagine that ports for GWT 3 will be released incrementally. Some things don't need to be ported like the EventBus stuff, others are easy to port like Places, ClientBundle. Medium complex are DOM/Widget and finally some stuff is difficult to port like UiBinder or nearly impossible without accepting breaking changes, e.g. GWT-RPC.

I think its a bit early to get concrete answers but most stuff should be available for GWT 3. However you might need to think about your library generally because with GWT 3 people might start favoring Elemental/JsInterop for new apps and won't choose a library that requires the widget system. Time will tell.

-- J.

Frank Hossfeld

unread,
Aug 24, 2015, 1:09:48 PM8/24/15
to GWT Contributors
Am Montag, 24. August 2015 17:34:30 UTC+2 schrieb Jens:

The question is: will this classes be part of GWT 3.0?

In one way or another they should be available for GWT 3.0. But don't expect most 2.x library code to be available when GWT 3 is release. I could imagine that ports for GWT 3 will be released incrementally. Some things don't need to be ported like the EventBus stuff, others are easy to port like Places, ClientBundle. Medium complex are DOM/Widget and finally some stuff is difficult to port like UiBinder or nearly impossible without accepting breaking changes, e.g. GWT-RPC.

Thanks, that sounds logical.
 

I think its a bit early to get concrete answers but most stuff should be available for GWT 3. However you might need to think about your library generally because with GWT 3 people might start favoring Elemental/JsInterop for new apps and won't choose a library that requires the widget system. Time will tell.

Even setting on Elemental/JsInterop I think there must be something like AcceptsOneWidget and so on ... Also I would expect that Sencha will do something related to the widget system. I don_t think that they will stop developing (and selling) GXT. Let's wait and see.
 
-- J.
Reply all
Reply to author
Forward
0 new messages