karlramberg at gmail.com
Wed May 12 20:03:18 EDT 2010
On Thu, May 13, 2010 at 1:17 AM, Bert Freudenberg <bert at freudenbergs.de>wrote:
> Am 12.05.2010 um 15:20 schrieb karl ramberg:
> There are some Etoy classes left in Morphic-Scripting and Morphic-Scripting
> These should be in Etoy package, right ?
> Makes sense :)
> Your update worked, if only by accident. Moving stuff from one package to
> another is tricky. You can see that after updating, the Morphic package is
> marked dirty.
> It worked because in the config map, the Etoys package comes before the
> Morphic package. When loading your Etoys package, classes are moved to
> Etoys, making the Morphic package dirty. Merging the Morphic package next
> does not reset that dirty mark.
> It would have been worse when moving the other way - then the classes would
> have been removed first, and then re-loaded later. That would have created
> obsolete instances.
> If we ever need to, it is possible to put a "small" config map into the
> update stream that just updates the two packages in the right order.
> Not sure how to reset the "dirty" bit of the Morphic package. One can do it
> in the MC browser by pressing "changes". We might put something similar into
> the update stream. Or fix MC upgrades to check for changes after merging ...
> that might be a better idea.
> And here is a hint for everyone submitting MC packages: before publishing,
> *always* check the changes (press MC's changes button) so you are sure that
> only changes you want to publish are included.
> - Bert -
I saw this mess and got a little confuced :-(
Couldn't a preamble doit for classes moving between packages work like
AlignmentMorph subclass: #ViewerRow
category: 'Etoys-Scripting Tiles' ?
It would be a lot cleaner at least.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the etoys-dev