Re: j2s-development] gwt groups post

[Zhou R. <jo...@sj...>]

Ash Wima wrote:
>> Hi Ash and all,
>>
>> I am still thinking a little about GWT's Java to JavaScript compiler.
>> And it seems that there are ways for Java2Script compiler to compile
>> Java2Script's SWT applications in GWT-like way. It means that the
>> performance of Java2Script will be improved and *.js file size will be
>> decreased a lot! And there are ways to keep current dynamical module
>> loading and java reflection either.
>>     
>
> hey Zhou,
>
> this is great news. i really plan to follow up on this thread in a day
> or so. i am currently way under prepared to deliver a presentation on
> GWT tomorrow so i dont have time at the moment.
>
> see http://www.slatteryit.com.au/eja_industry_forum_melb.html
>
>
>   
>> Ash, as once you said, you spent some time trying to integrate GWT and
>> J2S together. Maybe you see something we never see yet. Would you like
>> to share your ideas with us? And what about the above new compiling way
>>     
>
> the one thing that i would like you and your community to consider is
> what the _real_ value proposition of j2c is.
>   
Well, this is a big question for Java2Script compiler.
> the tension that i personally experience with j2c is that i see a
> great opportunity to address a void in gwt that will likely never be
> addressed. but then i reconsider it and feel that it is orthogonal to
> you and your communities goals.
>   

> i believe what you have engineered is fantastic, but is it solving the
> right problem?
>   
Some words: What is the right problem?

That is actually a big question not only just for me, may be also for 
you and for all AJAX toolkit and framework designers. Yes, from my early 
experience, 200k+ *.js will be reached very easily  for AJAX 
applications. So when Java2Script generated about 400k+ *.js for 
java.util.* and SWT.libraries, I just took it for granted. :) In my 
early thoughts, such size of *.js was OK for rich *Intranet* 
applications. And in early days of Java2Script, I took fast development 
and deployment as an inner goal. It seemed at that time I accepted that 
fast developed or easily mantained solutions are more likely to be accepted.

And I am sure want to hear what is your or your customers' problems over 
java to javascript RIA solutions.
> more on this later. i wanted to ping u back so that u didnt think i
> lost interest in the thread.
>
>   
If your representation will be published online, please let GWT group 
and us know.
> best wishes
> ash
> http://www.gworks.com.au
>
> -------------------------------------------------------------------------
>
>
>   

-- 

Regards,
Zhou Renjian

http://j2s.sourceforge.net/
Java2Script: Bridge of RCP to RIA
Reusing Java codes and tools into JavaScript