Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Plug-in Dependency Visualization"

(Deliverables)
(Deliverables)
Line 10: Line 10:
 
* Filter by JRE Version [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168729 (Bug#168729)]
 
* Filter by JRE Version [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168729 (Bug#168729)]
 
* Filter by Enabled / Disabled [https://bugs.eclipse.org/bugs/show_bug.cgi?id=183658 (Bug#183658)]
 
* Filter by Enabled / Disabled [https://bugs.eclipse.org/bugs/show_bug.cgi?id=183658 (Bug#183658)]
* Filter by Regular Expression (on bundle name)
+
* Filter by Regular Expression (on bundle name) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=183661 (Bug#183661)]
  
 
2. Add dependency path analysis (show why a plug-in is required by highlighting dependency paths).
 
2. Add dependency path analysis (show why a plug-in is required by highlighting dependency paths).

Revision as of 16:22, 23 April 2007

Understanding dependencies between plug-ins in Eclipse is a complex task. The current plug-in dependency analysis tools available in Eclipse are restricted to simple tree views with drill-down support. This project aims at adding visualization support to the Eclipse Plug-in Development Environment (PDE) in order to help provide cognitive support to developers as they analyze their plug-in dependencies. This view is being done as part of the Google Summer Of Code.

The Project

The dependency visualization aims to provide a set of views to assist with plug-in dependency analysis tasks. In particular, the views will provide cognitive support to people as they attempt to understand the dependencies between their plug-ins.

For a complete description of the view, please visit the project website.

Deliverables

1. Complete the PDE View and add 3 plug-in filters

2. Add dependency path analysis (show why a plug-in is required by highlighting dependency paths).

3. Add improved navigation support

  • Forward and back button support
  • Add search support for the list of show plug-ins

4. Remove the dependency on GEF

Accessing the code

Look here for a complete description of how to access the code for the PDE Dependency View

Back to the top