airportmarc

Hello all, This is more a design question. I am rebuilding my validation class, and have looked at a few different frameworks to see how they do it. What I see is that they create a base class, then each validation method extends this. eg. Required is a Class that extends Validate. Is there a benefit to doing this, compared to have a single class with a required method? Any insight would be great.

Hello all, So I have created an internal messaging system for our users, and while it works, I wanted to grow my OOP knowledge. So I have 2 objects, message, and messageControl. What I wanted to know was what should do what? For example, should the message be able to send itself, or is that the job for messageControl? Also, in the message class I have a method that displays itself, is that ok or should that be handled somewhere else (I can see this looking like MVC). On the site I have other objects where I run into the same problem of what should handle what. On the site an admin can approve or deny a users request. I have an object request and requestControl. What object should handle the approve/Deny process? While not new to PHP, my OOP design knowledge is lacking. Thanks for your help, Marc

Hello all, I am looking at the best way to implement an email system. I have a class that can email the person, but I have a lot of different messages that I might have to send. I wanted to know if my line of thought was efficient. Would it be a good idea to have a class that had all the possible email messages in it, and I would send it a key word to retrieve the proper message. Then if I had to email 100-300 people, would I create the class so that each instance of the class would send 1 email to a person, then destroy the class create a new one, etc... Or would it be better to send the class the list of people the Email should be sent to, and then have the looping occur within the class? Any ideas or suggestions would be great. Thanks All