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.
I was in a hurry while i typed this :)
now that i've put a little more thought in it
-extensions can "work like plugins", they just directly integrate in
the app so you can call all the logic you want from them, you can use
the models, .. from a programming/scope side of view, it was af is the
code files were inside your app just like the others, so this gives
very much freedom. (same goes for "open plugins" offcourse)
-plugins that want to "expose/inject their code into the app" might be
better off being built as extensions, when you want to expose your code
to the app you're suggesting a strong , deeply integrated connection
between the plugin and the app. Plugins aren't meant for this. they
are meant to be little applications working on their own, the main app
shouldn't have to implement, or inherit from the plugin. However, if
you want to "improve" a plugin, i think you should be able to.
(without the need to alter the original plugin). Inheritance seems
like a good way for this, i don't know if several plugins can inherit
from each other (i doubt it) (this also shouldn't be necessary, giving
the purpose of plugins (being "seperate apps")) but there should be
some way in which you can create a new plugin, that "includes" another
plugin to inherit from it. Though, this is another problem then the
one i described. (however, having an "extensions" directory in a
plugins directory would be pretty neat too, if you can follow my
thoughts)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
