<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13.0208px; border-collapse: collapse; color: rgb(51, 51, 51); ">>"Direct manipulation doesn't quite get you the code (in<br>the way Interface Builder does.)"</span><br>
<br><div>Actually that is pretty much what IB was doing in the beginning ... :D It instantiates the objects and then archives them.</div><div><br><div class="gmail_quote">On Wed, Mar 30, 2011 at 6:44 PM, David Corking <span dir="ltr"><<a href="mailto:lists@dcorking.com">lists@dcorking.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Jason,<br>
<br>
On Tue, Mar 29, 2011, Casey Ransberger wrote:<br>
> WRT Morphic and direct user interface construction: this isn't fantasy. You<br>
> can actually do this today, as it was one of the original drivers for the<br>
> system when it was conceived in Self, as an evolution of Randall Smith's<br>
> Smalltalk based Alternate Reality Toolkit (ARK.)<br>
<br>
I agree with Casey: it is not fantasy.<br>
<br>
However, with Squeak / Pharo, direct manipulation gets you _instances_<br>
of morphs. To fit the Smalltalk programming paradigm, you need a class<br>
and methods (at least a drawOn: method, but probably some event<br>
handlers too.) Direct manipulation doesn't quite get you the code (in<br>
the way Interface Builder does.)<br>
<br>
But ...<br>
<br>
(1) You can probably figure out the code using an inspector and a<br>
little arithmetic.<br>
<br>
(2) Morphic Players get real Smalltalk code behind them that you can<br>
see in your changeset browser.<br>
<br>
(3) Have you seen this yet?<br>
<a href="http://www.jarober.com/blog/blogView?showComments=true&printTitle=ST_4U_53:_Introducing_the_Morphic_UI_Designer&entry=3476333796" target="_blank">http://www.jarober.com/blog/blogView?showComments=true&printTitle=ST_4U_53:_Introducing_the_Morphic_UI_Designer&entry=3476333796</a><br>
<font color="#888888"><br>
David<br>
<br>
</font></blockquote></div><br></div>