> I suppose the book is being fair when it says "There is a lot that it
> doesn't do for you but it will get you started."   Hmm, more like get
> you frustrated and ready to move on to a fully-featured working
> library.  I will propose a 'diplomatic' amendment to the book.

I understand why you were frustrated. I, too, have been frustrated by
the component. With that said, I think an email component is something
that does need to be in the core and look forward to seeing the
component expand into a more robust solution. I think that an email
component should be in there because it is such a common task when it
comes to building web applications. To have to import third party
libraries, it's an extra step of integration that users will commonly
have to do, and documenting that process will be more difficult.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to