Download
On a sidenote, the 4.x would also be the ideal chance to rethink the already discussed future of I18N.
I like the idea of a manifest file, especially as an index of the plugin's structure.
Something that would also be absolutely awesome to have quickly at hand (imo, I coded my own) would be managing a plugin version update. You would simply write a file
As for plugin folder structure (separate folders), other established cms'es can be a good source of inspiration for making a decision.
I like the idea of a manifest file, especially as an index of the plugin's structure.
Something that would also be absolutely awesome to have quickly at hand (imo, I coded my own) would be managing a plugin version update. You would simply write a file
update.php, include it in your plugin dir, and the file would be automatically run only once when PHP sees that the cached plugin version and the freshly uploaded one don't match. Similarly, i'd always looked for hooks for running code only once upon plugin (de)activation.As for plugin folder structure (separate folders), other established cms'es can be a good source of inspiration for making a decision.
