| to perspective or not to perspective [message #715971] |
Tue, 16 August 2011 02:28  |
Eclipse User |
|
|
|
Hello all,
I'd like to have a suggestion on a program I'm going to develop using RCP. Essentially it is an ERP program, so the user will have different set of master-slave tables to edit and read. Now my doubt is: should I have to use a perspective for each kind of tables the user will be shown to? I mean, a perspective for the articles, one for the customers, one for the suppliers, and so on? Or should I use simply views?
Advantages of using perspective could be that the program becomes more customizable, I mean I can always remove a perspective or hide a perspective depending on the user permissions, but it is not clear if this is the right approach. Any suggestion is welcome.
Thanks
|
|
|
| Re: to perspective or not to perspective [message #715980 is a reply to message #715971] |
Tue, 16 August 2011 02:45  |
| Eclipse User |
|
|
|
Hi,
The customization argument can also be applied to Views. We are using
Views in our ERP application and group them in perspectives. E.g.
Privileges Perspective contains User, Group, ... Views, ....
Tom
Am 16.08.11 08:28, schrieb Luca Ferrari:
> Hello all,
> I'd like to have a suggestion on a program I'm going to develop using
> RCP. Essentially it is an ERP program, so the user will have different
> set of master-slave tables to edit and read. Now my doubt is: should I
> have to use a perspective for each kind of tables the user will be shown
> to? I mean, a perspective for the articles, one for the customers, one
> for the suppliers, and so on? Or should I use simply views? Advantages
> of using perspective could be that the program becomes more
> customizable, I mean I can always remove a perspective or hide a
> perspective depending on the user permissions, but it is not clear if
> this is the right approach. Any suggestion is welcome.
>
> Thanks
|
|
|
Powered by
FUDForum. Page generated in 0.03182 seconds
Home