James Williams wrote:
> Another problem other than the classloaders is all the reflection
> classes that Groovy needs to compile(most reside in rt.jar). I think the
> only way to get Groovy working would be to rip out all the dynamic
> classes and MOP. The result would be a language that is not really Groovy.
Yeah, Android is actually a whole lot like GWT in terms of how it works
in relation to Java. So Groovy as we know it currently isn't practical.
But that points to something a bit different that is possible which is
targeting Android from GWT so that a GWT-powered webapp could easily
have an Android version.
There have been some folks trying to use Groovy and GWT together.
http://docs.codehaus.org/display/GRAILS/GWT+Pluginhttp://blogs.pathf.com/agileajax/gwt/index.htmlhttp://www.ayokasystems.com/googlewebtoolkit.htmlJim
> On Jan 23, 2008 11:37 AM, tugwilson <
tug@...
> <mailto:
tug@...>> wrote:
>
> Tahir Akhtar wrote:
> >
> > Hi,
> > I found this through google.
> >
>
http://www.jameswilliams.be/blog/entry/38;jsessionid=7711F31E5A4CE248E63009221DFE6117> >
> > Someone got a better solution?
> >
>
> As i understand it, the Android JVM does not use the normal JVM
> bytecodes.
> There is a preprocessor which converts class files produced by the Java
> compiler into the format used by Android (the Android bytecodes use a
> register rather than a stack architecture).
> ...
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
