Tilted Forum Project Discussion Community - View Single Post

trache · 03-04-2005, 07:24 AM

Why not just have one user class that is role-based? I have a journal system I've created in PHP/Pg that has a field for roles that is comma-separated.

"write_entries, comment_entries, edit_entries" etc.

I search for "write_entries" in the role/permissions field, and boom, the user can write entries in the diary (I've created it so many people can write to a specific journal... this entire system is going to be multi-journal).

Use a simple string search and replace to edit the field and update it back to the DB.

Subclasses work by specifying:

Code:

ClassB extends ClassB {
blah
blah
blah
}

But, good luck using information hiding, polymorphism, etc etc with PHP. The online documentation is utterly horrible. PHP4 has a cobbled-together concept of OOP that doesn't really work out, but I think PHP5 is much better. We'll see about that one *sigh*.

03-04-2005, 07:24 AM	#2 (permalink)
trache Insane	Why not just have one user class that is role-based? I have a journal system I've created in PHP/Pg that has a field for roles that is comma-separated. "write_entries, comment_entries, edit_entries" etc. I search for "write_entries" in the role/permissions field, and boom, the user can write entries in the diary (I've created it so many people can write to a specific journal... this entire system is going to be multi-journal). Use a simple string search and replace to edit the field and update it back to the DB. Subclasses work by specifying: Code: ClassB extends ClassB { blah blah blah } But, good luck using information hiding, polymorphism, etc etc with PHP. The online documentation is utterly horrible. PHP4 has a cobbled-together concept of OOP that doesn't really work out, but I think PHP5 is much better. We'll see about that one sigh. __________________ "You looked at me as if I was eating runny eggs in slow motion." - Gord Downie of The Tragically Hip Last edited by trache; 03-04-2005 at 07:32 AM..