Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Status of Use Cases"
| Line 21: | Line 21: | ||
'''Visual Designers''': Nokia Proposed, Outlined. Nokia participates to development. | '''Visual Designers''': Nokia Proposed, Outlined. Nokia participates to development. | ||
| − | + | ---- | |
===Medium Priority=== | ===Medium Priority=== | ||
| Line 49: | Line 49: | ||
'''Execution (Launch) Update''': | '''Execution (Launch) Update''': | ||
| − | + | ---- | |
===Low Priority=== | ===Low Priority=== | ||
Revision as of 06:31, 17 November 2006
Status of MTJ rel. 1.0 Use Cases
High Priority
Fixes and enhancements to 0.7
- Finalize the APIs
- Enhance documentation
- Project based preferences
- Support for non UEI SDKs
- Enhance build mechanism to manage resources
- Bug fixes
Device Fragmentation: Nokia Proposed, Outlined
Obfuscate the code: Nokia to provide proposal. Nokia participates to development.
Visual Designers: Nokia Proposed, Outlined. Nokia participates to development.
Medium Priority
New Profiles and configurations:
Support Multiple SDKs in a project:
Mobile JUnit:
Localization: Nokia to provide proposal. Nokia participates to development.
Profiling:
Help:
mtj.project Static Information:
Execution (Launch) Update:
Low Priority
Create Generic SDK Interface:
Migration from other IDEs :
Create Web Services stubs:
Convert Audio:
Migration path from 0.7 to 1.0:
Provide a way to import a combination of a jar and jad and create a new project from the result
Provide a way to import a midlet into an existing project
Back to DSDP-MTJ Use Cases