Download
2012-06-21, 01:51:00
I don't know, I like components, it gives me a single location to manage all my code modules.
Plus it removes all that overhead form your plugin, you don't have to code a codemirror textarea since we already have a mechanism for this. i18n search does this and I found it much more pleasant to work with than the way , say item manager did.
Of course if you implement a textarea, users can always just call their own component inside it, so doesn't really affect us. Was just thinking of ways to make plugin authoring easier than having code inputs all over the place.
Maybe in core we can have components register with the system and all show up in component editor, but remain linked to the plugin they belong to, so when the plugin is removed, the component can be and vice versa.
Plus it removes all that overhead form your plugin, you don't have to code a codemirror textarea since we already have a mechanism for this. i18n search does this and I found it much more pleasant to work with than the way , say item manager did.
Of course if you implement a textarea, users can always just call their own component inside it, so doesn't really affect us. Was just thinking of ways to make plugin authoring easier than having code inputs all over the place.
Maybe in core we can have components register with the system and all show up in component editor, but remain linked to the plugin they belong to, so when the plugin is removed, the component can be and vice versa.
