The lively devs have struggled with various attempts to solve this problem. There were attempts at merging/updating morphs from their originals, and at one time, we had an editor that could edit multiple morphs at a time (see http://blog.bithug.org/uni/12FelgentreffTessenowThamsenObjectGroups.pdf for an explanation). Right now, a workaround is to select the morphs (dragging to select) and then inspect the selections. It has a property (selectedMorphs, IIRC) and you can run a script (for example "addScript" ;) ) on each of them.
There were other attempts at fixing this, Jens probably knows more. From: Sean P. DeNigris Sent: 19/02/2014 19:41 To: [email protected] Subject: Re: [lively-kernel] [General] Redefining the Class of Instantiated Morphs, Subclassing Instantiated Morphs on the Fly Philip Weaver wrote > A significant distinction appears to exist in Lively between writing > classes in the ide and interacting with objects using the inspector... I > wish I could click on an instantiated morph and select either "New > subclass" (even "Change class") Bump... this is an important topic. How does one generalize from visually created prototypes. For instance, you create a morph, then make copies, but realize that all the copies should have an additional property or script; how does one avoid adding it individually to each individual morph? ----- Cheers, Sean -- View this message in context: http://forum.world.st/General-Redefining-the-Class-of-Instantiated-Morphs-Subclassing-Instantiated-Morphs-on-the-Fly-tp3033887p4744932.html Sent from the Lively Kernel mailing list archive at Nabble.com. _______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel _______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
