Re: Checking lots of conditions...ORed and ANDed

I've put together the design for something similar and am waiting for project go-ahead at work to implement it. The design takes a different tack.

There is a set of authorities which define every action a given user can take.
Each user has a given set of authorities assigned to them.
There is a given set of menu items which are all the items that can be put into a menu.
Each menu item knows what authority(s) are necessary to have it displayed.
A controller will have every menu item query the user object for its specific authority(s). The menu item determines if it should be displayed.

So, when you create a new menu item, you have it (and only it) know which authority combination is required for it to be displayable. If you don't want a menu item to be shown, you simply have the controller not put it in the list for querying.

Simple.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

Comment on Re: Checking lots of conditions...ORed and ANDed

Replies are listed 'Best First'.
Re^2: Checking lots of conditions...ORed and ANDed by TVSET (Chaplain) on Jun 08, 2004 at 02:16 UTC
In my case, menus are very dynamic, depend on many factors and can change several times during the day. Consider managing a schedule for few people for few shifts (24x7 network operations center). Checking who is allowed to do what, has been already done. It is one level above this code. ;) Leonid Mamtchenkov aka TVSET	[reply]
Re^3: Checking lots of conditions...ORed and ANDed by dragonchild (Archbishop) on Jun 08, 2004 at 11:50 UTC
Ok. So, have the menu item know what factors affect its ability to display itself. shrugs Just because you've handled the problem I describe solving doesn't mean the algorithm wouldn't be helpful in solving what you're looking to do. ------ We are the carpenters and bricklayers of the Information Age. Then there are Damian modules.... sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon.* - flyingmoose I shouldn't have to say this, but any code, unless otherwise stated, is untested	[reply]
Re^4: Checking lots of conditions...ORed and ANDed by TVSET (Chaplain) on Jun 08, 2004 at 20:07 UTC
Sorry. Misunderstood. Leonid Mamtchenkov aka TVSET	[reply]