DSDP/MTJ/Release 2 Planning

From Eclipsepedia

< DSDP‎ | MTJ
Jump to: navigation, search


Contents

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:
Target Milestone:
  • Declare internal code
  • Declare Public/Supported APIs
  • Enhance documentation
Contributors:
Target Milestone:
  • User Documentation
  • Developer Documentation
  • API Documentation
  • Project based preferences
Contributors:
Target Milestone:
  • Support for non UEI SDKs (user provides the information for any platform that is not already defined)
Contributors: IBM
Target Milestone: M2 Implemented in Create Generic SDK Interface
  • Enable external obfuscator plug-ins
  • Enhance build mechanism to manage resources
Contributors:
Target Milestone:
  • Bug fixes
Target Milestone:
Contributors:

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

Status of Use Cases: Proposed, Outlined
Contributors: IBM
Target Milestone: M3
Use Cases: Java ME Launch Mechanism
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639

Device Fragmentation Solution

Status of Use Cases: Proposed, Outlined
Contributors:
Target Milestone:
Use Cases: Device Fragmentation

Obfuscation

Status of Use Cases: Proposed, Outlined
Contributors: Nokia
Target Milestone: M1
Use Cases: Obfuscate the code



Create Generic SDK Interface

Status of Use Cases:
Contributors: IBM
Target Milestone: M2
Use Cases: User Defined SDK Use Case
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=175137

(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: Nokia (code) IBM (use case)
Target Milestone: M2
Use Cases: Link to Device Platform Data


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

Even though this has been reported as completed, this does not work. You can delete an SDK entry or edit it, and the project does not see the changes. Created new bugzilla to address failure.

Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=192190



MEDIUM PRIORITY

New Profiles and configurations

Contributors: Kevin Horowitz
Additional Information Additional Information
Target Milestone: M4
Use Cases: N/A
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=183837 (Foundation Hello World)
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639 (Run for Non MIDP failure)
  • MIDP 2.1 support - Changes required to support the JAD entry MIDP-2.1. Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=191785
  • MIDP 3.0 support (not included)
  • Foundation Profile (Sample, Working with SDK Definition)
  • Personal Profile (no AWT visual editor) (Sample, Working with SDK Definition)
  • Personal Basis Profile (Working with SDK Definition)
  • CDC (Are there working emulators?) Yes. There are methods supported to execute an application on a desktop machine.

Support Multiple SDKs in a single project

Status of Use Cases:
Contributors: Nokia
Target Milestone: M4
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 (LCDUI). Nokia, SVGT use cases during March-April
Target Milestone: M2 LCDUI
Use Cases: Visual Designers
  • LCDUI
  • SVGT Graphics Support

Import MIDlets into the project

Status of Use Cases:
Contributors: Nokia
Target Milestone: M4
Use Cases:
  • Provide a way to import a midlet into an existing project

Mobile JUnit

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Localization

Status of Use Cases: Proposed, Outlined
Contributors: Nokia, intial use cases
Target Milestone:
Use Cases: Localization
  • low
  • Manage resources
  • Visual designer support


Profiling

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Help

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:
  • F1 help
  • Tool tip
  • Coding tips


Execution (Launch) Update

Status of Use Cases:
Contributors:
Target Milestone:
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

Visual Designers

Status of Use Cases: Proposed, Outlined
Contributors: Nokia, intial use cases
Target Milestone:
Use Cases: Visual Designers
  • eSWT


Migration from other IDEs

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:

Import JARs & JADs to create a new project

Status of Use Cases:
Contributors:
Target Milestone:
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:
Target Milestone:
Use Cases:


Convert Audio

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Provide a migration path from 0.7 to 1.0

Status of Use Cases:
Contributors:
Target Milestone:
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.


Proposed Schedule

M1 31 Jan. 2007
M2 28 Feb. 2007
M3 30 Mar. 2007
M4 30 Apr. 2007
M5 31 May 2007
RC1 29 Jun. 2007
RC2 31 July 2007
Release 3Q 2007 (Expected in Sept.)