Re: [Phpwebsite-developers] Central group authorization table (Option 2)

[Matthew M. <ma...@tu...>]

> What if we implemented the group-based restrictions by category instead?
> That way the user has one choice to make -- "what category(ies) does the
> announcement belong to? " That way, they don't -have- to know that
> announcements in "Financial Reports" can only be seen by users that are
> members of the Accounting, Oversight, and Investors groups.  The
> application
> immediately becomes more idiot-proof!

I think this is a good idea but I wouldn't alter the current FatCat code.
I am currently rewriting it for 0.9.3.

The problem is we have to look at the way we currently are using FatCat.
When we wrote many of these modules, FatCat wasn't considered a 'core'
module. Therefore, FatCat works independently from all modules. Module's
have no idea what category they are in and FatCat doesn't really know the
significance of the information it receives from the module.

So FatCat is going to need to be 'aware' of what it is categorizing and
modules need to be 'aware' of what category they are in. Currently, it's
just not in the code.

So I agree with your idea but I would hold off trying to alter the current
code. Stay tuned though and jump in the chat room so you can offer input
when we start restructuring it.

Thanks,
Matt

-------------------

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu