2009-08-12, 04:23:48
I've been thinking a little bit about the way plugins could be added and there is solution that came to mi mind.
I really like components (and now it also supports php) so I was thinking why not to make it something similar. Imagine that you'd just put plugin to a certain folder like themes (that is pretty much in every CMS) but plugin would be divided into under the hood and views (you can as well take typical "model controller view"... that pretty much doesn't matter from point of a regural person). What is important is that this plugin would have just generated their own "components" where you coul simply create a new component or edit existing ones and it would only generate a simple function like components does (e.g. <?php get_component('tagline'); ?>). This could really easily fit into system. Even more "drastic" way would be to start considering components as plugins (so every single component would be a plugin) and they would be divided in admin also).
This way you could create "components plugin" for analytics (meaning batch of components containing analytics snippets) or "components plugin" for a small text all over the website, but also a real plugins like photogallery etc.
What i described so far is how you could prepare plugins for front end. I've been giving a thought to integrating plugins to admin a little too, but I haven't figured the moste efficient way to do that yet (just a bunch of average ones). The biggest problem in admin is how to decide which plugin should get its own tab for managing (like galleries or ecommerce solutions and stuff like that) and which shouldn't (so there would be a "plugin" tab with all the less important plugins (like a small statistics scripts or simple rss feed) it would be nice to get in touch with developers to talk about this and maybe find very effective solution for this too... or at least get their feedback.
I really like components (and now it also supports php) so I was thinking why not to make it something similar. Imagine that you'd just put plugin to a certain folder like themes (that is pretty much in every CMS) but plugin would be divided into under the hood and views (you can as well take typical "model controller view"... that pretty much doesn't matter from point of a regural person). What is important is that this plugin would have just generated their own "components" where you coul simply create a new component or edit existing ones and it would only generate a simple function like components does (e.g. <?php get_component('tagline'); ?>). This could really easily fit into system. Even more "drastic" way would be to start considering components as plugins (so every single component would be a plugin) and they would be divided in admin also).
This way you could create "components plugin" for analytics (meaning batch of components containing analytics snippets) or "components plugin" for a small text all over the website, but also a real plugins like photogallery etc.
What i described so far is how you could prepare plugins for front end. I've been giving a thought to integrating plugins to admin a little too, but I haven't figured the moste efficient way to do that yet (just a bunch of average ones). The biggest problem in admin is how to decide which plugin should get its own tab for managing (like galleries or ecommerce solutions and stuff like that) and which shouldn't (so there would be a "plugin" tab with all the less important plugins (like a small statistics scripts or simple rss feed) it would be nice to get in touch with developers to talk about this and maybe find very effective solution for this too... or at least get their feedback.