[Newbies] Best practice for very simple objects

Hi, I'm thinking right now about some role and permission stuff for my webapp. But I'm asking myself what will be a good approach for this. At first I created a lot of classes like AdminRole, MemberRole, CreatePermission, ModifyPermission etc. I used the class objects for this. These only carry

Re: [Newbies] Best practice for very simple objects

Norbert Hartl wrote: At first I created a lot of classes like AdminRole, MemberRole, CreatePermission, ModifyPermission etc. I used the class objects for this. These only carry some state like index, label. The role objects also carry a set of permissions. I'm a big fan of instances :-)

Re: [Newbies] Best practice for very simple objects

Norbert Hartl wrote: Hi, I'm thinking right now about some role and permission stuff for my webapp. But I'm asking myself what will be a good approach for this. P.S. have you looked at the SmallWiki permission and role implementation? ___ Beginners

Re: [Newbies] Best practice for very simple objects

On Tue, 2007-06-26 at 15:45 +0200, Michael Rueger wrote: Norbert Hartl wrote: At first I created a lot of classes like AdminRole, MemberRole, CreatePermission, ModifyPermission etc. I used the class objects for this. These only carry some state like index, label. The role objects also

Re: [Newbies] Best practice for very simple objects

On Tue, 2007-06-26 at 15:46 +0200, Michael Rueger wrote: Norbert Hartl wrote: Hi, I'm thinking right now about some role and permission stuff for my webapp. But I'm asking myself what will be a good approach for this. P.S. have you looked at the SmallWiki permission and role

[Newbies] How do you find which code runs when you click on something?

*** Hi Ian, This is an excellent question ‘cause it shows up the current obscurity of the answer. The secret you need to know its that the object that dispatches the mouse events looks high and low for someone to handle it. When an unspecial morph is clicked on the fellow who handles it is the