man alive. I must cut down on the crack for lunch
Here is how I figured it could work:
vB has a mack installer.
The installer would deal with new phrases, phrasegroups, plugin code, templates and optionally running queries.
Macks would then come with as an XML file listing all of these things.
vB could cache the xml file for later removal if needed.
The real butt pain as was previously mentioned is that complex XML files are a bummer to create.
That is until a mack maker is released.
The mack maker would simply be an admincp page that would:
Allow you to create a 'project'
Define the phrasegroups and phrases
Define the templates
Define the plugin code
Optionally define DB queries
It could then persist these into a table(s), click 'generate' and viola! It could create the xml for you.
A mack maker wouldnt be too hard to make and I am sure the community would take care of that in no time. However that would be dependant on vB creating an installer that at least handled more than just doing the plug in code.
Whew.