pde-ui-home/main.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.36 - (download) (as text) (annotate)
Mon Oct 4 04:40:22 2004 UTC (5 years, 1 month ago) by wmelhem
Branch: MAIN
Changes since 1.35: +6 -0 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.1 Development Effort - Milestone 2 
(September 24, 2004)</h4>

<ul>
<li>Rich Client Platform<ul>
<li>Enhance the New Plug-in Project Creation wizard to allow the creation of a 
minimal, ready-to-run rich client application</li>
<li>Rename 'Runtime Workbench' launcher to 'Eclipse Application'.</li>
<li>Introduce the concept of a 'Plug-ins' working set, and add shortcuts to 
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>

</ul>
    </li>
<li>Plug-in Manifest Validation<ul>
<li>Fix the problem with flagging errors correctly but at the wrong line numbers 
that is due to imprecise parsers. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59681">bug 
59681</a>)</li>
<li>Add support to schemas to be able to flag un-translated attributes in 
plugin.xml files.&nbsp; This is a must to enable externalization of strings in 
manifest files in the future. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=51336">bug 
51336</a>)</li>

</ul>
    </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>

</ul>
    </li>
<li>Testing<ul>
<li>Add &gt;= 1 JUnit test(s)</li>
<li>Add &gt;= 1 performance test(s).</li>

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

</ul>
    </li>

</ul>
    </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>