xmlvm-users — For current and interested XMLVM users, for public discussions and anouncements.

[xmlvm-users] Using OpenJDK classes instead of built-in stubs

[Barry L. <bar...@ao...>]

 

When I run:

  java -jar xmlvm.jar --in=myapp.jar --target=iphone-c --app-name=MyApp

I wind up with with my nicely converted code, but there's only the minimal set of core java classes, all of which appear to be hand-written. One thing my app uses that is completely missing from the generated code is java.util.TreeMap.

Should these missing classes be automatically converted from the classes in openjdk6-build.jar? I read something on the mailing list that suggested that this was going to happen, but it doesn't seem to be happening now.

If not, is there a way I can generate the classes from openjdk6-build.jar as part of my project? If not, is this a planned feature for the near future? Or is this something that is supported by the "iphone" target but not the "iphone-c" target yet?

Re: [xmlvm-users] Missing uiresponderdelegate.h and mailinglist archives

[Linus B. <li...@br...>]

Hi!

Thanks for the quick reply and for straightening out about skeletons.

Regarding my YUResponderDelegate: I do have latest trunk. I also tried
cleaning and rebuilding, but the problem remains.

br

/Linus

On Wed, Sep 29, 2010 at 10:25 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

>
> On Sep 29, 2010, at 10:55 AM, Linus Brimstedt wrote:
>
> > Hello,
> >
> > I've created a simple android app with a button and a WebView, it works
> on android emulator and in real phones.
> > After converting to xcode project i get error when compiling in xcode:
> > org_xmlvm_iphone_UIResponderDelegate.h: No such file or directory.
> >
> > I don't indeed have this file, but there is a corresponding class file.
> >
> > Any clues?
>
> Make sure you are using the latest XMLVM sources
>
>
> >
> > On the new google-site docs there is reference to
> skeleton=android:migrate, but my xmlvm seems only to accept skeleton=iphone?
> Is this something not yet implemented, or something that is now removed? :)
> >
> > best regard
> >
> > /linus
>
>
> Neither of these :)
> The patch is still pending, this is a "feature under development".
> It is implemented, but you have to wait a bit until you see it in the XMLVM
> source tree
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] Missing uiresponderdelegate.h and mailinglist archives

[Panayotis K. <pan...@pa...>]

On Sep 29, 2010, at 10:55 AM, Linus Brimstedt wrote:

> Hello,
> 
> I've created a simple android app with a button and a WebView, it works on android emulator and in real phones.
> After converting to xcode project i get error when compiling in xcode:
> org_xmlvm_iphone_UIResponderDelegate.h: No such file or directory.
> 
> I don't indeed have this file, but there is a corresponding class file.
> 
> Any clues?

Make sure you are using the latest XMLVM sources


> 
> On the new google-site docs there is reference to skeleton=android:migrate, but my xmlvm seems only to accept skeleton=iphone? Is this something not yet implemented, or something that is now removed? :)
> 
> best regard
> 
> /linus


Neither of these :)
The patch is still pending, this is a "feature under development".
It is implemented, but you have to wait a bit until you see it in the XMLVM source tree

[xmlvm-users] Missing uiresponderdelegate.h and mailinglist archives

[Linus B. <li...@br...>]

Hello,

I've created a simple android app with a button and a WebView, it works on
android emulator and in real phones.
After converting to xcode project i get error when compiling in xcode:
org_xmlvm_iphone_UIResponderDelegate.h: No such file or directory.

I don't indeed have this file, but there is a corresponding class file.

Any clues?

On the new google-site docs there is reference to skeleton=android:migrate,
but my xmlvm seems only to accept skeleton=iphone? Is this something not yet
implemented, or something that is now removed? :)

best regard

/linus

[xmlvm-users] Mobile Cross Platform Development Survey

[Daniel v. d. H. <mo...@da...>]

Dear all, 

