What I have so far:
- Riffing on Rogue's RPFramework, I've started to develop a separate module that contains methods with blocks of common code. Mine is in no way comparable, but RP's approach is a great way to get ideas (that is to say, steal them).
- Using the Indigo API <Template> facility, I've developed XML templates to simplify pluginConfig files for common settings (like plugin update notification and debug settings). I can see these being useful for other things too (like MenuItems).
- I create one instance of each item in a central folder in my development environment and then create hard links in each of the appropriate plugins' source files. Update one, update all.
- When working on any plugin, if I find a bug or enhancement, I can include it then and there and it will "automatically" propagate to my other plugins that use that framework element. It is important to note that you must make the changes to the original version of the file. It seems that if you make a change from one of the links, the change will only be made there and the link will be broken.
I do realize that to most of the developers here this is like me saying that I just found my elbow. But any hints or tips that others use to help me find my other elbow would be most appreciated. Maybe others could benefit from the discussion too.
- Code: Select all
<?xml version="1.0"?>
<PluginConfig>
<Field id="infoLabel0" type="label">
<Label>Some Plugin</Label>
</Field>
<Field id="pluginRefresh" type="textfield" defaultValue="15" tooltip="Enter the number of seconds between refreshes.">
<Label>Refresh Frequency</Label>
</Field>
<!-- Notifications Template -->
<Template file="template_notifications.xml" />
<!-- Debugging Template -->
<Template file="template_debugging.xml" />
</PluginConfig>