My favorites | Sign in
Project Home Downloads Wiki Issues
READ-ONLY: This project has been archived. For more information see this post.
Search
for
PlatformDifferences  
Any differences between platform.
Phase-Requirements, Phase-Design, Phase-Implementation
Updated Nov 21, 2011 by jackokring

Programming Code in the API

There should be no difference. The configuration of the tool to include the right version of the library API is the most complex piece of distribution, and is best served by a template project for SE, which exports a jar file excluding the library API jar [jarvar.jar]. This can then be supported by some other template projects which make an auto-starting ME or Android project, given the SE exported jar with no API library, is used as a library within these secondary platform compilations. These templates may then be customized.

This will allow later platform development from the minimal SE jar, and the built-in ClassPath of the NSPlugin or jarvar cli/gui tool. An SE loader tool may also be useful, which sets the right ClassPath and starts any Process objects. Due to the way unused classes are not used, any platforms jar or apk should work with the SE or cli/gui tool. I think a lot depends on MANIFEST compatibility, and the use of non-platform manifest entries.

I see it as potentially being, a runner app for SE (with an unused ME manifest entry from the general [appME.jar], and unused ME Foundation API classes, as the Java runtime jre/lib/ext directory can contain [jarvar.jar]). This would make a general ME compile work on both ME and SE. I'm not sure about how easy it would be to make a jar file handler for Android which unpacks the jar, and merges it with [javarAn.jar] to make an apk which auto installs. Running [appME.jar] on the jarvar cli/gui tool would also not use the ME classes, and so no error would be triggered, to ask for a ClassPath, cascading class loading to all possible references, could even eliminate the ME classes from the jvr intermediate file. Maybe development on an ME compiler is best then, giving a feel of the limited scope interface first.

Files of the Library API (speculative)

  • [javar.jar] - SE platform javar API library (install once)
  • [javarME.jar] - ME platform jarvar API library (can be included in distro)
  • [javar.apk] - Android platform jarvar API library (install once)
  • [jarvar.c] - Plugin and cli/gui tool (compile and install once)

Ant should be capable of building maximal platform files, i.e. a .apk and an ME.jar, but maybe a jar runner on android should run the ME.jar version, and just replace the used classes via the reflection mechanism and a ClassLoader in Android. This could reduce the distributable to one format and a faster local format. The ME version and the intermediate jarvar cli/gui tool output version in a .jvr file. Ummmm....

Maybe http://www.netmite.com/android/ is Useful

Maybe me4se.jar is Useful

An SE dependence on the sixlegs PNG library is likely (stripped for readonly?)

Powered by Google Project Hosting