[Vm-dev] Re: [Pharo-project] Plugin organization

Andreas Raab andreas.raab at gmx.de
Sat Jan 31 23:26:13 UTC 2009

David T. Lewis wrote:
>>> This still looks perfectly good to me, so how about just using
>>> "VMConstruction-Plugins-*" rather than "Plugins-*"?
>> Maybe I'm missing something but how is any of this different from 
>> VMMaker-Plugins which is the current categorization for plugins?
> The classes in category VMMaker-Plugins-OSProcessPlugin would then
> appear as part of the VMMaker package. If someone was maintaining
> VMMaker with Monticello, and also had OSProcessPlugin (or whatever)
> in their image, they would not want OSProcessPlugin to be saved as
> part of the VMMaker package.

I see. If that's the issue I would probably argue to split up VMMaker 
(it's too big as it stands for my taste) perhaps into 
VMMaker-Translation (CCodeGen, Slang), VMMaker-Interpreter 
(ObjectMemory, Interpreter), and VMMaker-Plugins (all the plugins with 
the common ones being in VMMaker-Plugins-Common). In which case 
VMMaker-Plugins-OSProcess could live side by side with the rest of the 
VMMaker packages.

   - Andreas

More information about the Vm-dev mailing list