I now see what you are saying
There seems to be a need to create many object instances, which while elegant will definitely make the library seem daunting to new users and adopters
Is there a way of having some of the classes hidden from the developer, via public setters/getters that abstract the details
For example when adding an address in PHP Mailer, you provide an email and a name (optional), the ezcMailAddress instance can be created internally
I think Zend Framework has this kind of abstraction where you can provide an array of options (including) a class name and the object classes are initialized for the user
Your thoughts?
↧