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 "DSDP/MTJ/Release 2 Planning"

< DSDP‎ | MTJ
 
Line 32: Line 32:
  
  
−
'''Device Fragmentation Solution'''
+
====Device Fragmentation Solution====
 
: Status of Use Cases: Nokia Proposed, Outlined
 
: Status of Use Cases: Nokia Proposed, Outlined
 
: Contributors:  
 
: Contributors:  
Line 48: Line 48:
  
  
−
'''Obfuscation'''
+
====Obfuscation====
  
 
: Status of Use Cases: Nokia Proposed, Outlined
 
: Status of Use Cases: Nokia Proposed, Outlined
Line 59: Line 59:
  
  
−
'''Create Generic SDK Interface'''
+
====Create Generic SDK Interface====
  
 
(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 66: Line 66:
 
-- Kevin Horowitz
 
-- Kevin Horowitz
 
</div>
 
</div>
−
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
  
  
−
'''mtj.project Static Information'''
+
<div style="border: 2px solid #8E87EB; padding: 6px;">
 +
====mtj.project Static Information====
  
 
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 77: Line 77:
 
-- Kevin Horowitz
 
-- Kevin Horowitz
 
</div>
 
</div>
 +
  
 
===MEDIUM PRIORITY===
 
===MEDIUM PRIORITY===
  
  
−
'''New Profiles and configurations'''
+
====New Profiles and configurations====
 
*CDC
 
*CDC
 
*Foundation Profile
 
*Foundation Profile
Line 90: Line 91:
  
  
−
'''Support Multiple SDKs in a single project'''
+
====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
 
*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;">
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
−
'''Visual Designers'''
+
====Visual Designers====
 
*LCDUI
 
*LCDUI
 
*eSWT
 
*eSWT
Line 103: Line 104:
 
-- Kevin Horowitz
 
-- Kevin Horowitz
 
</div>
 
</div>
 +
  
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
Line 108: Line 110:
  
  
−
'''Import MIDlets into the project'''
+
====Import MIDlets into the project====
 
*Provide a way to import a midlet into an existing project
 
*Provide a way to import a midlet into an existing project
  
 
-- Kevin Horowitz
 
-- Kevin Horowitz
 
</div>
 
</div>
 +
 +
 
'''Mobile JUnit'''
 
'''Mobile JUnit'''
  
  
−
'''Localization''' (low)
+
====Localization====
 +
*low
 
*Manage resources
 
*Manage resources
 
*Visual designer support
 
*Visual designer support
  
  
−
'''Profiling'''
+
====Profiling====
  
  
−
'''Help'''
+
====Help====
 
*F1 help
 
*F1 help
 
*Tool tip
 
*Tool tip
Line 140: Line 145:
  
  
−
'''Execution (Launch) Update'''
+
====Execution (Launch) Update====
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
<div style="border: 2px solid #8E87EB; padding: 6px;">
 
<strike>
 
<strike>

Revision as of 04:47, 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, 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:
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: 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

(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

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.


Import MIDlets into the project

  • 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


Import JARs & JADs to create a new project

  • 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=DSDP/MTJ/Release_2_Planning&oldid=18512"

Back to the top