Skip to main content
Jump to: navigation, search

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

< DSDP‎ | MTJ
Line 33: Line 33:
 
*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:'''  
<div style="border: 2px solid #8E87EB; padding: 6px;">
+
 
 
*There needs to be a run option for non-MidP projects
 
*There needs to be a run option for non-MidP projects
 
: '''Contributors:'''  
 
: '''Contributors:'''  
  
I believe this needs to be in the highest priority to bring parity to non-MIDP projects.
 
 
-- Kevin Horowitz
 
</div>
 
 
*Enhance build mechanism to manage resources
 
*Enhance build mechanism to manage resources
 
: '''Contributors:'''  
 
: '''Contributors:'''  
Line 51: Line 47:
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 
: '''Use Cases:''' [[Device Fragmentation]]
 
: '''Use Cases:''' [[Device Fragmentation]]
 
 
<div style="border: 2px solid #8E87EB; padding: 6px;">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.
 
 
 
<strike>
 
'''Visual Designers'''
 
*LCDUI
 
*eSWT
 
</strike>
 
 
-- Kevin Horowitz</div>
 
  
  
Line 72: Line 56:
  
 
*Enable external obfuscator plug-ins
 
*Enable external obfuscator plug-ins
 
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
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.
 
  
  
Line 87: Line 67:
 
Prioritize SDK Matches for automated solution
 
Prioritize SDK Matches for automated solution
  
-- Kevin Horowitz
 
</div>
 
  
  
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
 
====mtj.project Static Information====
 
====mtj.project Static Information====
  
Line 100: Line 77:
 
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.
 
   
 
   
-- Moved to higher priority. 
 
  
-- Kevin Horowitz
 
</div>
 
  
  
Line 133: Line 107:
  
  
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
 
====Visual Designers====
 
====Visual Designers====
  
Line 143: Line 116:
 
*eSWT
 
*eSWT
  
-- Copied down to here
 
  
-- Kevin Horowitz
 
</div>
 
 
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
I believe this is very important to our usability.
 
  
  
Line 161: Line 127:
 
*Provide a way to import a midlet into an existing project
 
*Provide a way to import a midlet into an existing project
  
-- Kevin Horowitz
 
</div>
 
  
  
'''Mobile JUnit'''
+
 
 +
====Mobile JUnit====
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
Line 201: Line 166:
 
*Tool tip
 
*Tool tip
 
*Coding tips
 
*Coding tips
 
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
I believe this needs to be in the high priority item because we now have inconsistent data between a project and the runtimes.
 
 
<strike>
 
mtj.project has static information.  It should have references to device information instead of local copies.
 
</strike>
 
 
-- Kevin Horowitz
 
</div>
 
  
  
Line 220: Line 174:
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
<strike>
 
*There needs to be a run option for non-MidP projects
 
</strike>
 
I believe this needs to be in the highest priority to bring parity to non-MIDP projects.
 
 
-- Kevin Horowitz
 
 
</div>
 
 
*There is a dirty bit on deploy projects to say they are out-of-date but it is not being used
 
*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
 
*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
 
*Enhance launch/debug framework to enable launch/debug on remote device in a simplistic manner
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
 
* Provide an OTA method to launch
 
* Provide an OTA method to launch
  
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.
 +
 
  
-- Kevin Horowitz
 
</div>
 
  
  
 
===LOW PRIORITY===
 
===LOW PRIORITY===
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
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.
 
<strike>
 
 
 
====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
 
</strike>
 
 
-- Kevin Horowitz
 
</div>
 
  
  
Line 274: Line 202:
  
 
*Provide a way to import a combination of a jar and jad and create a new project from the result
 
*Provide a way to import a combination of a jar and jad and create a new project from the result
 
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
I believe this is very important to our usability.
 
<strike>
 
Provide a way to import a midlet into an existing project
 
</strike>
 
 
-- Kevin Horowitz
 
</div>
 
  
  
Line 308: Line 226:
  
  
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
We need to add all of the Europa requirements to this list.
 
  
-- Kevin Horowitz
 
  
'''Europa requirements'''
+
====Europa requirements====
 
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
 
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
 
-- Rauno Seppälä
 
</div>
 

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