pde-ui-home/main.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.43 - (download) (as text) (annotate)
Fri Sep 23 16:31:27 2005 UTC (4 years, 2 months ago) by wmelhem
Branch: MAIN
Changes since 1.42: +44 -2 lines 
*** empty log message ***

<html>
<head>
<title>PDE UI Component</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
</head>

<body bgcolor="#FFFFFF" text="#000000">
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=left width="72%"> <font class=indextop> pde ui </font> <br>
      <font class=indexsub> plug-in development ui </font></td>
    <td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg" height=86 width=120></td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=LEFT valign=TOP bgcolor="#0080C0"><b><font color="#FFFFFF" face="Arial,Helvetica">Development 
      Resources </font></b></td>
  </tr>
  <tr> 
    <td> 
      <p>If you are already a PDE UI developer, check out the <a href="dev.html">Development 
        Resources</a>.</p>
      </td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=LEFT valign=TOP bgcolor="#0080C0"><b><font color="#FFFFFF" face="Arial,Helvetica">PDE UI</font></b></td>
  </tr>
  <tr> 
    <td> 
      <p>The Plug-In Development Environment (PDE) is a collection of integrated 
      tools targeted at you, the plug-in developer. Some of PDE's contributions 
      to the Eclipse workbench include:<ul>
          <li>New Plug-in, fragment, feature and update site projects creation 
          wizards.</li>
          <li>Multi-page editors to edit manifest files for plug-ins, fragments, 
          features and update sites.</li>
          <li>Import wizards to import external plug-ins, fragments and 
          features.</li>
          <li>Export wizards to build, package and deploy plug-ins, fragments 
          and features.</li>
          <li>a launcher to test and debug your plug-in.</li>
          <li>a search engine to search for plug-ins, fragments, extensions, and 
          extension points with a scope that goes beyond the workspace.</li>
          <li>a log view with sorting, filtering capabilities to view the 
          contents of the log file.</li>
        </ul></p>
      </td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=LEFT valign=TOP bgcolor="#0080C0"><b><font face="Arial,Helvetica" color="#FFFFFF">What's 
      Happening? </font></b></td>
  </tr>
  <tr> 
    <td> 
      <p>Over the next 6 months the major focus points are:</p>
      <ul>
        <li>RCP tooling.</li>
        <li>Runtime/OSGi tooling.</li>
        <li>Improving feature development tooling.</li>
        <li>Enhancing existing features.</li>
        <li>Reducing the defect backlog</li>
        </ul>
      <p>For more detailed information, check out the <a href="dev.html">Development 
        Resources</a>.</p>
      <p>&nbsp;</p>
</td>
  </tr>
  <tr> 
    <td> 

<h4> <a name="Milestone_Planning"></a> 3.2 Development Effort - Milestone 2 
(September 23, 2005)</h4>

<ul>
<li>Rich Client Platform<ul>
<li>Enhance the New Plug-in Project Creation wizard to allow the creation of a 
headless rich client application.</li>
<li>Provide a Hello World headless RCP template.</li>
<li>Add Intro support to the RCP Product editor.</li>

</ul>
</li>
<li>Runtime/OSGi<ul>
<li>Enhance the New Plug-in Project Creation wizard to allow the creation of a 
pure OSGi bundle that is not dependent on the runtime layer.</li>

</ul>
</li>

<li>An Integrated IDE<ul>
<li>Plug-in working sets should participate in builds, view filtering, searches.</li>
<li>Participate in refactoring (manifest.mf, plugin.xml and fragment.xml files).</li>

</ul>
    </li>
<li>Eclipse Application launcher<ul>
<li>Make the launch configurations portable.</li>
<li>Make the launcher tabs and the runner configuration API.</li>

</ul>
    </li>

<li>Reduce the defect backlog.</li>

</ul>
    <p>&nbsp;</p>
<p> <a name="Milestone_Planning"></a> <b><font size="3">3.2 Development Effort - Milestone 
3 
(November 5, 2005)</font></b></p>
<ul>
  <li>Runtime/OSGi tooling<ul>
    <li>Implement an OSGi launcher</li>
    <li>Automated management of exported packages in a plug-in.&nbsp; Come up 
    with a tooling equivalent of the old &lt;export name=&quot;*&quot;/&gt;</li>
    <li>More refactoring: renaming a package in an Export-Package header should 
    result in the renaming of that package in all client bundles that have 
    imported it.</li>
  </ul>
  </li>
  <li>Bundle Execution Environment - Prelude to J2SE5.0 adoption<ul>
    <li>Add support for the Bundle-RequiredExecutionEnvironment manifest header 
    into the PDE plugin editor.</li>
    <li>The New Plug-in/Fragment project creation wizard to start asking the 
    user the level of JRE the plug-in is targeted for.</li>
    <li>Use the Bundle-RequiredExecutionEnvironment header when importing 
    plug-ins to set the correct compiler compliance levels.</li>
  </ul>
  </li>
  <li>NLS tooling<ul>
    <li>Implement an NLS wizard to externalize plug-in manifest files</li>
    <li>Add support the manifest builder to flag unused keys in the 
    plugin.properties files.</li>
  </ul>
  </li>
  <li>Quick fixes (Investigation)<ul>
    <li>Investigate a quick fix support on manifest files.</li>
    <li>The pioneer quick fix would be the one to fix the soon-to-be-deprecated 
    Eclipse-AutoStart header.</li>
  </ul>
  </li>
  <li>New Source Lookup (investigation)<ul>
    <li>start the investigation</li>
    <li>co-ordinate with the Debug and Core teams on what pieces need to be in 
    place.</li>
  </ul>
  </li>
  <li>Reduce the defect backlog.</li>
</ul>
<p>&nbsp;</td>
  </tr>
  <tr> 
    <td> 

&nbsp;</td>
  </tr>
</table>
<table border=0 cellspacing=5 cellpadding=2 width="100%" >
  <tr> 
    <td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font color="#FFFFFF" face="Arial,Helvetica">Get 
      Involved!</font></b></td>
  </tr>
  <tr> 
    <td> 
      <p>If you are interested in participating in the development of the PDE UI component, 
        check out the developer's mailing list: <a href="http://dev.eclipse.org/mailman/listinfo/pde-ui-dev">pde-ui-dev@eclipse.org</a>. 
        Chat with people there about your problems and interests, and find out 
        what you can do to help.</p>
      <p>In particular, if you have written (or have ideas for) any utilities, "spy" functions, code generators, transformers,
        importers, exporters, or any other code that you find useful (or would find useful) for development of plug-ins, and
        would like to get involved in getting the function integrated as part of PDE, we would like to hear from you.</p>
      <p>For more detailed information, check out the <a href="dev.html">Development 
        Resources</a>.</p>
      </td>
  </tr>
</table>
<p>&nbsp;</p>
</body>
</html>