I carry out a survey of (cross platform) development of mobile applications for smartphones within the scope of my diploma thesis. I would be very thankful if you, as mobile developers, have approx. 15-20 minutes to answer the questions. Of course, your information will be treated confidentially and stored anonymously. If you want I will let you know the results of the survey after the evaluation.

Link to the survey: http://www.daniel-von-der-helm.com/umfrage/index.php?sid=87643&lang=en


Thank you very much for your time & support!

Kind regards
Daniel von der Helm

Re: [xmlvm-users] Problem with demo Android projects

[Sascha H. <sa...@xm...>]

Sure, try the second approach and see how it works. Switching it around in
case it's not optimal should be easy.

// Sascha

2010/9/23 Panayotis Katsaloulis <pan...@pa...>

> On 23 Σεπ 2010, at 11:41 π.μ., Sascha Haeberling wrote:
>
> > Well, one of the things we will need to do for the cross-compilation of
> Android projects is to add the Android SDK. We can do this two ways: Either
> we put it  into a JAR, just like the OpenJDK JAR or we assume the developer
> has Android installed and use an environment flag to point to the classes.
> >
> > The advantage of the latter is that we don't blow up the size of our
> repository and one-jar further and I guess we can assume that every dev has
> Android installed.
>
>
> These are my exact thoughts.
> In the beginning I was towards the first solution, but now I am more in
> favor of the second, even if compilation of Android demos with XMLVM will
> not be "out of the box", and some manual tuning of XMLVM config files should
> be required (and will be documented).
>
> If you agree, I can go on with the second approach :)
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] Problem with demo Android projects

[Panayotis K. <pan...@pa...>]

On 23 Σεπ 2010, at 11:41 π.μ., Sascha Haeberling wrote:

> Well, one of the things we will need to do for the cross-compilation of Android projects is to add the Android SDK. We can do this two ways: Either we put it  into a JAR, just like the OpenJDK JAR or we assume the developer has Android installed and use an environment flag to point to the classes.
> 
> The advantage of the latter is that we don't blow up the size of our repository and one-jar further and I guess we can assume that every dev has Android installed.


These are my exact thoughts.
In the beginning I was towards the first solution, but now I am more in favor of the second, even if compilation of Android demos with XMLVM will not be "out of the box", and some manual tuning of XMLVM config files should be required (and will be documented).

If you agree, I can go on with the second approach :)

Re: [xmlvm-users] Problem with demo Android projects

[Sascha H. <sa...@xm...>]

Well, one of the things we will need to do for the cross-compilation of
Android projects is to add the Android SDK. We can do this two ways: Either
we put it  into a JAR, just like the OpenJDK JAR or we assume the developer
has Android installed and use an environment flag to point to the classes.

The advantage of the latter is that we don't blow up the size of our
repository and one-jar further and I guess we can assume that every dev has
Android installed.

// Sascha

On Thu, Sep 23, 2010 at 10:17 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

> On 23 Σεπ 2010, at 4:22 π.μ., Arno Puder wrote:
>
> >
> > you will have to explain that a little more in detail. The demos that
> > are shipped with XMLVM are proper Android projects. They were created
> > with the Android plugin for Eclipse (which is officially released by
> > Google). In Eclipse, you can import xmlvm/demo/android/xokoban and you
> > will see a proper Android project in your workspace. The location of the
> > Android SDK is configured with the Eclipse plugin.
> >
> > XMLVM needs to compile .class files (not .dex files) to do its thing.
> > So, the build.xml for that can be independent of the Android SDK.
> >
> > What exactly is the problem?
> >
> > Arno
>
>
> Exactly that is the problem, it is only usable under Eclipse and not on the
> command line.
> The problem with the command line is that the Android SDK should be defined
> somewhere.
>
> If we want to use the exact build options as with Android projects (as
> discussed in a previous email with android libraries), the Android SDK
> should be present.
>
> I have thought of this problem and I think I found an alternative approach.
> The first time the user requests the Android based demos to be compiled -
> and the location of the Android SDK was not provided to the XMLVM system -
> an error will appear and the compilation will abort. When the user will
> define the location, the compilation could go on as usual.
>
> Again, this has to do with the demo XMLVM Android projects. This will not
> alter in any case the regular xmlvm usage from the command line.
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] Problem with demo Android projects

