Re: [xmlvm-users] src/xmlvm2objc/compat-lib/objc vs. src/xmlvm2objc/compat-lib/java/org/xmlvm/iphone

[Wolfgang K. <wol...@xm...>]

Hi,

the explanation for that is pretty simple. XMLVM provides its own Java
based emulator which is basically a pure Java desktop application.
"Java-for-iPhone" applications use the Java classes if they are run on
XMLVM's emulator (without being cross-compiled). This is a great tool if
you have to debug your application because you are still in a Java-only
world. For that you can use the debugging tools of your choice and you
don't have to worry about Objective-C. If the application is cross
compiled the Java implementation of the classes you mentioned is not
needed. Instead the application is linked against the Objective-C
implementation which basically wraps the already existent Cocoa Touch
classes and provide the name-mangled API which gets called by all the
cross-compiled classes.

Does this answer your question?

-- Wolfgang



Tor Lillqvist wrote:
> Hi,
>
> Trying to understand xmlvm better (especially the Java on the iPhone
> aspect), I am a bit confused how the source code for what seems to be
> the same Java classes occurs both in src/xmlvm2objc/compat-lib/objc
> and in src/xmlvm2objc/compat-lib/java/org/xmlvm/iphone.
>
> Could somebody explain to me for instance which
> org.xmlvm.iphone.CGFont gets used, the one written in Java in
> src/xmlvm2objc/compat-lib/java/org/xmlvm/iphone/CGFont.java
> (eventually compiled to a class file and then translated by xmlvm to
> Objective-C) or the one written in Objective-C in
> src/xmlvm2objc/compat-lib/objc/org_xmlvm_iphone_CGFont.[hm] ?
>
> Or does the code for this class get "merged" from these two
> implementations, with just those parts that need to call Apple APIs
> written in Objective-C and the rest in Java? That would actually be
> quite elegant I guess.
>
> --tml
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>