Re: [Gnumed-devel] GNUmed client > 0.2.8.1 menu alteration proposals

[Karsten Hilbert]

On Fri, Jan 04, 2008 at 08:48:37AM -0800, James Busser wrote:

> A related question, apart from how we group menu options, is how to manage 
> the availability of features depending on the user. For example, doctors 
> would be allowed to do and access things that receptionists may not. And 
> maybe it is desirable that not every doctor be able to do all things 
> administrative. What are the best (or even manageable) choices among
For one thing, options are settable by the current user for
the current user only. Options with systemwide consequences
will need to ask for the gm-dbo password. That approach does
have weaknesses but is fairly easy to implement.

> - configuring the presence or absence of menu options, by user
doable, depending on option

> - keeping the menu options constant across users, but just enabling or 
> disabling (dimming) menu items according to user
doable, depending on option

> - keeping the same menu items available to all users, communicating 
> anything that is disallowed to the user e.g. with a beep and a notice in 
> the status line like
>       "Feature restricted ...  insufficient privileges"
doable, depending on option

> ... likewise the question would arise for plug-ins, whether to control 
> whether certain users can add them to their plug-in lists and how these can 
> or cannot be used once the user is back in the client
That question is more relevant, IMO, and we don't have a
good solution yet.

> Naturally some menu items or plug-ins will permit some users partial views 
> or partial write-access, those would be controlled programmatically inside 
> the menu item or plug-in
yes

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346