[Panayotis K. <pan...@pa...>]

On 23 Σεπ 2010, at 4:22 π.μ., Arno Puder wrote:

> 
> you will have to explain that a little more in detail. The demos that 
> are shipped with XMLVM are proper Android projects. They were created 
> with the Android plugin for Eclipse (which is officially released by 
> Google). In Eclipse, you can import xmlvm/demo/android/xokoban and you 
> will see a proper Android project in your workspace. The location of the 
> Android SDK is configured with the Eclipse plugin.
> 
> XMLVM needs to compile .class files (not .dex files) to do its thing. 
> So, the build.xml for that can be independent of the Android SDK.
> 
> What exactly is the problem?
> 
> Arno


Exactly that is the problem, it is only usable under Eclipse and not on the command line.
The problem with the command line is that the Android SDK should be defined somewhere.

If we want to use the exact build options as with Android projects (as discussed in a previous email with android libraries), the Android SDK should be present.

I have thought of this problem and I think I found an alternative approach. The first time the user requests the Android based demos to be compiled - and the location of the Android SDK was not provided to the XMLVM system - an error will appear and the compilation will abort. When the user will define the location, the compilation could go on as usual.

Again, this has to do with the demo XMLVM Android projects. This will not alter in any case the regular xmlvm usage from the command line.

Re: [xmlvm-users] Problem with demo Android projects

[Arno P. <ar...@pu...>]

you will have to explain that a little more in detail. The demos that 
are shipped with XMLVM are proper Android projects. They were created 
with the Android plugin for Eclipse (which is officially released by 
Google). In Eclipse, you can import xmlvm/demo/android/xokoban and you 
will see a proper Android project in your workspace. The location of the 
Android SDK is configured with the Eclipse plugin.

XMLVM needs to compile .class files (not .dex files) to do its thing. 
So, the build.xml for that can be independent of the Android SDK.

What exactly is the problem?

Arno


On 9/22/10 12:51 AM, Panayotis Katsaloulis wrote:
> MOTIVATION
> Since I am creating a patch which makes demo iPhone projects self-contained (and easy to be copied and manipulated), I was thinking to do the same with Android projects. Thus everybody could have a real "demo" case, and not only a "proof of concept", with difficult assumptions on how to migrate an existing project to Android.
>
>
> STATUS OF THE ART
> The currently demo projects of XMLVM are not "full" android projects, i.e. not being created by the "android create project" command.
> They can only be used from inside Eclipse and not with Google tools which handle Android projects.
> For this reason you have written special ant tasks in the base build.xml file, to overcome this problem.
>
>
> THE PROBLEM
> ... is that an Android project should specifically define an Android SDK location for the Google-provided build scripts to work.
> But this can change from system to system, and specifically be defined in a local.properties file, which should not be committed to the SVN
>
> MY PROPOSAL
> ... is, like in the case of OpenJDK, to include the absolute minimum requirements from the Android project to the XMLVM project. Thus the demo Android projects will be "full", self-contained and "ready to be copied" Android projects.
> And it will be dead-easy to run these tests in the Android Emulator itself.
>
> What do you think?
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] Problem with demo Android projects

[Panayotis K. <pan...@pa...>]

MOTIVATION
Since I am creating a patch which makes demo iPhone projects self-contained (and easy to be copied and manipulated), I was thinking to do the same with Android projects. Thus everybody could have a real "demo" case, and not only a "proof of concept", with difficult assumptions on how to migrate an existing project to Android. 


STATUS OF THE ART
The currently demo projects of XMLVM are not "full" android projects, i.e. not being created by the "android create project" command.
They can only be used from inside Eclipse and not with Google tools which handle Android projects.
For this reason you have written special ant tasks in the base build.xml file, to overcome this problem.


