Difference between revisions of "DSDP/MTJ/Release 2 Planning"

Revision as of 08:43, 8 December 2006

Target

• Version 1.0
• With needed quality
• With needed features (to have “full” development environment)
• With needed documentation

Priorities

Features have a priority High, Medium or Low and the following list has been sorted accordingly

Use Cases

All Use Cases are here: MTJ Use Cases

Content of Release 2

HIGH PRIORITY

Fixes and enhancements to 0.7

There will not be use cases for this category

• Finalize the APIs

Contributors:

• Declare internal code
• Declare Public/Supported APIs

• Enhance documentation

Contributors:

• User Documentation
• Developer Documentation
• API Documentation

• Project based preferences

Contributors:

• Support for non UEI SDKs (user provides the information for any platform that is not already defined)

Contributors:

• There needs to be a run option for non-MidP projects

Contributors:

• Enhance build mechanism to manage resources

Contributors:

• Bug fixes

Contributors:

Device Fragmentation Solution

Status of Use Cases: Proposed, Outlined

Contributors:

Use Cases: Device Fragmentation

Obfuscation

Status of Use Cases: Proposed, Outlined

Contributors: Nokia

Use Cases: Obfuscate the code

• Enable external obfuscator plug-ins

Create Generic SDK Interface

Status of Use Cases:

Contributors:

Use Cases:

(Define a generic SDK so that users can configure against something that has not been added by a vendor) Prioritize SDK Matches for automated solution

mtj.project Static Information

Status of Use Cases:

Contributors:

Use Cases:

mtj.project has static information. It should have references to device information instead of local copies.

MEDIUM PRIORITY

New Profiles and configurations

Status of Use Cases:

Contributors:

Use Cases:

• CDC
• Foundation Profile
• Personal Profile (no AWT visual editor)
• Personal Basis Profile
• MIDP 2.1 support
• MIDP 3.0 support (not included, but may come to the picture)

Support Multiple SDKs in a single project

Status of Use Cases:

Contributors:

Use Cases:

• this is not part of the device fragmentation, but would be necessary to build a project with fragments

Visual Designers

Status of Use Cases: Proposed, Outlined

Contributors: Nokia, intial use cases

Use Cases: Visual Designers

• LCDUI
• eSWT

Import MIDlets into the project

Status of Use Cases:

Contributors:

Use Cases:

• Provide a way to import a midlet into an existing project

Mobile JUnit

Status of Use Cases:

Contributors:

Use Cases:

Localization

Status of Use Cases: Proposed, Outlined

Contributors: Nokia, intial use cases

Use Cases: Localization

• low
• Manage resources
• Visual designer support

Profiling

Status of Use Cases:

Contributors:

Use Cases:

Help

Status of Use Cases:

Contributors:

Use Cases:

• F1 help
• Tool tip
• Coding tips

Execution (Launch) Update

Status of Use Cases:

Contributors:

Use Cases:

• There is a dirty bit on deploy projects to say they are out-of-date but it is not being used
• There needs to be a way to specify VM and Program arguments to the launch
• Enhance launch/debug framework to enable launch/debug on remote device in a simplistic manner
• Provide an OTA method to launch

• • We have code from EclipseME and should enable it to provide an OTA launch.

LOW PRIORITY

Migration from other IDEs

Status of Use Cases:

Contributors:

Use Cases:

Import JARs & JADs to create a new project

Status of Use Cases:

Contributors:

Use Cases:

• Provide a way to import a combination of a jar and jad and create a new project from the result

Create Web Services stubs

Status of Use Cases:

Contributors:

Use Cases:

Convert Audio

Status of Use Cases:

Contributors:

Use Cases:

Provide a migration path from 0.7 to 1.0

Status of Use Cases:

Contributors:

Use Cases:

Europa requirements

Europa Simultaneous Release

Future Wish List

eRCP Support

1. eRCP application project templates similar to RCP project templates. (Hello world eRCP application, eRCP application with a View etc.) [High priority]

2. Management of build path. eRCP applications are targeted for nothing but CDC, currently PDE(at least on 3.2) does not manage that only access to CDC is available even if the runtime supports java se 1.x. I guess the easiest way to have this would be adding access rules to runtime. [Hig Priority]

3. Exporting/packing eRCP applications for target mobile platforms: I am not sure how many platforms can be covered but I am thinking at least a framework that works nicely with PDE export to provide install packages like .sis files etc. [Medium priority] 4. Running eRCP applications on mobile emulators. By default PDE works only with the windows desktop implementation of eRCP, MTJ can extend PDE to provide run/debug support for eRCP applications on the emulator [Low priority]

Thanks, Görkem Ercan eRCP project lead.