Bug 284698 - [CommonNavigator] Visibility of content extension by using Common Expressions
Summary: [CommonNavigator] Visibility of content extension by using Common Expressions
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 04:25 EDT by Markus Jessenitschnig CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Jessenitschnig CLA 2009-07-27 04:25:30 EDT
Hello, 

I'm currently working on an application based on RCP which needs to hide/show parts of the UI depending on permissions granted to users. A proper way for most parts of the UI is using commons expressions to enable/change visibility for the active user depending on her access rights. For example, the visibility of commands can be easily changed following this way. 

Now I'm considering to integrate CNF in order to enable users navigating in our application. In order to show only content extensions the active user is currently allowed to see I would need a similar mechanism also for CNF. By now, the visibility of content extensions for a specific viewer is controlled using include and exclude patterns based on extension identifers. A more general approach might be achieved by using commons expressions to deal with content/filter visibility. This would introduce much more flexibility and would also enable a variaty of usage scenarios beside security related stuff. 

Kind regards and best wishes
Markus
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:14:20 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.