THE PROBLEM
... is that an Android project should specifically define an Android SDK location for the Google-provided build scripts to work.
But this can change from system to system, and specifically be defined in a local.properties file, which should not be committed to the SVN

MY PROPOSAL
... is, like in the case of OpenJDK, to include the absolute minimum requirements from the Android project to the XMLVM project. Thus the demo Android projects will be "full", self-contained and "ready to be copied" Android projects.
And it will be dead-easy to run these tests in the Android Emulator itself.

What do you think?

Re: [xmlvm-users] Running Examples

[Ben K. <be...@no...>]

> > Hi,
> >
> > This is probably the most inane question you've been asked, but how do
> > you run the example apps purely with java?
> >
> > I was able to compile XMLVM with ant, and run the examples from within
> > Eclipse, I can even run xmlvm (using java -jar xmlvm) perfectly fine,
> > but when running the examples I get the following error:
> >
> > D:\Users\Ben\workspace\xmlvm\dist\demo\iphone\ifireworks\java>java -jar
> > ifireworks.jar
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/xmlvm/demo/ifireworks/Main
> > Caused by: java.lang.ClassNotFoundException:
org.xmlvm.demo.ifireworks.Main
> >        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> >        at java.security.AccessController.doPrivileged(Native Method)
> >        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> >        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> > Could not find the main class: org.xmlvm.demo.ifireworks.Main. Program
> > will exit.
> >
> > I couldn't really find anything in the manual (and it just says to use
> > java -jar). I'm obviously missing something fundamental.
> >
> > I'd be thankful for any help.
> >
> > Regards,
> > Ben

> I suspect it has to do with windows path separator "\"
> Unfortunately I can't help you more than that :(

Looks like that was what it was. I updated the manifest file and made
the path relative (and fixing /) and it appears to work. Doesn't run
yet, but I'm closer:

Exception in thread "main" java.lang.Error: Unresolved compilation problem:

        at org.xmlvm.iphone.UIApplication.main(UIApplication.java:117)
        at org.xmlvm.demo.ifireworks.Main.main(Main.java:56)

Something's gone wrong there anyway. I notice that the Eclipse launch
file doesn't actually use the ant-built jar files, so I might just try
compiling them myself.

Thanks for the pointer.
Ben

Re: [xmlvm-users] Running Examples

[Leo I. <leo...@gm...>]

In the manifest file, packages are supposed to be separated by dots (.) not
slashes (/).

On Mon, Sep 20, 2010 at 4:47 AM, Panayotis Katsaloulis <
pan...@pa...> wrote:

> On 19 Σεπ 2010, at 7:33 μ.μ., Ben Kirk wrote:
>
> > Hi,
> >
> > This is probably the most inane question you've been asked, but how do
> > you run the example apps purely with java?
> >
> > I was able to compile XMLVM with ant, and run the examples from within
> > Eclipse, I can even run xmlvm (using java -jar xmlvm) perfectly fine,
> > but when running the examples I get the following error:
> >
> > D:\Users\Ben\workspace\xmlvm\dist\demo\iphone\ifireworks\java>java -jar
> > ifireworks.jar
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/xmlvm/demo/ifireworks/Main
> > Caused by: java.lang.ClassNotFoundException:
> org.xmlvm.demo.ifireworks.Main
> >        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> >        at java.security.AccessController.doPrivileged(Native Method)
> >        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> >        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> > Could not find the main class: org.xmlvm.demo.ifireworks.Main. Program
> > will exit.
> >
> > I couldn't really find anything in the manual (and it just says to use
> > java -jar). I'm obviously missing something fundamental.
> >
> > I'd be thankful for any help.
> >
> > Regards,
> > Ben
>
>
> I suspect it has to do with windows path separator "\"
> Unfortunately I can't help you more than that :(
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] XMLVM android-compat.jar vs. android.target.classpath

[Arno P. <ar...@pu...>]

+1 from my side as well.

Arno


