[etoys-dev] Re: Merging Etoys
andreas.raab at gmx.de
Mon Feb 22 08:21:03 EST 2010
Bert Freudenberg wrote:
> Sounds right - I did not mean to literally use this old change set but to take it as a reference point. And matching the trunk structure is important.
> For the various non-trunk categories I think moving them to the "Etoys" package would be a good first-order guideline. Here is an example:
> MessageSet openMessageList: (PackageInfo named: 'FlexibleVocabularies') extensionMethods name: 'ext methods'
> We currently have about 30 packages more than Trunk (try the script below) but many of them are accidental and would have a natural home in the "Etoys" package (e.g. Connectors - unless someone would step up to maintain it as a separate package).
Sounds reasonable. One of the things that might be helpful is to set up
a wiki with "porting notes and status" for each package (like noting
that we should discuss folding Connectors into Etoys).
We should then spend some time to go over the differences and just take
notes about the portions that require work. I'd like to get an idea
first about the scope of what needs to be done and then about how to
address the issues.
> And we should fix the spelling of the "Etoys" package to not have a capital "T", both in the Etoys image and Trunk.
Fine by me. You've got all the commit rights you need :-)
> - Bert -
> packages := PluggableSet new.
> packages equalBlock: [:a :b | a sameAs: b].
> packages hashBlock: [:a | a asLowercase hash].
> SystemOrganization categories do: [:category |
> packages add: (category copyUpTo: $-) asString].
> Smalltalk allClassesDo: [:cls | cls organization categories do: [:protocol |
> protocol first = $* ifTrue: [
> packages add: (protocol allButFirst copyUpTo: $-)]]].
> packages asSortedArray
> etoys-dev mailing list
> etoys-dev at squeakland.org
More information about the etoys-dev