Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317736 - Tigerstripe Explorer shouldn't be tied to Java Package Explorer
Summary: Tigerstripe Explorer shouldn't be tied to Java Package Explorer
Status: CLOSED DUPLICATE of bug 317761
Alias: None
Product: Tigerstripe
Classification: Technology
Component: UI (show other bugs)
Version: 0.5M1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 14:29 EDT by Eric Dillon CLA
Modified: 2010-08-16 09:57 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Dillon CLA 2010-06-23 14:29:17 EDT 
As of now, the Tigerstripe Explorer is built by extending the Java Package Explorer which is including an unnecessary dependency on the JDT.

The Tigerstripe Explorer should be built directly upon the common navigator framework, eg. or similar existing framework.

Parity on functionalities should be ensured.
In particular:
- Same look-n-feel regarding icons for Tigerstripe artifacts, or diagrams.
- DnD from Tigerstripe explorer to Class and Instance Diagrams.
- Representation for modules (whether local to project or installed)
- references to other model projects
- refactoring of Tigerstripe artifacts, DnD across projects.
- moving/copying diagrams within projects and across projects.
- Allowing to display flat or hierarchical views for packages.

In addition it would be good to provide support for Working Sets and filters which is not supported by the Tigerstripe Explorer as is.
Comment 1 Richard Craddock CLA 2010-08-16 09:57:45 EDT 

*** This bug has been marked as a duplicate of bug 317761 ***