On 9/19/10 9:01 AM, Wolfgang Korn wrote:
> I go for the third option - because it is the safest one.
>
> -- Wolfgang
>
> Am 19.09.2010 17:56 schrieb "Panayotis Katsaloulis"
> <pan...@pa... <mailto:pan...@pa...>>:
>  > Hello all!
>  >
>  > I am in the process of automating the integration of XMLVM into an
> Android project.
>  > But I found a problem and I would like to discuss with you the
> possible solutions.
>  >
>  > The problem is with the android libraries, which come from two
> sources: one from the XMLVM project (which will emulate Android on an
> iPhone) and second, the actual bootstrap libraries of a genuine Android
> device.
>  > Although they are more or less the same, they are not "exactly" the same.
>  >
>  > The source code of a project could be compiled perfectly with both
> libraries. The produced class files though will (probably) be a bit
> different. This can be demonstrated even in the case of the "aFireworks"
> project.
>  > So, in order to work perfectly with both environments, I can see
> these scenarios and I'd like you to say your opinion, on what to implement:
>  >
>  > a) Use only android bootstrap libraries. That means that the xmlvm
> android library should be API-perfect, or else compilation on the ObjC
> part will fail.
>  >
>  > b) Compile with XMLVM libraries and use these classes for both ObjC
> project *and* Android emulation. As long as the XMLVM library is more or
> less compatible with the official android bootstrap, this will work.
> But, in the case that something is binary incompatible, the application
> on the Android device will crash for no obvious reason.
>  >
>  > c) Compile the ObjC code with the xmlvm libraries, and the Android
> emulator project with the Android bootstrap files. So every time the
> project is rebuilt, the produced classes should be cleaned and re-generated.
>  >
>  >
>  > I am more in favor of the third approach, although it is not the most
> optimized, but because it is the safest. There will be a penalty for
> compilation, but I think it is not so important, compared with the benefits.
>  >
>  >
>  > Before implementing anything though, I'd love to hear your thoughts...
>  >
> ------------------------------------------------------------------------------
>  > Start uncovering the many advantages of virtual appliances
>  > and start using them to simplify application deployment and
>  > accelerate your shift to cloud computing.
>  > http://p.sf.net/sfu/novell-sfdev2dev
>  > _______________________________________________
>  > xmlvm-users mailing list
>  > xml...@li...
> <mailto:xml...@li...>
>  > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] Running Examples

[Panayotis K. <pan...@pa...>]

On 19 Σεπ 2010, at 7:33 μ.μ., Ben Kirk wrote:

> Hi,
> 
> This is probably the most inane question you've been asked, but how do
> you run the example apps purely with java?
> 
> I was able to compile XMLVM with ant, and run the examples from within
> Eclipse, I can even run xmlvm (using java -jar xmlvm) perfectly fine,
> but when running the examples I get the following error:
> 
> D:\Users\Ben\workspace\xmlvm\dist\demo\iphone\ifireworks\java>java -jar
> ifireworks.jar
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/xmlvm/demo/ifireworks/Main
> Caused by: java.lang.ClassNotFoundException: org.xmlvm.demo.ifireworks.Main
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> Could not find the main class: org.xmlvm.demo.ifireworks.Main. Program
> will exit.
> 
> I couldn't really find anything in the manual (and it just says to use
> java -jar). I'm obviously missing something fundamental.
> 
> I'd be thankful for any help.
> 
> Regards,
> Ben


I suspect it has to do with windows path separator "\"
Unfortunately I can't help you more than that :(

Re: [xmlvm-users] Does XMLVM work with iPhone simulator > 3.1?

[Thomas H. <hol...@gm...>]

Thanks for the hints!

I now was able to compile it in xcode. However, my app is using too much 
Android API classes that are not supported yet so it didn't compile 
without errors.

I will keep on following the project! Keep on good work!

Regards,
Thomas


