Updating additional_plugins
Posted: Wed Jan 14, 2009 12:42 pm
As you all know, I'm committed to contribute to s9y further by not only editing the emitted HTML code for core plugins, but also the so-called additional_plugins. Now, before I begin, I wanted to check on some ground rules with you guys.
A. If I actually change the emitted code, am I supposed to incement the version number of the plugin in question? Is it maybe even necessary for the new version to show up in Spartacus? Is there any common pattern for plugin version numbering?
B. A lot of the potential changes will be about removing inline styles. Inline styles really are a pain in the ass. However, it might be necessary to keep some base styles for the plugin in order to keep it usable. How do I go about this? Can I add a "plugin-specific stylesheet" which will be added to serendipity.css dynamically? I know some plugins do this, but how do I actually add something like that to a plugin?
YL
A. If I actually change the emitted code, am I supposed to incement the version number of the plugin in question? Is it maybe even necessary for the new version to show up in Spartacus? Is there any common pattern for plugin version numbering?
B. A lot of the potential changes will be about removing inline styles. Inline styles really are a pain in the ass. However, it might be necessary to keep some base styles for the plugin in order to keep it usable. How do I go about this? Can I add a "plugin-specific stylesheet" which will be added to serendipity.css dynamically? I know some plugins do this, but how do I actually add something like that to a plugin?
YL