pde-ui-home/main.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.40, Tue Mar 1 04:26:18 2005 UTC revision 1.41, Tue Aug 23 22:46:59 2005 UTC
# Line 74  Line 74 
74    <tr>    <tr>
75      <td>      <td>
76    
77  <h4> <a name="Milestone_Planning"></a> 3.1 Development Effort - Milestone 2  <h4> <a name="Milestone_Planning"></a> 3.2 Development Effort - Milestone 2
78  (September 24, 2004)</h4>  (September 24, 2004)</h4>
79    
80  <ul>  <ul>
81  <li>Rich Client Platform<ul>  <li>Rich Client Platform<ul>
82  <li>Enhance the New Plug-in Project Creation wizard to allow the creation of a  <li>Enhance the New Plug-in Project Creation wizard to allow the creation of a
83  minimal, ready-to-run rich client application</li>  headless rich client application.</li>
84  <li>Rename 'Runtime Workbench' launcher to 'Eclipse Application'.</li>  <li>Provide a Hello World headless RCP template.</li>
85  <li>Introduce the concept of a 'Plug-ins' working set, and add shortcuts to  <li>Add Intro support to the RCP Product editor.</li>
 these working sets on the Target Platform preference page and the Plug-ins tab  
 of the launchers.</li>  
 <li>Add a validation button to the Plug-ins tab of the launcher to validate&nbsp; the list of plug-ins chosen by the  
 user on-demand and report any problems with the plug-in selection prior to  
 launching.</li>  
   
 <li>Make the Eclipse application launch context menus sensitive to the selected  
 project to launch the correct application with the correct subset of plugins.</li>  
   
 </ul>  
 </li>  
 <li>Other<ul>  
 <li>Reduce the defect backlog.</li>  
 <li>Implement small feature requests from Bugzilla.</li>  
   
 </ul>  
 </li>  
   
 <li>Conference in Germany</li>  
 <li>Vacation</li>  
   
 </ul>  
     <p><font size="3"><b>3.1 Development Effort - Milestone 3 (Nov 05, 2004)</b></font></p>  
   
 <ul>  
 <li>Add support for the plug-in in JAR format&nbsp;&nbsp; (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=58658">bug  
 58658</a>)&nbsp;&nbsp; (Deferred from Milestone 2)&nbsp; <ul>  
 <li>The PDE state/parser must recognize such plug-ins in the target platform.</li>  
 <li>Modify the classpath/source attachment computation algorithm to account for  
 the new format.</li>  
 <li>Add support in the plug-in import wizard to handle this format.</li>  
 <li>Add an option in the export wizard to build plug-ins in this format.</li>  
 <li>Revisit all search/open actions acting on external plug-ins.</li>  
 <li>The Plug-ins view must be able to render this new plug-in layout.</li>  
   
 </ul>  
 </li>  
 <li>Rich Client Platform<ul>  
 <li>Rework the configuration tab of the launcher to allow the launch of an  
 Eclipse application using a template config.ini. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=72274">bug  
 72274</a>)</li>  
   
 </ul>  
     </li>  
 <li>Classpath computation<ul>  
 <li>Introduce a new extension point to expose plug-in javadoc (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=52894">bug  
 52894</a>)</li>  
86    
87  </ul>  </ul>
88      </li>      </li>
89  <li>Plug-in Manifest Validation<ul>  <li>Runtime/OSGi<ul>
90  <li>Fix the problem with flagging errors correctly but at the wrong line numbers  <li>Enhance the New Plug-in Project Creation wizard to allow the creation of a
91  that is due to imprecise parsers. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59681">bug  pure OSGi bundle that is not dependent on the runtime layer.</li>
92  59681</a>)</li>  <li>Implement an OSGi Application launcher.</li>
93    
94  </ul>  </ul>
95      </li>      </li>
 <li>Plug-in Search<ul>  
 <li>Migrate to the new search infrastructure (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59999">bug  
 59999</a>)</li>  
96    
97  </ul>  <li>An Integrated IDE<ul>
98      </li>  <li>Plug-in working sets should participate in builds, view filtering, searches.</li>
99  <li>Testing<ul>  <li>Participate in refactoring (manifest.mf, plugin.xml and fragment.xml files).</li>
 <li>Add &gt;= 1 JUnit test(s)</li>  
 <li>Add &gt;= 1 performance test(s).</li>  
