From: Panayotis K. <pan...@pa...> - 2010-09-22 07:51:45
|
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? |