Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DSDP/MTJ/Release 2 Planning"
| Line 33: | Line 33: | ||
====Device Fragmentation Solution==== | ====Device Fragmentation Solution==== | ||
| − | : Status of Use Cases: Nokia Proposed, Outlined | + | : '''Status of Use Cases:''' Nokia Proposed, Outlined |
| − | : Contributors: | + | : '''Contributors:''' |
<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. | <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. | ||
| Line 50: | Line 50: | ||
====Obfuscation==== | ====Obfuscation==== | ||
| − | : Status of Use Cases: Nokia Proposed, Outlined | + | : '''Status of Use Cases:''' Nokia Proposed, Outlined |
| − | : Contributors: | + | : '''Contributors:''' |
*Enable external obfuscator plug-ins | *Enable external obfuscator plug-ins | ||
| Line 60: | Line 60: | ||
====Create Generic SDK Interface==== | ====Create Generic SDK Interface==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
(Define a generic SDK so that users can configure against something that has not been added by a vendor) | (Define a generic SDK so that users can configure against something that has not been added by a vendor) | ||
| Line 70: | Line 73: | ||
<div style="border: 2px solid #8E87EB; padding: 6px;"> | <div style="border: 2px solid #8E87EB; padding: 6px;"> | ||
====mtj.project Static Information==== | ====mtj.project Static Information==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
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 83: | Line 89: | ||
====New Profiles and configurations==== | ====New Profiles and configurations==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*CDC | *CDC | ||
*Foundation Profile | *Foundation Profile | ||
| Line 92: | Line 102: | ||
====Support Multiple SDKs in a single project==== | ====Support Multiple SDKs in a single project==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*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 97: | Line 111: | ||
<div style="border: 2px solid #8E87EB; padding: 6px;"> | <div style="border: 2px solid #8E87EB; padding: 6px;"> | ||
====Visual Designers==== | ====Visual Designers==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*LCDUI | *LCDUI | ||
*eSWT | *eSWT | ||
| Line 111: | Line 129: | ||
====Import MIDlets into the project==== | ====Import MIDlets into the project==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*Provide a way to import a midlet into an existing project | *Provide a way to import a midlet into an existing project | ||
| Line 118: | Line 140: | ||
'''Mobile JUnit''' | '''Mobile JUnit''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
====Localization==== | ====Localization==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*low | *low | ||
*Manage resources | *Manage resources | ||
| Line 127: | Line 157: | ||
====Profiling==== | ====Profiling==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
====Help==== | ====Help==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*F1 help | *F1 help | ||
*Tool tip | *Tool tip | ||
| Line 146: | Line 184: | ||
====Execution (Launch) Update==== | ====Execution (Launch) Update==== | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
<div style="border: 2px solid #8E87EB; padding: 6px;"> | <div style="border: 2px solid #8E87EB; padding: 6px;"> | ||
<strike> | <strike> | ||
| Line 185: | Line 227: | ||
'''Migration from other IDEs''' | '''Migration from other IDEs''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
'''Import JARs & JADs to create a new project''' | '''Import JARs & JADs to create a new project''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
*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;"> | <div style="border: 2px solid #8E87EB; padding: 6px;"> | ||
I believe this is very important to our usability. | I believe this is very important to our usability. | ||
| Line 200: | Line 252: | ||
'''Create Web Services stubs''' | '''Create Web Services stubs''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
| + | |||
'''Convert Audio''' | '''Convert Audio''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
'''Provide a migration path from 0.7 to 1.0''' | '''Provide a migration path from 0.7 to 1.0''' | ||
| + | |||
| + | : '''Status of Use Cases:''' | ||
| + | : '''Contributors:''' | ||
Revision as of 04:51, 24 November 2006
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, Low and the following list has been sorted accordingly
Content of Release 2
HIGH PRIORITY
Fixes and enhancements to R1
- Finalize the APIs
- Declare internal code
- Declare Public/Supported APIs
- Enhance documentation
- User Documentation
- Developer Documentation
- API Documentation
- Project based preferences
- Support for non UEI SDKs (user provides the information for any platform that is not already defined)
- 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
- Enhance build mechanism to manage resources
- Bug fixes
Device Fragmentation Solution
- Status of Use Cases: Nokia Proposed, Outlined
- Contributors:
Visual Designers
- LCDUI
- eSWT
-- Kevin Horowitz
Obfuscation
- Status of Use Cases: Nokia Proposed, Outlined
- Contributors:
- 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:
(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:
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:
- 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:
- this is not part of the device fragmentation, but would be necessary to build a project with fragments
Visual Designers
- Status of Use Cases:
- Contributors:
- 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:
- Provide a way to import a midlet into an existing project
-- Kevin Horowitz
Mobile JUnit
- Status of Use Cases:
- Contributors:
Localization
- Status of Use Cases:
- Contributors:
- low
- Manage resources
- Visual designer support
Profiling
- Status of Use Cases:
- Contributors:
Help
- Status of Use Cases:
- Contributors:
- 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:
- 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:
Import JARs & JADs to create a new project
- Status of Use Cases:
- Contributors:
- 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:
Convert Audio
- Status of Use Cases:
- Contributors:
Provide a migration path from 0.7 to 1.0
- Status of Use Cases:
- Contributors:
We need to add all of the Europa requirements to this list.
-- Kevin Horowitz
Europa requirements Europa Simultaneous Release
-- Rauno Seppälä