Multiple inheritance

What if I want to make a compound draggable morph? Does my new morph inherit from both CompoundMorph and DraggableMorph? An example like this might be helpful. --
Bharvey (talk | contribs) 15:34, 23 May 2012 (UTC)

Hmm, you mean like a slider with a display? I personally would inherit from CompoundMorph, with a StringDisplayMorph and a DraggableMorph subclass. But I don't know what you should be doing. I'm actually working on a lightweight (barely: over 1000 lines of code and counting!) version of Morphic.js just for fun, and I'm finding inheritance the biggest issue. I stole Jens' inheritance code, got totally confused as to what it actually does, had to ask him for help, got lost even more, then finally rewrote it myself so that it worked. But an hour later when my Morphs had higher-level attributes like an array of children, reference issues popped up all over the place and now I'm lost again, making do with ugly patches all over the place. :( Who invented this yucky reference gunk anyway?!
But I digress. My point was, inheritance seems like a slippery subject, so I'll need to do some research on that before I write an article where I pretend to be an expert on the matter. So stay tuned! :)
Hardmath123 (talk | contribs) 16:27, 23 May 2012 (UTC)
Thinking some more, it seems like there are actually two inheritances (genealogies?) going on: the class inheritance which improves on the actual Morph and the "surface" inheritance where a CompoundMorph has children DraggableMorph and StringDisplayMorph. Is that right or have I totally lost it now?
Hardmath123 (talk | contribs) 16:29, 23 May 2012 (UTC)

Making shapes

Another thing I'd find helpful is an example of how things like the Scratch block shapes, which aren't simple polygons or arcs of ellipses are made. --
Bharvey (talk | contribs) 15:34, 23 May 2012 (UTC)