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

Bug 404919

Summary:	[Navigation Service] Improve the target of the Navigation Service
Product:	[Modeling] Papyrus	Reporter:	Camille Letavernier <cletavernier>
Component:	Core	Assignee:	Camille Letavernier <cletavernier>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	lars.gelin, papyrus-bugs, patrik
Version:	0.10.0
Target Milestone:	M7
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	399882
Bug Blocks:

Description Camille Letavernier

2013-04-04 12:06:44 EDT

Currently, the Navigation Service retrieves the target element in the current context (i.e. current diagram if used from a Diagram, or ModelExplorer is used from the ModelExplorer)

The resolution shall be improved, and use for example the following strategy:

- Search in the current view
- If not found, search in the ModelExplorer

We may also search in all existing diagrams, but this would then take much more time on big models. This should probably be a separate feature (e.g. from the ModelExplorer, search all views referencing the selected element).

Comment 1 Camille Letavernier

2013-04-30 08:03:06 EDT

Fixed in r10999

The Navigation Service has been augmented to support Navigation Target contributions. The mechanism is an Extension Point with a priority mechanism: the first valid Navigation Target is used (valid means that the target is able to select an element, e.g. the element is displayed in a Diagram)

Two implementations of the Navigation Target have been provided:

- Navigate in the current nested editor (i.e. current diagram)
- Navigate in the ModelExplorer (If the first option fails to retrieve the element)

More strategies may be easily added, but as said in the initial comment:

> We may also search in all existing diagrams, but this would then take much more time on big models. This should probably be a separate feature