The MIDP3.0 features are to be added in phases according to priority and available resource. The aim is to prioritise features needed most urgently by developers.
Provide a new LIBlet project wizard.
Provide support for basic attributes (ie name, vendor, version, Jar URL, etc)
Provide support for building, signing and export in line with the functionality already available for MIDlet projects.
At this stage, LIBlet jars can be built, and then manually added as External JARs on the build path of a MIDlet. There is no explicit editor support for adding LIBlet dependencies.
Both LIBlet and MIDlet projects can list their LIBlet dependencies.
Dependencies can be resolved either to Project dependencies or External Jar dependencies, and will then be automatically added to the build path.
TBD: decide whether or not to be able to add a LIBlet JAR as a resource of another project.
Provide editor and validator support for dependencies.
See plan.
Both MIDlet and LIBlet projects may have additional optional attributes as defined by MIDP3.0.
Implementation of these will be prioritised according to developer needs.
Priority classification of these attributes is on the MIDlet project extensions and LIBlet project pages.
See plan.
Provide explicit editor support for MIDP3.0-style parameterised permissions.
Provide an extension point for each JSR to implement permission string parsing and validation.
Implement validators for permissions associated with JSRs:
JSR271
JSR135
JSR82
TBD: others?
See plan.
Define and implement UEI extensions to support concurrency.
If necessary, define and implement UEI extensions to support idle-screen instantiation.
See plan.
Implement features de-prioritised from the other phases.
For example, editor support for localisation of MIDlet and LIBlet attributes may be de-prioritised.
See plan.