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
 
(43 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
<!-- Valid use case status is
 +
      1) Proposed
 +
      2) Outlined
 +
      3) Approved
 +
      4) Design  (not available, but planned)
 +
      5) ????
 +
-->
 +
 
==Target==
 
==Target==
 
*Version 1.0
 
*Version 1.0
Line 10: Line 18:
  
 
== Use Cases ==
 
== Use Cases ==
All Use Cases are here: '''[[DSDP-MTJ Use Cases]]'''  
+
All Use Cases are here: '''[[DSDP-MTJ Use Cases|MTJ Use Cases]]'''  
  
 
==Content of Release 2==
 
==Content of Release 2==
Line 22: Line 30:
 
*Finalize the APIs
 
*Finalize the APIs
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
:* Declare internal code
 
:* Declare internal code
 
:* Declare Public/Supported APIs
 
:* Declare Public/Supported APIs
 
*Enhance documentation
 
*Enhance documentation
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
:* User Documentation
 
:* User Documentation
 
:* Developer Documentation
 
:* Developer Documentation
Line 31: Line 41:
 
*Project based preferences
 
*Project based preferences
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
*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:''' IBM
<div style="border: 2px solid #8E87EB; padding: 6px;">
+
: '''Target Milestone: ''' M2 Implemented in [[Release_2_Planning#Create Generic SDK Interface|Create Generic SDK Interface]]
*There needs to be a run option for non-MidP projects
+
*Enable external obfuscator plug-ins
: '''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:'''  
 +
: '''Target Milestone: '''
 
*Bug fixes
 
*Bug fixes
 +
: '''Target Milestone: '''
 
: '''Contributors:'''  
 
: '''Contributors:'''  
  
 +
====There needs to be a run option for non-MidP projects====
 +
: '''Status of Use Cases:''' Proposed, Outlined
 +
: '''Contributors:''' IBM
 +
: '''Target Milestone: ''' M3
 +
: '''Use Cases:''' [[DSDP/MTJ/JavaME_launch_mechanism | Java ME Launch Mechanism]]
 +
: '''Bugzilla Entry:''' [https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639 https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639 ]
  
 
====Device Fragmentation Solution====
 
====Device Fragmentation Solution====
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''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>
 
 
  
 
====Obfuscation====
 
====Obfuscation====
Line 69: Line 70:
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Contributors:''' Nokia
 
: '''Contributors:''' Nokia
 +
: '''Target Milestone: '''M1
 
: '''Use Cases:''' [[Obfuscate the code]]
 
: '''Use Cases:''' [[Obfuscate the code]]
  
*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 81: Line 79:
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' IBM
: '''Use Cases:'''  
+
: '''Target Milestone: '''M2
 +
: '''Use Cases:''' [[DSDP/MTJ/GENERIC_SDK_DEFINITION | User Defined SDK Use Case]]
 +
: '''Bugzilla Entry:''' [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175137 https://bugs.eclipse.org/bugs/show_bug.cgi?id=175137 ]
  
 
(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)
 
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====
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' Nokia (code) IBM (use case)
: '''Use Cases:'''  
+
: '''Target Milestone: '''M2
 +
: '''Use Cases:''' [[DSDP/MTJ/mtj_project_static_data | Link to Device Platform Data]]
 +
 
  
 
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
+
Even though this has been reported as completed, this does not work.  You can delete an SDK entry or edit it, and the project does not see the changes.  Created new bugzilla to address failure.
</div>
+
: '''Bugzilla Entry:''' https://bugs.eclipse.org/bugs/show_bug.cgi?id=192190
  
 +
 +
----
  
 
===MEDIUM PRIORITY===
 
===MEDIUM PRIORITY===
Line 111: Line 108:
 
====New Profiles and configurations====
 
====New Profiles and configurations====
  
: '''Status of Use Cases:'''  
+
: '''Contributors:''' Kevin Horowitz
: '''Contributors:'''  
+
: '''Additional Information''' [[DSDP/MTJ/New_Profiles_Information | Additional Information]]
: '''Use Cases:'''  
+
: '''Target Milestone: '''M4
 
+
: '''Use Cases:''' N/A
*CDC
+
: '''Bugzilla Entry:''' https://bugs.eclipse.org/bugs/show_bug.cgi?id=183837 (Foundation Hello World)
*Foundation Profile
+
: '''Bugzilla Entry:''' https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639 (Run for Non MIDP failure)
*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)
+
  
 +
*MIDP 2.1 support - Changes required to support the JAD entry MIDP-2.1.  '''Bugzilla Entry:''' https://bugs.eclipse.org/bugs/show_bug.cgi?id=191785
 +
*MIDP 3.0 support (not included)
 +
*Foundation Profile (Sample, Working with SDK Definition)
 +
*Personal Profile (no AWT visual editor) (Sample, Working with SDK Definition)
 +
*Personal Basis Profile (Working with SDK Definition)
 +
*CDC (Are there working emulators?) Yes.  There are methods supported to execute an application on a desktop machine.
  
 
====Support Multiple SDKs in a single project====
 
====Support Multiple SDKs in a single project====
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' Nokia
 +
: '''Target Milestone: ''' M4
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
 
*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;">
 
 
====Visual Designers====
 
====Visual Designers====
  
 
: '''Status of Use Cases:''' Proposed, Outlined
 
: '''Status of Use Cases:''' Proposed, Outlined
: '''Contributors:''' Nokia
+
: '''Contributors:''' Nokia, intial use cases (LCDUI). Nokia, SVGT use cases during March-April
 +
: '''Target Milestone: '''M2 LCDUI
 
: '''Use Cases:''' [[Visual Designers]]
 
: '''Use Cases:''' [[Visual Designers]]
  
 
*LCDUI
 
*LCDUI
*eSWT
+
*SVGT Graphics Support
 
+
-- Copied down to here
+
 
+
-- Kevin Horowitz
+
</div>
+
 
+
 
+
<div style="border: 2px solid #8E87EB; padding: 6px;">
+
I believe this is very important to our usability.
+
 
+
  
 
====Import MIDlets into the project====
 
====Import MIDlets into the project====
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
: '''Contributors:'''  
+
: '''Contributors:''' Nokia
 +
: '''Target Milestone: ''' M4
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
 
*Provide a way to import a midlet into an existing project
 
*Provide a way to import a midlet into an existing project
  
-- Kevin Horowitz
+
====Mobile JUnit====
</div>
+
 
+
 
+
'''Mobile JUnit'''
+
  
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''
 
: '''Use Cases:'''
 
  
  
 
====Localization====
 
====Localization====
  
: '''Status of Use Cases:'''  
+
: '''Status of Use Cases:''' Proposed, Outlined
: '''Contributors:'''  
+
: '''Contributors:''' Nokia, intial use cases
 +
: '''Target Milestone: '''
 
: '''Use Cases:''' [[Localization]]
 
: '''Use Cases:''' [[Localization]]
  
Line 188: Line 174:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
  
Line 196: Line 182:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
Line 201: Line 188:
 
*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 218: Line 194:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''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>
 
  
 +
====Visual Designers====
  
====Create Generic SDK Interface====
+
: '''Status of Use Cases:''' Proposed, Outlined
 +
: '''Contributors:''' Nokia, intial use cases
 +
: '''Target Milestone: '''
 +
: '''Use Cases:''' [[Visual Designers]]
  
 
+
*eSWT
(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 263: Line 222:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
: '''Use Cases:'''  
+
: '''Target Milestone: '''
 
+
: '''Use Cases:'''
 
+
  
 
====Import JARs & JADs to create a new project====
 
====Import JARs & JADs to create a new project====
Line 271: Line 229:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
 
*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 290: Line 239:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
 
  
  
Line 298: Line 247:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
Line 305: Line 255:
 
: '''Status of Use Cases:'''  
 
: '''Status of Use Cases:'''  
 
: '''Contributors:'''  
 
: '''Contributors:'''  
 +
: '''Target Milestone: '''
 
: '''Use Cases:'''  
 
: '''Use Cases:'''  
  
  
<div style="border: 2px solid #8E87EB; padding: 6px;">
+
====Europa requirements====
We need to add all of the Europa requirements to this list.
+
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
  
-- Kevin Horowitz
 
  
'''Europa requirements'''
+
==Future Wish List==
[[Europa_Simultaneous_Release#Requirements_For_Participation|Europa Simultaneous Release]]
+
 
 +
===eRCP Support===
 +
 
 +
1. eRCP application project templates similar to RCP project templates.
 +
(Hello world eRCP application, eRCP application with a View etc.) [High priority]
 +
 
 +
2. Management of build path. eRCP applications are targeted for nothing but CDC, currently PDE(at least on 3.2) does not manage that only access to CDC is available even if the runtime supports java se 1.x. I guess the easiest way to have this would be adding access rules to runtime. [Hig Priority]
 +
 
 +
3. Exporting/packing eRCP applications for target mobile platforms: I am not sure how many platforms can be covered but I am thinking at least a framework that works nicely with PDE export to provide install packages like .sis files etc.  [Medium priority] 4. Running eRCP applications on mobile emulators. By default PDE works only with the windows desktop implementation of eRCP, MTJ can extend PDE to provide run/debug support for eRCP applications on the emulator [Low priority]
 +
 
 +
Thanks,
 +
Görkem Ercan
 +
eRCP project lead.
 +
 
 +
 
 +
== Proposed Schedule ==
 +
:M1  31 Jan. 2007
 +
 
 +
:M2  28 Feb. 2007
 +
 
 +
:M3  30 Mar. 2007
 +
 
 +
:M4  30 Apr. 2007
 +
 
 +
:M5  31 May  2007
 +
 
 +
:RC1 29 Jun. 2007
 +
 
 +
:RC2 31 July 2007
  
-- Rauno Seppälä
+
:Release 3Q 2007 (Expected in Sept.)
</div>
+

Latest revision as of 12:28, 27 May 2008


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:
Target Milestone:
  • Declare internal code
  • Declare Public/Supported APIs
  • Enhance documentation
Contributors:
Target Milestone:
  • User Documentation
  • Developer Documentation
  • API Documentation
  • Project based preferences
Contributors:
Target Milestone:
  • Support for non UEI SDKs (user provides the information for any platform that is not already defined)
Contributors: IBM
Target Milestone: M2 Implemented in Create Generic SDK Interface
  • Enable external obfuscator plug-ins
  • Enhance build mechanism to manage resources
Contributors:
Target Milestone:
  • Bug fixes
Target Milestone:
Contributors:

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

Status of Use Cases: Proposed, Outlined
Contributors: IBM
Target Milestone: M3
Use Cases: Java ME Launch Mechanism
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639

Device Fragmentation Solution

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

Obfuscation

Status of Use Cases: Proposed, Outlined
Contributors: Nokia
Target Milestone: M1
Use Cases: Obfuscate the code



Create Generic SDK Interface

Status of Use Cases:
Contributors: IBM
Target Milestone: M2
Use Cases: User Defined SDK Use Case
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=175137

(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: Nokia (code) IBM (use case)
Target Milestone: M2
Use Cases: Link to Device Platform Data


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

Even though this has been reported as completed, this does not work. You can delete an SDK entry or edit it, and the project does not see the changes. Created new bugzilla to address failure.

Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=192190



MEDIUM PRIORITY

New Profiles and configurations

Contributors: Kevin Horowitz
Additional Information Additional Information
Target Milestone: M4
Use Cases: N/A
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=183837 (Foundation Hello World)
Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=177639 (Run for Non MIDP failure)
  • MIDP 2.1 support - Changes required to support the JAD entry MIDP-2.1. Bugzilla Entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=191785
  • MIDP 3.0 support (not included)
  • Foundation Profile (Sample, Working with SDK Definition)
  • Personal Profile (no AWT visual editor) (Sample, Working with SDK Definition)
  • Personal Basis Profile (Working with SDK Definition)
  • CDC (Are there working emulators?) Yes. There are methods supported to execute an application on a desktop machine.

Support Multiple SDKs in a single project

Status of Use Cases:
Contributors: Nokia
Target Milestone: M4
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, intial use cases (LCDUI). Nokia, SVGT use cases during March-April
Target Milestone: M2 LCDUI
Use Cases: Visual Designers
  • LCDUI
  • SVGT Graphics Support

Import MIDlets into the project

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

Mobile JUnit

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Localization

Status of Use Cases: Proposed, Outlined
Contributors: Nokia, intial use cases
Target Milestone:
Use Cases: Localization
  • low
  • Manage resources
  • Visual designer support


Profiling

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Help

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:
  • F1 help
  • Tool tip
  • Coding tips


Execution (Launch) Update

Status of Use Cases:
Contributors:
Target Milestone:
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

Visual Designers

Status of Use Cases: Proposed, Outlined
Contributors: Nokia, intial use cases
Target Milestone:
Use Cases: Visual Designers
  • eSWT


Migration from other IDEs

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:

Import JARs & JADs to create a new project

Status of Use Cases:
Contributors:
Target Milestone:
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:
Target Milestone:
Use Cases:


Convert Audio

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Provide a migration path from 0.7 to 1.0

Status of Use Cases:
Contributors:
Target Milestone:
Use Cases:


Europa requirements

Europa Simultaneous Release


Future Wish List

eRCP Support

1. eRCP application project templates similar to RCP project templates. (Hello world eRCP application, eRCP application with a View etc.) [High priority]

2. Management of build path. eRCP applications are targeted for nothing but CDC, currently PDE(at least on 3.2) does not manage that only access to CDC is available even if the runtime supports java se 1.x. I guess the easiest way to have this would be adding access rules to runtime. [Hig Priority]

3. Exporting/packing eRCP applications for target mobile platforms: I am not sure how many platforms can be covered but I am thinking at least a framework that works nicely with PDE export to provide install packages like .sis files etc. [Medium priority] 4. Running eRCP applications on mobile emulators. By default PDE works only with the windows desktop implementation of eRCP, MTJ can extend PDE to provide run/debug support for eRCP applications on the emulator [Low priority]

Thanks, Görkem Ercan eRCP project lead.


Proposed Schedule

M1 31 Jan. 2007
M2 28 Feb. 2007
M3 30 Mar. 2007
M4 30 Apr. 2007
M5 31 May 2007
RC1 29 Jun. 2007
RC2 31 July 2007
Release 3Q 2007 (Expected in Sept.)

Back to the top