anselm wrote:
I do like the idea - but why make them different from plugins and add
another file structure to the system ? Plugins could choose to be
"closed" plugins, or "open" plugins ? Or plugins could have even select
which part of their API they decide to make public.

Okay, i like this idea.  Actually it's very similar to my idea, except
that i differ between plugins and extensions, and you differ between
open and closed plugins.  When working with your approach, plugins
would need to have a certain file or naming method that makes it clear
wether they are open or closed.
When working with my approach you don't need that, but you add another
directory to the app structure.
Your solution has the added benefit that plugins can have the workings
of plugins+extensions at the same time, while in my case, this wouldn't
be possible.

The problems then would be about versioning (the plugin will probably
expect an html helper which may, or may not be the same version you're
using) and namespacing (for instance for elements - "dateBox" ?)

The method i'm suggesting is just a tidy but efficient (atleast so i
think ;-) method of having sources available while coding in the scope
of your app.  This assumes you want some sources to be availble in your
app.  the old approach (eg getting all the files and inserting them in
the right directories), or the slightly improved (sorry i don't mean
this badly) version of this: merge-ins like tarique described, are also
ways to inject those logic into your app.
the versioning/namespacing problems are issues that arise when working
with "libraries" or when you depend on, or use other classes.
The problems aren't bound to the manner in which you make those
sources/classes available to your application, but more the actual
source they contain.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to