[Cuis] Grow Button [WAS Re: New updates: Reference Finder..]

[Juan Vuletich]

On 12/31/2013 7:08 PM, Ken Dickey wrote:
> ...
> My model is that Classes use messages/methods/iVars
> but individual instances use events/handlers/properties.
>
> In particular, part of my list of past sins includes writing code in and for  MultiMedia authoring environments.  MM authoring -- particularly for media centric people who are not programmers -- tends to be more prototype based than class based.
>
> One starts with a bunch of media pallets and explorers, splats media on the stage, adds behaviors, ...  Authoring tends to me more graphical by nature. [See mTropolis UI examples below].
>
> One of the things I am thinking about is pushing Morphic toward a more direct/graphic style of authoring.
>
> One change to think about is making some tests more instance based.
>
> Why have an entire class of instances respond to some message when only a few instances need to?  An extra subclass with just a few methods.
>
> Simple (possibly useless) example.
>
> We could change some methods to look for properties.
>
> Say
>
> Morph>>allowsSubmorphDrag
>    ^ self hasProperty: #allowsSubMorphDrag
>
> So a class can still short-circuit this by
>
> SomeSubclassOfMorph>>>>allowsSubmorphDrag
>    ^true
>
> With no bad effects -- all the current code still works!  ;^)
>
> But now one can have various instances support dragging submorphs without having to create a special subclass just to do this.  Just dynamically add (or remove!) a property.
>
> Anyway, this is the kind of stuff I am playing with in the background.
>
> Cheers,
> -KenD
>

I like this Ken. This kind of ideas could really help an end user 
authoring system. Feel free to submit stuff like this for inclusion. All 
we need is to include some method comments, to let people know that this 
is not yet finished, explain the idea, etc.

Cheers,
Juan Vuletich