[ovirt-devel] GWT vs. Java

[Roy Golan]

On 10/03/2014 06:19 PM, Vojtech Szocs wrote:
>
> ----- Original Message -----
>> From: "Yair Zaslavsky" <yzaslavs at redhat.com>
>> To: "Vojtech Szocs" <vszocs at redhat.com>
>> Cc: devel at ovirt.org
>> Sent: Friday, October 3, 2014 4:37:36 PM
>> Subject: Re: [ovirt-devel] GWT vs. Java
>>
>>
>>
>> ----- Original Message -----
>>> From: "Vojtech Szocs" <vszocs at redhat.com>
>>> To: devel at ovirt.org
>>> Sent: Friday, October 3, 2014 4:29:15 PM
>>> Subject: [ovirt-devel] GWT vs. Java
>>>
>>> Hi guys,
>>>
>>> I've had a discussion with Roy about GWT vs. Java plans,
>>> he asked me to share this information, so here we go.
>>>
>>> GWT 2.6
>>> =======
>>> - patch pending merge: http://gerrit.ovirt.org/#/c/32135/
>>> - support for Java 7 language syntax like <> operator etc.
>>> - once patch ^^ is merged, we can consolidate Java language
>>>    compliance for whole Engine -> both frontend and backend
>>>    can use Java 7 (yey!)

Good news - @amureini prepare the nose of the Animal Sniffer :)
@Vojtech keep us posted so we'll bump the language version of common

Curious to know, does GWT have a WebSockets module for 2 way 
communication with the backend and are we planning to use it?

>>> GWT 2.7
>>> =======
>>> - planned support for *only* Java 8 language syntax like
>>>    lambdas etc. but *without* emulating new Java 8 APIs like
>>>    streams etc. (Java 8 API emulation should come in GWT 3.0)
>>>
>>> Likely, GWT 2.7 will remove GWT deRPC implementation on which
>>> we currently rely on. (@Martin, can you please share details?)
>>>
>>> This means that until we move UI to REST API, we can't upgrade
>>> post GWT 2.6, so this will put more pressure to work on oVirtJS
>>> project in consequence.
>>>
>>> GWT 3.0
>>> =======
>>> - ETA early next year?
>>> - planned to fully support Java 8 -> both language and APIs
>>> - one of key highlights is better integration with JavaScript,
>>>    which fits the scenario where GWT "application" is one module
>>>    that's part of bigger application (hybrid approach)
>> Thanks for sharing with us!
>> Can you please elabroate more on this hybrid approach?
> With "hybrid approach" I meant a situation where the web application
> consists of distinct modules, each module providing some functionality.
>
> The common base technology for all modules, as well as for the module
> infra itself, is JavaScript. Each module can export APIs that other
> modules can consume. The whole complexity of web application is broken
> by dividing its logical parts into modules. Each module can be built
> (and packaged too) as a separate project.
>
> For a long time, I felt that GWT lived in its "own" world, with vast
> majority of GWT use cases = GWT to implement the whole web application.
>
> GWT 3.0 should provide better JavaScript integration, so GWT can also
> more easily fill the role of a "module" as opposed to the traditional
> role of "the whole application".

Does this mean you're thinking of replacing some of the frontend parts
with plain javascript and html and make them play with the GWT modules?

>> Cheers,
>> Yair
>>
>>> Regards,
>>> Vojtech
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel