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/Phone Meeting 08-Feb-2007"

< DSDP‎ | MTJ
 
Line 4: Line 4:
 
* Arto Laurila, Nokia  
 
* Arto Laurila, Nokia  
 
* Rauno Seppälä, Nokia
 
* Rauno Seppälä, Nokia
 +
* Stanley , Apogee
  
  
Line 29: Line 30:
 
===Content of M2===
 
===Content of M2===
  
What to include?
+
LCDUI
 +
 
 +
MTJ static info
 +
 
 +
Generic SDK
 +
 
 +
Support for multiple devices? (Check from Arto)
 +
 
  
  

Revision as of 10:10, 8 February 2007

Attendees

  • Craig Setera, EclipseME
  • Kevin Horowitz, IBM
  • Arto Laurila, Nokia
  • Rauno Seppälä, Nokia
  • Stanley , Apogee


Notes

some relevant notes from previous minutes left here, as they still apply


Schedule

Let's fill in Target Milestones to wiki Release 2 Planning in order to see the content for M2.


Status of feature list

No changes


Status of use cases

No Changes


Content of M2

LCDUI

MTJ static info

Generic SDK

Support for multiple devices? (Check from Arto)


Obfuscation

Localization

Fragmentation Core Services

Fragmentation Metadata Services

Generic SDK 3/4 done


Let's continue to plan via Release 2 Planning using Target Milestone field.


Fragmentation

Fragmentation requires some changes to JDT. Discussion how this could be handled.

  • EclipseME has done it in different way.
  • byte code onfly
  • not the best possible solution
  • Should be solved somehow, as others are able to do it: NetBeans, JMEPolish
  • JDT team is reluctant to make needed changes
  • MTJ proposal for preprocessing-JDT should be done
  • Where preproseccing touches: editor, debugger, compiler
  • Enough Software should be get into loop to discuss about the solution
  • Craig will reopen the bug report in Bugzilla


AOB

Next meeting

  • Next one on the 22nd of February, 2007


Action Points

OLD

AP: Arto to provide a summary of areas that he needs help, ONGOING
AP: Kevin to provide Use Cases. ONGOING
AP Rauno: Provide two weeks commenting time for UI and Flow Designer cases, then officially approve them. ONGOING:
This will continue as readabilty of wiki pages wasn't good enough.

Back to the top