Am 2010-09-14 23:44, schrieb Leo Izen:
> cannot find symbol for -lcrt1.10.5.o is a mistake apple made when 
> writing OS X leopard.
>
> On any other system, it looks for crt1.o. However, on Mac OS 10.5, 
> Apple made it look for crt1.*10.5*.o when compiling for Leopard, 
> because the default was to compile for 10.4, for increased 
> compatibility. This is fixed in 10.6 (Snow Leopard).
>
> To fix this yourself symbolically link crt1.10.5.o to crt1.o. I think 
> xmlvm is designed for Leopard, so it uses crt1.10.5.o instead of crt1.o.
>
> The symbol "undefined reference to main in -lcrt1.10.5.o" says that 
> you are not linking your project into the object file, or you don't 
> have a main function/method. The undefined reference in crt1.o is 
> defined by your main method. If you don't have a main method, then you 
> will get this error.
>
> On Tue, Sep 14, 2010 at 2:58 PM, Thomas Holzmann <hol...@gm... 
> <mailto:hol...@gm...>> wrote:
>
>     Hi,
>
>     I'm really like the idea of XMLVM and therefore wanted to try to
>     cross-compile one of my Android apps to iOS.
>
>     Everything workes fine until I have to execute the makefile. It says:
>
>     library not found for -lcrt1.10.5.o
>
>     I looked into the Makefile and found out that it is configured to
>     run on
>     iPhone simulator 3.1. I have the simulators 3.2, 4.0 and 4.1 installed
>     but not 3.1, so I tried to change it to 3.2 in the Makefile.
>     After that there was another error (undefined symbols in crt or
>     something like this). However, it also didn't work.
>
>     So is there a possibility to get XMLVM to work on newer simulators or
>     does it just work on 3.1 at the moment?
>
>     Thanks!
>
>     Regards,
>     Thomas
>
>
>
>     ------------------------------------------------------------------------------
>     Start uncovering the many advantages of virtual appliances
>     and start using them to simplify application deployment and
>     accelerate your shift to cloud computing.
>     http://p.sf.net/sfu/novell-sfdev2dev
>     _______________________________________________
>     xmlvm-users mailing list
>     xml...@li...
>     <mailto:xml...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>    

[xmlvm-users] Running Examples

[Ben K. <be...@no...>]

Hi,

This is probably the most inane question you've been asked, but how do
you run the example apps purely with java?

I was able to compile XMLVM with ant, and run the examples from within
Eclipse, I can even run xmlvm (using java -jar xmlvm) perfectly fine,
but when running the examples I get the following error:

D:\Users\Ben\workspace\xmlvm\dist\demo\iphone\ifireworks\java>java -jar
ifireworks.jar
Exception in thread "main" java.lang.NoClassDefFoundError:
org/xmlvm/demo/ifireworks/Main
Caused by: java.lang.ClassNotFoundException: org.xmlvm.demo.ifireworks.Main
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: org.xmlvm.demo.ifireworks.Main. Program
will exit.

I couldn't really find anything in the manual (and it just says to use
java -jar). I'm obviously missing something fundamental.

I'd be thankful for any help.

Regards,
Ben

Re: [xmlvm-users] XMLVM android-compat.jar vs. android.target.classpath

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

I go for the third option - because it is the safest one.

-- Wolfgang

Am 19.09.2010 17:56 schrieb "Panayotis Katsaloulis" <pan...@pa...
>:
> Hello all!
>
> I am in the process of automating the integration of XMLVM into an Android
project.
> But I found a problem and I would like to discuss with you the possible
solutions.
>
> The problem is with the android libraries, which come from two sources:
one from the XMLVM project (which will emulate Android on an iPhone) and
second, the actual bootstrap libraries of a genuine Android device.
> Although they are more or less the same, they are not "exactly" the same.
>
> The source code of a project could be compiled perfectly with both
libraries. The produced class files though will (probably) be a bit
different. This can be demonstrated even in the case of the "aFireworks"
project.
> So, in order to work perfectly with both environments, I can see these
scenarios and I'd like you to say your opinion, on what to implement:
>
> a) Use only android bootstrap libraries. That means that the xmlvm android
library should be API-perfect, or else compilation on the ObjC part will
fail.
>
> b) Compile with XMLVM libraries and use these classes for both ObjC
project *and* Android emulation. As long as the XMLVM library is more or
less compatible with the official android bootstrap, this will work. But, in
the case that something is binary incompatible, the application on the
Android device will crash for no obvious reason.
>
> c) Compile the ObjC code with the xmlvm libraries, and the Android
emulator project with the Android bootstrap files. So every time the project
is rebuilt, the produced classes should be cleaned and re-generated.
>
>
> I am more in favor of the third approach, although it is not the most
optimized, but because it is the safest. There will be a penalty for
compilation, but I think it is not so important, compared with the benefits.
>
>
> Before implementing anything though, I'd love to hear your thoughts...
>
------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] XMLVM android-compat.jar vs. android.target.classpath

