Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Compose a plugin on demand
Thank you, Yiannis, this could be a reasonable compromise. It gives the “main” plugin some control over its “components”, and technically should not be too complicated (but I leave it with devs). The end user wins in simplicity too. But, to be reliable, it requires a centralized permanent storage for plugins. If some day textpattern.org/ is rebuilt, this could be an interesting feature (for plugin updates too).
Offline
Re: Compose a plugin on demand
I have nothing against if someone wants to do custom packaged plugins, or if packaging features are added to a plugin, but I would rather not have any type of endorsed custom package compiling in the core projects, Textpattern or the actual plugin template. I personally don’t use ied_plugin_composer, so, I have no opinion to what you do with it. You can go crazy with it, as I care.
What this has gone from that is to about the plugin management, dependencies and updating. Which don’t work that well. Well, they don’t really suck, but are just nonexistent. There is no dependency management, no standards, no updaters, no noting.
…but I wouldn’t neither recommend us adding those to the core. We could never solve issues with third party libraries and dependencies. Truth is, you can’t use libraries with Textpattern plugin system since the plugins can just be a single file. The system does not comply well with ever growing array of PSR-0/1/2 projects. There is no namespaces, or autoloader mapping possibilities with the blob format Textpattern’s plugins use. It’s limited due to its simplicity. Only thing we could do with the plugin system is to have plugin dependencies… which doesn’t do anything.
Offline
Re: Compose a plugin on demand
Jukka, you are certainly right, things should be kept simple. What I meant in the previous post, is a core function to fetch plugins code from some uri and install it. This would allow a “master” plugin to contact some “repository” and install “library” plugins on user request, all in keeping trace of it, say in preferences. Master plugin would then know which libraries are (potentially) available.
Gocom wrote:
Only thing we could do with the plugin system is to have plugin dependencies… which doesn’t do anything.
Could be useful on delete.
Offline