Skip to main content
Jump to: navigation, search

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

< DSDP‎ | MTJ
Line 76: Line 76:
  
 
mtj.project has static information.  It should have references to device information instead of local copies.
 
mtj.project has static information.  It should have references to device information instead of local copies.
 
 
  
  
Line 102: Line 100:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
 
*this is not part of the device fragmentation, but would be necessary to build a project with fragments
 
*this is not part of the device fragmentation, but would be necessary to build a project with fragments
Line 115: Line 112:
 
*LCDUI
 
*LCDUI
 
*eSWT
 
*eSWT
 
 
  
  
Line 126: Line 121:
  
 
*Provide a way to import a midlet into an existing project
 
*Provide a way to import a midlet into an existing project
 
 
  
  
Line 135: Line 128:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''
 
: '''Use Cases:'''
 
  
  
Line 154: Line 146:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
  
Line 180: Line 171:
  
 
**We have code from EclipseME and should enable it to provide an OTA launch.
 
**We have code from EclipseME and should enable it to provide an OTA launch.
 
 
  
  
Line 192: Line 181:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
  
Line 209: Line 197:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
  
Line 224: Line 211:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
 
  
  
 
====Europa requirements====
 
====Europa requirements====
 
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
 
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]

Revision as of 09:52, 7 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
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:
Contributors:
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

Back to the top