Skip to main content
Jump to: navigation, search

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

< DSDP‎ | MTJ
Line 10: Line 10:
  
 
== Use Cases ==
 
== Use Cases ==
Use Cases are here: '''[[DSDP-MTJ Use Cases]]'''
+
All Use Cases are here: '''[[DSDP-MTJ Use Cases]]'''  
  
 
==Content of Release 2==
 
==Content of Release 2==

Revision as of 08:17, 24 November 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: DSDP-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:

I believe this needs to be in the highest priority to bring parity to non-MIDP projects.

-- Kevin Horowitz

  • Enhance build mechanism to manage resources
Contributors:
  • Bug fixes
Contributors:


Device Fragmentation Solution

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


I believe that the Visual Designers are actually a lower priority for our developers right now. Especially the LCDUI editor. Even if we might complete this before some higher priority items for individual reasons, this should be a lower priority for the project.


Visual Designers

  • LCDUI
  • eSWT

-- Kevin Horowitz


Obfuscation

Status of Use Cases: Proposed, Outlined
Contributors: Nokia
Use Cases: Obfuscate the code
  • Enable external obfuscator plug-ins


I believe this is very important to our usability. This will allow general users access to our product when a custom SDK has not been created. This should help adoption of our product.


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

-- Kevin Horowitz


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.

-- Moved to higher priority.

-- Kevin Horowitz


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

-- Copied down to here

-- Kevin Horowitz


I believe this is very important to our usability.


Import MIDlets into the project

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

-- Kevin Horowitz


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


I believe this needs to be in the high priority item because we now have inconsistent data between a project and the runtimes.

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

-- Kevin Horowitz


Execution (Launch) Update

Status of Use Cases:
Contributors:
Use Cases:

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

I believe this needs to be in the highest priority to bring parity to non-MIDP projects.

-- Kevin Horowitz

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

-- Kevin Horowitz


LOW PRIORITY

I believe this is very important to our usability. This will allow general users access to our product when a custom SDK has not been created. This should help adoption of our product.


Create Generic SDK Interface

(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

-- Kevin Horowitz


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


I believe this is very important to our usability. Provide a way to import a midlet into an existing project

-- Kevin Horowitz


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:


We need to add all of the Europa requirements to this list.

-- Kevin Horowitz

Europa requirements Europa Simultaneous Release

-- Rauno Seppälä

Back to the top