On Jul 6, 2010, at 10:51 PM, Pavel Krivanek wrote: > code: > > MethodReference organization moveCategory: '*Kernel-Traits' to: > '*Traits-Kernel'. > LRUCache organization moveCategory: '*Polymorph-Widgets-override' to: > 'accessing'. > Project class organization moveCategory: 'utilities' to: '*Morphic'. > Character organization moveCategory: '*Multilingual' to: > '*Multilingual-Encodings'. > TranscriptStream organization moveCategory: 'toolbuilder' to: > '*ToolBuilder-Kernel'. > TranscriptStream class organization moveCategory: 'toolbuilder' to: > '*ToolBuilder-Kernel'. > > description: > > MethodReference organization moveCategory: '*Kernel-Traits' to: > '*Traits-Kernel'. > - swap package name parts to a more logical ownership. It contains > only a method actualClass that has no other kernel implementation. > Both packages will be in the kernel image.
What about just folding actualClass in MethodReference? I do not understand the point of the KernelTraits or Traits-Kernel. May be MCDefinition>>actualClass should also be folded into MCDefinition and not Polymorph-Tools-Diff > LRUCache organization moveCategory: '*Polymorph-Widgets-override' to: > 'accessing'. > - only one method. Declared as override but has no old version in the > history and has general functionality ok > Project class organization moveCategory: 'utilities' to: '*Morphic'. > - all methods have no real senders or are called only from Morphic In fact these methods should be moved in another place so that we can remove Project. For now this is ok to move them to Morphic > Character organization moveCategory: '*Multilingual' to: > '*Multilingual-Encodings'. > - only fix MC package name Ok even if I was wondering why encodings is not folded into Collections-Strings.. > TranscriptStream organization moveCategory: 'toolbuilder' to: > '*ToolBuilder-Kernel'. > - single method buildWith:, used only for the Toolbuilder > > TranscriptStream class organization moveCategory: 'toolbuilder' to: > '*ToolBuilder-Kernel'. > - the same with this logic it means that we could remove toolbuilder or plug it on demand. Why not. I will integrate already that. > > _______________________________________________ > 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
