<br><br><div><span class="gmail_quote">On 7/26/07, <b class="gmail_sendername">Jerome Peace</b> <<a href="mailto:peace_the_dreamer@yahoo.com">peace_the_dreamer@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Morphic! (ans to Jason from previous thread)</blockquote><div><br>[...] </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Spec means speculation and doing something on spec
<br>means you take the responsibility that it might or<br>might not be accepted by the publisher. The other way<br>to do something is on commission where others specify<br>what you are to do but give a garantee that the work
<br>will be of use to them and you will be compensated.</blockquote><div><br>Ah, I see. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As for motivation for morphic work, for me it means<br>the work must be interesting (as defined by my<br>curiosity) lead to something I think elegant in the<br>code and the behavior of the morphs and allow me to<br>learn and grow in my own understanding of squeak,
<br>morphic and things larger.<br><br>You apparently have the curiosity streak as well.</blockquote><div><br>Yes. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So answer me this, and I can better advise you.<br><br>What would you like to learn from reading the<br>"specifications?" you thought I had mentioned?</blockquote><div><br>Wel,l I could figure out where morphic is suppost to go, and if it has arrived.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What would you like to be able to do with the<br>knowledge?</blockquote><div><br>
It would make it easier to refactor morphic, because I feel it would be easier to understand.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Often, instead of specifications, I find it useful to<br>just write down what I want to see squeak do. As<br>vaguely as my initial understanding permits. As<br>briefly as I can fit all my ideas in. And as<br>passionately as the forces of desire inside me wish
<br>for the feature to exist.</blockquote><div><br>I would like to have interfaces. I've looked at smallInterfaces and it looks to me a bit messy. I don't have the understand yet, to write my own.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Oddly, the rest of it is all downhill from there. The<br>specifications become the detailing of the initial<br>statement. The code comes from implementing pieces of<br>the details, testing them and proving they work. The
<br>fun comes when the coding process leads to something<br>unexpected and the detail or even the original<br>statement becomes worth rewriting. Incremental design<br>benifits the designer by educating him all along the<br>
way. (Look on the web for articles about McReadys<br>gossamer condor.)</blockquote><div><br>I see your point. It that when you are just starting, it helps to know where you are trying to go. <br><br>Reading the SELF paper on Morphic, I now have a better idea what morphic is about.
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Anyway thanks for your response and request. Its been<br>fun writing this.<br>
</blockquote></div><br>Thank you also. Sorry for the delay. I found it after I did a search.<br><br>Regards,<br> Jason <br>