Bug 398036 - suggestion for adding fragment ids and annotations using them
Summary: suggestion for adding fragment ids and annotations using them
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-13 16:44 EST by Steven Spungin CLA
Modified: 2013-02-15 15:27 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Spungin CLA 2013-01-13 16:44:34 EST
Based on difficulty I have had obtaining my rendered fragment elements from the EModel Service, I suggest the following

1. Add an ID Parameter to the org.eclipse.e4.workbench.model fragment extension element

2. Use this ID as a parameter the context to get elements from the EModelService:
     EModelService.findFragmentElement(fragmentId, elementId)]

3. Create an annotation @FragmentRendered(name=<fragmentId>) that is called after all items in the fragment have been processed.  If the parameter is not set, the annotated method will be called after all fragments in the model have been rendered.

This would speed up searches for plugins concerned with their own contributions, and also create a well known access point to manipulate those contributions.  The annotations would also give us more control over initialization with multiple fragments (It's not currently clear in this case when using post fragment org.eclipse.e4.workbench.model processors as to when and in what order they are called.)