> Just to add my last 2ps to the idea - I was wondering along these > lines not for providing generic extensions but for preventing feature > bloat in specific applications.
To me it is about having (reusable) sources available in a flexible way (like "libraries" in most languages, except that in this case cake core doesn't have to search through the "libraries", it can immediately find what it needs if we implement a few conventions ) one of the side-effects of extensions would be that more specific featuresets end up in specific extensions (if you want that, if you don't that's fine too ofcourse ) So if that's your only goal, you could use it just fine for that too ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
