Hello Arno,
first of all thanks for your quick response!
to 1. I am aware that I can see the API in the locations you mentioned. I
asked that question with some written/detailed documentation in mind. But I
guess the official Android/iOS documentations will be ok.
to 2. I know that your API doesn't feature all the Cocoa classes and I am
sure that your API is correct. What I really wanted to know was if the
classes themselves are complete, meaning that for example your WebView
implementation features ALL the methods the UIWebView class has.
to 3. Nice
to 4. In my case it is very important that I can send http requests and
handle either json or xml responses. Is that possible with your current API?
to 5. My question could've been more specific ;) But I didn't have anything
too specific in mind. It was more about common feautures like networking,
local data storage (e.g. SQLite) that can't be done with xmlvm.
Markus
2011/5/17 Arno Puder <ar...@pu...>
>
>
> On 5/17/11 12:35 AM, Markus Balsam wrote:
> > 1. Is there any type of documentation available for the android/cocoa
> > compatibilty libs (javadoc or something)
>
> You can see the Cocoa Touch API that XMLVM supports in
> xmlvm/src/xmlvm2objc/compat-lib/java. Similarly, the Android API
> supported by XMLVM can be found in xmlvm/src/android2iphone.
>
> > 2. Is the featured subset of classes in the cocoa lib complete, i.e. do
> > those classes offer the same functionality as their objective-c
> > counterparts (that would make it possible to consult the apple docs for
> > reference)?
>
> You mix completeness with correctness. XMLVM implements the Cocoa Touch
> API correctly (which is to say, you can consult the Apple documentation)
> but we are not complete. However, the most important API is present.
>
> > 3. Are there any limitations with respect to event handling (especially
> > touch/swipe etc.)?
>
> No.
>
> > 4. Is it possible to use the 3rd party libraries shipping with Android
> > (apache http, json etc.)? If not, is there any other way of dealing with
> > networking or parsing json/xml etc.?
>
> In theory, yes. We are migrating to the new C backend. It is much more
> complete than the old Objective-C backend. E.g., we can cross-compile
> Apache Harmony for complete J2SE compliance with the C backend (which
> cannot be done with the Objective-C backend).
>
> > 5. Are there any other limitations?
>
> Probably many, but you have to be specific. XMLVM is Open Source and
> lives by contributions made by volunteers. We always welcome patches to
> push the envelope with XMLVM.
>
> Arno
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
|