100    
101  </ul>  </ul>
102      </li>      </li>
103  <li>Other<ul>  <li>Eclipse Application launcher<ul>
104  <li>Reduce the defect backlog.</li>  <li>Make the launch configurations portable.</li>
105    <li>Make the launcher tabs and the runner configuration API.</li>
106    
107  </ul>  </ul>
108      </li>      </li>
109    
110  </ul>  </ul>
     <p><font size="3"><b>3.1 Development Effort - Milestone 4 (Dec 17, 2004)</b></font></p>  
 <ul>  
   <li>Performance<ul>  
     <li>Cache the state for the target platform for faster population of PDE  
     models upon restart</li>  
     <li>Take some of the load off the runtime and its -clean argument when  
     self-hosting by generating manifest.mf files for workspace plug-ins upon  
     launching.</li>  
     <li>Identify and address other performance issues when self-hosting against  
     a target platform with 1000's of plug-ins.</li>  
   </ul>  
   </li>  
   <li>Rich Client Platform<ul>  
     <li>Provide an RCP template.</li>  
   </ul>  
   </li>  
   <li>Manifest Validation<ul>  
     <li>Add schema support to flag untranslated and deprecated attributes.</li>  
     <li>Improve the validation of schemas, features, and update sites by  
     improving the parsing and adding more flags.</li>  
   </ul>  
   </li>  
   <li>A more integrated IDE<ul>  
     <li>PDE should become a refactoring-participant to update plugin.xml files  
     when Java classes are renamed.</li>  
   </ul>  
   </li>  
   <li>Plug-in Dependencies<ul>  
     <li>Display a caller/callee view of plug-in dependencies</li>  
     <li>Display the plug-in dependencies in both a tree and table layouts.</li>  
   </ul>  
   </li>  
   <li>Update Site Tooling<ul>  
     <li>Revamp our update site tooling, including the editor and the overall  
     strategy and workflow.</li>  
   </ul>  
   </li>  
   <li>Testing<ul>  
     <li>Add more JUnit Tests</li>  
   </ul>  
   </li>  
   <li>Other<ul>  
     <li>Reduce the defect backlog.</li>  
   </ul>  
   </li>  
 </ul>  
     <p><font size="3"><b>3.1 Development Effort - Milestone 5 (Feb 18, 2005)</b></font></p>  
 <ul>  
   <li>Rich Client Platform<ul>  
     <li>Introduce the notion of an &quot;Eclipse Product&quot; to the tooling.</li>  
     <li>Implement a &quot;New Eclipse Product Configuration&quot; wizard.</li>  
     <li>Provide an Eclipse Product packaging/export solution.</li>  
   </ul>  
   </li>  
   <li>Runtime/Self-Hosting<ul>  
     <li>Adapt to the new runtime/manifest.mf changes.</li>  
     <li>Add a new option to the new plug-in project creation wizard to indicate  
     which version of Eclipse is being targeted (2.x, 3.0, 3.1)</li>  
     <li>Editors must be made aware of which version of Eclipse the plug-in is  
     for as some manifest headers may have different meanings.</li>  
   </ul>  
   </li>  
   <li>Features<ul>  
     <li>Redesign the feature manifest editor.</li>  
     <li>Improve the connectivity and workflow in the feature-update site story.</li>  
   </ul>  
   </li>  
   <li>Other<ul>  
     <li>Reduce the defect backlog.</li>  
   </ul>  
   </li>  
 </ul>  
     <p><font size="3"><b>3.1 Development Effort - Milestone 6 (April 1, 2005)</b></font></p>  
 <ul>  
   <li>Full JAR'd plug-in format support.&nbsp; Remaining issues include:<ul>  
     <li>Source attachment/packaging for JAR'd plug-ins.</li>  
     <li>Generating New Plug-in Project templates when org.eclipse.pde.ui is in  
     JAR'd form.</li>  
   </ul>  
   </li>  
   <li>Provide a wizard that creates a plug-in out of individual JARs.</li>  
   <li>Product/Plug-in/Feature Export<ul>  
     <li>Add a product export wizard to be invoked from the product configuration  
     editor and via the File &gt; Export.. menu to export an Eclipse product in  
     multiple formats.</li>  
     <li>Add support to sign Plug-in/Feature JAR archives.</li>  
     <li>Add support to create JNLP manifests for feature JAR archives.</li>  
   </ul>  
   </li>  
   <li>Classpath Computation<ul>  
     <li>Support the new Eclipse-ExtensibleAPI manifest.mf header, which allows  
     fragment JARs to go on a plug-in's classpath.</li>  
     <li>Introduce inclusion/exclusion patterns to the PDE container's classpath  
     computation to restrict access to code between plug-ins.</li>  
   </ul>  
   </li>  
   <li>Plug-in Manifest Editor<ul>  
     <li>Add new sections to support important manifest.mf headers such as  
     import/export packages, and import/export services.</li>  
     <li>Dynamic addition/removal of editor pages depending on whether the  
     plug-in has a manifest.mf or not.</li>  
     <li>Make the option to create a manifest.mf for a plug-in more prominent.</li>  
   </ul>  
   </li>  
   <li>Manifest.mf validation<ul>  
     <li>Introduce semantic manifest.mf validation.</li>  
   </ul>  
   </li>  
   <li>Improve schema editor<ul>  
     <li>Rework the schema editor to make the first page more user-friendly and  
     get rid of the property sheet.</li>  
     <li>Expose support for including schemas in the UI.</li>  
   </ul>  
   </li>  
   <li>Other<ul>  
     <li>Reduce the defect backlog.</li>  
   </ul>  
   </li>  
 </ul>  
111      </td>      </td>
112    </tr>    </tr>
113    <tr>    <tr>
Legend:
Removed from v.1.40  
changed lines
  Added in v.1.41