| limiting features [message #253346] |
Mon, 07 April 2008 11:50  |
Eclipse User |
|
|
|
Our software will be used by other companies. For each company, some users
will be given full use of the software, and some users will be given rights
to only some of the software. My company wants one plugin; I thought we
could offer two plugins with the features that everyone will use be in one.
That is not an option.
How would you suggest we control access to certain editors/views for some
users?
|
|
|
| Re: limiting features [message #253351 is a reply to message #253346] |
Mon, 07 April 2008 12:33  |
| Eclipse User |
|
|
|
On Mon, 7 Apr 2008 11:50:57 -0400, "Jay Simpson" <jkh1978@hotmail.com>
wrote:
>Our software will be used by other companies. For each company, some users
>will be given full use of the software, and some users will be given rights
>to only some of the software. My company wants one plugin; I thought we
>could offer two plugins with the features that everyone will use be in one.
>That is not an option.
>
>How would you suggest we control access to certain editors/views for some
>users?
>
Please have a look at http://www.bredex.de/en/rcp-auth/paper.html
On this page are papers, slides and some examples which may help you
solving this problem (It's an extended version of my short talk about
this at EclipseCon).
If you can use Eclipse 3.4, look at the Activities solution, otherwise
use the Equinox Transformation solution.
Achim
|
|
|
Powered by
FUDForum. Page generated in 0.07605 seconds
Home