Hi Folks --
Actually, this is all being thought through once again as we try to design and build the "Omniuser Authoring System" of which the next version of the kids' etoys system should be a subset.
I think that copy actions are too cavalier on the one hand, and classes are too top down and rigid on the other. We need something in between these two extremes. E.g. I would like to be able to "promote" an example player to being a "source" for instances. I think this will call for several UI changes, including ways to mark and find the "sources".
Ideas?
Cheers,
Alan
At 06:34 AM 12/26/2004, stéphane ducasse wrote:
Hi scott
I digested quite well your explanation (in fact this was what I thought).
I was always thinking that halo actions would not contain copy *and* make a sibling.
The change made in 3.8 is that once an object has been *scripted*, the halo handle seen at the top-right of its halo will now be an olive colored handle whose operation makes a sibling-instance rather than a deep-copy.
and in addition this is what confused me. I was looking anymore at halo actions since I thought that I would get all the time the make-sibling (and not copy). What pierre-andre was suggesting was to have make-sibling per default and with with plus green halo copy. this way you do not have to go into the halo menu mess.
Stef
Squeakland mailing list Squeakland@squeakland.org http://squeakland.org/mailman/listinfo/squeakland