After browsing more code I think that having a PackageOrganiser would support better the migration of existing code.
Stef On Oct 11, 2009, at 11:23 PM, Schwab,Wilhelm K wrote: > Stef, > > I'm not sure I'm following what you mean by a single class. I would > probably go for a singleton manager and a package class with > instances for each package. > > Loosely related , it would be _really_ nice to be able to assign > multiple categories to methods. > > Bill > > > -----Original Message----- > From: [email protected] [mailto:pharo- > [email protected]] On Behalf Of Stéphane Ducasse > Sent: Sunday, October 11, 2009 2:36 PM > To: Pharo Development > Subject: [Pharo-project] PackageOrganizer vs Package class side > > Hi all > > I coded a bit with david today on the package support and I would > like to know what you think about having Package class side methods > for register, named: ...... vs having and explicit separate class. > > I'm tend towards having one single class. > > Right now in Pharo packageInfo and PackageOrganizer responsibility > are not that clear. > > Stef > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
