[Yanel-dev] GWT usage for AJAX features in Yanel

[Evaldas Taroza]

simon litwan wrote:
> Evaldas Taroza schrieb:
>> Hi,
>> We were discussing that with Simon. One should know that GWT allows 
>> both server and client side development. I don't know how to deal with 
>> the server side, I can only tell you that it allows you to create 
>> "servlets" with methods that you can call via RPC. I am not sure how 
>> and where to put it in Yanel.
>>
>> Client side is pretty straightforward:
>> 1. You develop the JS library as a separate JAVA (GWT) project, then 
>> you need to put the compiled JS files where appropriate
>> 2. You develop in JAVA and then build everything together with the Yanel.
> after i had a closer look at gwt i really like it.
> i think the benefit of writing ajax stuff without the need of having 
> knowledge of javascript is huge for a a java based cms.
> 
> what i don't like so far is the workflow as evaldas proposed it. develop 
> your widget, generate js from java via gwt, copy the js over to your 
> resource or content. i would appreciate if the ajax source is also 
> located in the resource and gets compiled by the build of the resource 
> using gwt. the yanel build process would need to have access to the gwt 
> which probably could be downloaded via maven.
> 
> not sure someone agrees but i like if things are together if they belong 
> together. i think it's very time consuming and increases the learning 
> curve if one wants to modify a resource-type which uses ajax and first 
> has to find out where the source of the ajax widget used by this 
> resource is located, then download gwt to generate the new js files and 
> then copy them to the resource.

I agree that this could be a nice integration strategy. If we also 
manage to put server side GWT into Yanel, then Yanel may end-up as a 
very very AJAXy CMS, which I think is a competitive advantage.

Evaldas