Skip to main content
Jump to: navigation, search

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

< DSDP‎ | MTJ
(Added proposed schedule from meeting minutes. Updated IBM contributions.)
Line 1: Line 1:
 +
<!-- Valid use case status is
 +
      1) Proposed
 +
      2) Outlined
 +
      3) Approved
 +
      4) Design  (not available, but planned)
 +
      5) ????
 +
-->
 +
 
==Target==
 
==Target==
 
*Version 1.0
 
*Version 1.0
Line 32: Line 40:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
*Support for non UEI SDKs (user provides the information for any platform that is not already defined)
 
*Support for non UEI SDKs (user provides the information for any platform that is not already defined)
: '''Contributors:'''  
+
: '''Contributors:''' IBM
  
 
*There needs to be a run option for non-MidP projects
 
*There needs to be a run option for non-MidP projects
Line 46: Line 54:
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Contributors:'''  
 
: '''Contributors:'''  
: '''Use Cases:''' [[Device Fragmentation]]
+
: '''Status of Use Cases:''' Proposed, Outlined
  
  
Line 61: Line 69:
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' IBM
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
Line 72: Line 80:
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' IBM
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
Line 229: Line 237:
 
Görkem Ercan
 
Görkem Ercan
 
eRCP project lead.
 
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.)

Revision as of 16:56, 13 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: IBM
  • 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:
Status of Use Cases: Proposed, Outlined


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: IBM
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: IBM
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.


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.)

Back to the top