[Panayotis K. <pan...@pa...>]

Hello all!

I am in the process of automating the integration of XMLVM into an Android project.
But I found a problem and I would like to discuss with you the possible solutions.

The problem is with the android libraries, which come from two sources: one from the XMLVM project (which will emulate Android on an iPhone) and second, the actual bootstrap libraries of a genuine Android device.  
Although they are more or less the same, they are not "exactly" the same.

The source code of a project could be compiled perfectly with both libraries. The produced class files though will (probably) be a bit different. This can be demonstrated even in the case of the "aFireworks" project.
So, in order to work perfectly with both environments, I can see these scenarios and I'd like you to say your opinion, on what to implement:

a) Use only android bootstrap libraries. That means that the xmlvm android library should be API-perfect, or else compilation on the ObjC part will fail.

b) Compile with XMLVM libraries and use these classes for both ObjC project *and* Android emulation. As long as the XMLVM library is more or less compatible with the official android bootstrap, this will work. But, in the case that something is binary incompatible, the application on the Android device will crash for no obvious reason.

c) Compile the ObjC code with the xmlvm libraries, and the Android emulator project with the Android bootstrap files. So every time the project is rebuilt, the produced classes should be cleaned and re-generated.


I am more in favor of the third approach, although it is not the most optimized, but because it is the safest. There will be a penalty for compilation, but I think it is not so important, compared with the benefits.


Before implementing anything though, I'd love to hear your thoughts...

Re: [xmlvm-users] Integrated Garbage Collector into C backend

[Sascha H. <sa...@gm...>]

Great work Joshua! This is indeed a great milestone.

// Sascha

On Sunday, September 19, 2010, Arno Puder <ar...@pu...> wrote:
>
> Guys,
>
> I just committed a patch submitted by Joshua Melcon that integrates the
> Boehm Garbage Collector (http://www.hpl.hp.com/personal/Hans_Boehm/gc/)
> into the C backend. The source code of the Boehm GC is automatically
> added to the generated Xcode project.
>
> Another big milestone for XMLVM! Thanks to Joshua for his great work!
>
> Arno
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] C backend GUI

[Arno P. <ar...@pu...>]

in principle, yes. We generate portable C code that should be compilable 
with any C compiler. You mentioned that you want to use AWT/Swing. I 
would imagine that AWT has a bunch of native methods for low-level 
drawing routines. You would need to implement those based on some GUI 
toolkit. Don't know how much work this would be, but certainly doable.

Arno


On 9/18/10 12:11 PM, Leo Izen wrote:
> I might want to turn my Java into C, not just for the iPhone the way it
> seems everyone out here wants. What would be a nice way to implement
> AWT/Swing would be to use the QT Library, that way it is possible for
> the C to be compileable under X (linux, Mac) and Windows. Would it be
> possible to do this? Thanx!
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

[xmlvm-users] Integrated Garbage Collector into C backend

[Arno P. <ar...@pu...>]

Guys,

