Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317736

Summary:	Tigerstripe Explorer shouldn't be tied to Java Package Explorer
Product:	[Technology] Tigerstripe	Reporter:	Eric Dillon <erdillon>
Component:	UI	Assignee:	Project Inbox <tigerstripe.ui-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	rcraddoc
Version:	0.5M1
Target Milestone:	0.5M0
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Eric Dillon

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

2010-08-16 09:57:45 EDT


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