On 19 Sep 2006, at 21:55, backspaces wrote:
> This is a killer for my project. Our research group depends on
> deployability. The example I gave before of Processing.org's system:
>
http://www.backspaces.net/models/Stadium/applet/> was done to show our client what could be done quickly with Java
> and a well
> designed 3D library. Without the web deployability, we would have
> had to
> send them the Processing system and wrap it into an application,
> hoping it
> would work on their systems. We've tried this before and it was
> such a
> burden, we gave up the system that required we do that (Repast, the
> ABM
> system).
>
> If Groovy can't build applets, it will face huge problems
> attempting to
> define itself as a seamless Java/Agile system.
Web deployability != applets.
It can be argued (and I would argue) that JNLP is what applets should
have been in the first place.
Note also that I said that writing *unsigned* applets in groovy does
not look feasible to me. Signed applets are a whole other issue.
John Wilson
The Wilson Partnership
web
http://www.wilson.co.ukblog
http://eek.ook.org---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
