Jump to: navigation, search

Difference between revisions of "DSDP/MTJ/Discussion/Refactoring/EP"

< DSDP‎ | MTJ‎ | Discussion‎ | Refactoring
Line 11: Line 11:
 
* '''org.eclipse.mtj.ui.venderSpecJADAttributes'''
 
* '''org.eclipse.mtj.ui.venderSpecJADAttributes'''
 
* '''org.eclipse.mtj.ui.jadEditorPages'''
 
* '''org.eclipse.mtj.ui.jadEditorPages'''
 +
  
 
== Refactory Suggestions ==
 
== Refactory Suggestions ==

Revision as of 09:18, 29 January 2009

We currently have the following list of Extension points:

  • org.eclipse.mtj.core.api
    • Representation of an Java ME application programming interface (API).
  • org.eclipse.mtj.core.configurations
    • Extension that provides a listing of supported Java ME Configurations.
  • org.eclipse.mtj.core.deviceImporter
  • org.eclipse.mtj.core.library.MIDletLibrary
  • org.eclipse.mtj.core.profiles
  • org.eclipse.me.ui.deviceEditor
  • org.eclipse.mtj.ui.venderSpecJADAttributes
  • org.eclipse.mtj.ui.jadEditorPages


Refactory Suggestions

   org.eclipse.mtj.core.api 
    * Are we the only ones that implements this E.P?
    * Is it really necessary? since the UEI standard provides a way to gather the APIs from a SDK's device
    * The skeletonFile element is not used anymore