I just committed a patch submitted by Joshua Melcon that integrates the 
Boehm Garbage Collector (http://www.hpl.hp.com/personal/Hans_Boehm/gc/) 
into the C backend. The source code of the Boehm GC is automatically 
added to the generated Xcode project.

Another big milestone for XMLVM! Thanks to Joshua for his great work!

Arno

[xmlvm-users] C backend GUI

[Leo I. <leo...@gm...>]

I might want to turn my Java into C, not just for the iPhone the way it
seems everyone out here wants. What would be a nice way to implement
AWT/Swing would be to use the QT Library, that way it is possible for the C
to be compileable under X (linux, Mac) and Windows. Would it be possible to
do this? Thanx!

Re: [xmlvm-users] OneJar and XMLVM

[Sascha H. <sa...@gm...>]

2010/9/18 Panayotis Katsaloulis <pan...@pa...>

> On 18 Σεπ 2010, at 3:01 μ.μ., Sascha Haeberling wrote:
>
> >
> > Actually no. Of course just showing the help dialog is the worst
> situation. But show me the numbers when compiling a whole project.
>
> No it's not the worst case scenario, since all files need to be extracted
> all the time. It is not the best, it's just an indication that it slows down
> things. Probably not with
>

I call it worst case, because the work XMLVM needs to do is minimal (just
printing some text), but still everything needs to be launched and
extracted. When XMLVM does "real" work, this boot-up time will be a big part
anymore.


>
> >
> > I don't think that extracting data from the OneJAR is a huge part in the
> whole process. Believe me, I care about speed just as much as you do. Last
> week I made some significant changes that speed up the compilation
> significantly. I was able to save minutes. If the OneJAR only adds 2 seconds
> to a cross-compilation, I would see it as rather insignificant. But of
> course, if there are clever ways to make the OneJAR faster, I am always for
> it,but I wouldn't abandon it.
>
> It still needs a lot of improvements and I have made some myself in the
> past. Still, as Josua said, this is a benefit only for the xmlvm developer,
> not user (the iphone developer).
>
> For an iPhone developer who compiles and saves a project 100s times, even a
> 2 second penalty is too much.
>
> Now, for an actual case scenario, in order to do it it needs to make
> changes to the xmlvm to perform it.
> If I make these changes, I prefer to submit it as a patch, instead of
> discussing here ;)
>

Well now you are digressing, this is not productive. We all use XMLVM
everyday on tasks and we see how long things take. As I said, I did some
benchmarking last week when I implemented quite a few speed improvements.
Most of these task would run for many seconds anyway, so 2 seconds don't
seem much. But please correct me, if I am wrong.

As a concrete example: I was corss-compiling half of the OpenJDK library,
which originally took about 5 minutes to do. After the improvements
I've submitted it came down to 1.5 minutes. 2 seconds are not
even noticeable in such a scenario.

What I want to say is this: If most usual "real" tasks have a duration of
many seconds, then making a change as drastic as "getting rid of OneJAR"
only to save a minimal barely noticeable speed improvements seems out of
proportion.

// Sascha


>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>

Re: [xmlvm-users] OneJar and XMLVM

[Panayotis K. <pan...@pa...>]

On 18 Σεπ 2010, at 3:01 μ.μ., Sascha Haeberling wrote:

> 
> Actually no. Of course just showing the help dialog is the worst situation. But show me the numbers when compiling a whole project.

No it's not the worst case scenario, since all files need to be extracted all the time. It is not the best, it's just an indication that it slows down things. Probably not with

> 
> I don't think that extracting data from the OneJAR is a huge part in the whole process. Believe me, I care about speed just as much as you do. Last week I made some significant changes that speed up the compilation significantly. I was able to save minutes. If the OneJAR only adds 2 seconds to a cross-compilation, I would see it as rather insignificant. But of course, if there are clever ways to make the OneJAR faster, I am always for it,but I wouldn't abandon it.

It still needs a lot of improvements and I have made some myself in the past. Still, as Josua said, this is a benefit only for the xmlvm developer, not user (the iphone developer).

For an iPhone developer who compiles and saves a project 100s times, even a 2 second penalty is too much.

Now, for an actual case scenario, in order to do it it needs to make changes to the xmlvm to perform it.
If I make these changes, I prefer to submit it as a patch, instead of discussing here ;)