Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Release 2 Planning Documents"

(minor update to add 3 new tasks. launch options and import existing midlet)
 
(6 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
*With needed features (to have “full” development environment)
 
*With needed features (to have “full” development environment)
 
*With needed documentation
 
*With needed documentation
 +
 +
==Priorities==
 +
Features have a priority High, Medium, Low and the following list has been sorted accordingly
  
 
==Content Proposal==
 
==Content Proposal==
  
 +
===HIGH PRIORITY===
 
Fixes and enhancements to R1
 
Fixes and enhancements to R1
 
*Finalize the APIs
 
*Finalize the APIs
Line 17: Line 21:
 
*Project based preferences
 
*Project based preferences
 
*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)
 +
<div style="border: 2px solid #8E87EB; padding: 6px;">
 +
*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
 +
</div>
 
*Enhance build mechanism to manage resources
 
*Enhance build mechanism to manage resources
 
*Bug fixes
 
*Bug fixes
  
−
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
 
  
−
Execution (Launch) Update
+
Device Fragmentation Solution
−
*There needs to be a run option for non-MidP projects
+
 
−
*There is a dirty bit on deploy projects to say they are out-of-date but it is not being used
+
<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.
−
*There needs to be a way to specify VM and Program arguments to the launch
+
  
 +
<strike>
 
Visual Designers
 
Visual Designers
 
*LCDUI
 
*LCDUI
 
*eSWT
 
*eSWT
 +
</strike>
  
−
Device Fragmentation Solution
+
-- Kevin Horowitz</div>
−
 
+
−
Support Multiple SDKs in a single project
+
−
(This is not part of the device fragmentation, but would be necessary to build a project with fragments) [[Image:New.png]]
+
  
 
Obfuscation
 
Obfuscation
 
*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.
 +
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
 +
</div>
 +
<div style="border: 2px solid #8E87EB; padding: 6px;">
 +
mtj.project has static information.  It should have references to device information instead of local copies.
 +
 +
-- Moved to higher priority. 
 +
 +
-- Kevin Horowitz
 +
</div>
 +
 +
===MEDIUM PRIORITY===
 +
  
 
New Profiles and configurations
 
New Profiles and configurations
Line 49: Line 74:
 
*MIDP 3.0 support (not included, but may come to the picture)
 
*MIDP 3.0 support (not included, but may come to the picture)
  
 +
 +
Support Multiple SDKs in a single project
 +
*this is not part of the device fragmentation, but would be necessary to build a project with fragments
 +
 +
<div style="border: 2px solid #8E87EB; padding: 6px;">
 +
Visual Designers
 +
*LCDUI
 +
*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.
 +
 +
Provide a way to import a midlet into an existing project
 +
 +
-- Kevin Horowitz
 +
</div>
 
Mobile JUnit
 
Mobile JUnit
 +
  
 
Localization (low)
 
Localization (low)
 
*Manage resources
 
*Manage resources
 
*Visual designer support
 
*Visual designer support
 +
  
 
Profiling
 
Profiling
 +
 +
 +
Help
 +
*F1 help
 +
*Tool tip
 +
*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>
 +
 +
Execution (Launch) Update
 +
<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 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
 +
<div style="border: 2px solid #8E87EB; padding: 6px;">
 +
* Provide an OTA method to launch
 +
 +
We have code from EclipseME and should enable it to provide an OTA launch.
 +
 +
-- Kevin Horowitz
 +
</div>
 +
 +
===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>
  
 
Migration from other IDEs  
 
Migration from other IDEs  
 +
  
 
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
 
Provide a way to import a midlet into an existing project
 +
</strike>
  
−
Features picked from rel. 0.7 list:
+
-- Kevin Horowitz
 +
</div>
  
−
Help [[Image:New.png]]
 
−
*F1 help
 
−
*Tool tip
 
−
*Coding tips
 
  
−
Update the system [[Image:New.png]]
 
−
* What is this?
 
  
−
Create Web Services stubs  
+
Create Web Services stubs
 +
 
 +
 
 +
Convert Audio
  
−
Convert Audio
 
  
 
Provide a migration path from 0.7 to 1.0
 
Provide a migration path from 0.7 to 1.0
  
−
mtj.project has static information.  It should have references to device information instead of local copies.
+
<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_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
 +
 
 +
-- Rauno Seppälä
 +
</div>

Latest revision as of 04:03, 21 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, Low and the following list has been sorted accordingly

Content Proposal

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

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

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

  • 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

  • this is not part of the device fragmentation, but would be necessary to build a project with fragments

Visual Designers

  • LCDUI
  • eSWT

-- Copied down to here

-- Kevin Horowitz

I believe this is very important to our usability.

Provide a way to import a midlet into an existing project

-- Kevin Horowitz

Mobile JUnit


Localization (low)

  • Manage resources
  • Visual designer support


Profiling


Help

  • 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

  • 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


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


Convert Audio


Provide a migration path from 0.7 to 1.0

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

-- Kevin Horowitz

Europa requirements: Europa Simultaneous Release

-- Rauno Seppälä

Retrieved from "https://wiki.eclipse.org/index.php?title=Release_2_Planning_Documents&oldid=18013"

This page was last modified 04:03, 21 November 2006 by Rauno Seppala. Based on work by Kevin Horowitz.

Back to the top