[Pharo-project] Plugin organization
stephane.ducasse at inria.fr
Wed Jan 21 16:10:26 EST 2009
sounds good to my eyes.
regularity is a huge plus to my eyes. I would like to have patterns to
organize tests too.
We should keep our braincells for real problems.
On Jan 21, 2009, at 2:05 PM, Michael Rueger wrote:
> Hi all,
> while working on a new (Open)Sophie release I ran into the problem of
> where to put some plugin code. In this case it is for the Curl Plugin,
> which Steven Riggins ported into Sophie, but the problem is pretty
> common I would guess.
> So the problem is this (as illustrated using our Curl package):
> - we have a package Sophie-Curl, which includes the Squeak Curl client
> and the CurlPlugin class.
> - loaded into a "normal" image, the CurlPlugin ends up being a
> of ProtObject as the superclass is missing.
> - now we separate it into Sophie-Curl and Sophie-Curl-Plugin, but that
> won't fly with the MC name matching
> - so we name it Sophie-Curl and Sophie-Plugin-Curl
> I think that is ugly.
> What I would like to propose is that we organize all plugins in
> Pharo in
> to a Plugin category.
> So we would then have "Plugin-Curl", "Plugin-Locale" etc. Or
> alternatively "Plugin-Network-Curl", "Plugin-System-Locale" etc.
> That would also allow to simply load all plugins into a VMMaker
> image by
> using a package "Plugin".
> What do you guys think?
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev