<DIV>
<DIV>Being the newbie the Lex refers to below I can only say that he states the case well from my perspective. </DIV>
<DIV> </DIV>
<DIV>One of the touted aspects of smalltalk is how you can modify your environment and indeed the SM image. Well, I'm an old newbie with some experience with other languages and environments. So now I hit SM and am told "oh yeah, just go in and modify the SYSTEM, create this, and create that, and just start stuffing things into the image. If you don't like it then move it, go to the changeset or whatever...there are alternatives. Of course this is a very power capability, but I rather minimize time undoing and maximize time doing, as any of us would.
<DIV> </DIV></DIV>
<DIV>But if I get cute and start putting new subclasses, etc., under different categories and classes without a modicum of understanding (which comes only with experience) I could really make a mess of the image. For example, be it bad practice or whatever, in my first dalliances with Squeak I tended NOT to create new classes but to extend the existing ones. For example adding some statistical methods to Collections. It just seemed natural to do it that. But this soon made me uncomfortable--because I would never easly undo all the changes I might sprinkle thru the system--changeset or not. So you see, I needed some people like Lex, Dan, and Richard to give a little advice. Lex went a little further and sort of said 'people like you need a place to play, while you SORT things out.' </DIV>
<DIV> </DIV>
<DIV>Learning SM is like anything else--there is a good deal of bootstrapping involved. But first you gotta find the laces. </DIV>
<DIV> </DIV>
<DIV>Lex makes some good arguments.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Michael Grant</DIV>
<DIV> </DIV>
<DIV><BR><B><I>Lex Spoon <lex@cc.gatech.edu></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">ducasse <DUCASSE@IAM.UNIBE.CH>wrote:<BR>> I'm not convinced that this is different that any other class in the <BR>> system.<BR>> Why this empty would help. I doubt about that.<BR><BR><BR>Let me first repost my earlier message, from the thread "Documentation,<BR>more, more" back in September:<BR><BR><BR>//---------------------------------------------------------------------\<BR>\<BR>"mwgrant2001" <MWGRANT2001@YAHOO.COM>wrote:<BR>> I ENVISION MYSELF FALLING INTO A WOODY ALLEN-ESQUE NEUROTIC <BR>> PARALYSIS, UNABLE TO ACT ON ANY MATTER AS I WORRY OVER WHERE TO PUT <BR>> ANY CLASSES I MIGHT DEVELOP! <BR><BR>I wouldn't have thought of that particular problem. Perhaps we should<BR>add an empty category to the browser and put it at the top of the list. <BR>It could be called something like "Sandbox". Every little bit that can<BR>be shaved off of the initial user experience
is helpful.<BR><BR>Okay, I've programmed it. It's in my next message.<BR>\\---------------------------------------------------------------------/<BR>/<BR><BR><BR>The basic idea is to let people make decisions in whatever order they<BR>like. I hate the break in flow that comes in Squeak when I am forced to<BR>name a class and put it in a category before I can do anything with it. <BR>Sometimes my thought is simply "I want an object holding a Foo and a<BR>Bar". If it's the first class in a project, then I have to think up a<BR>category name as well. If there is a Sandbox category available, I can<BR>simply stick everything in there until I am ready. Similarly for the<BR>class and methods.<BR><BR>For newbies, like the person I responded to, the situation is even<BR>worse. Every step is harder for a newbie, and every step shaved is a<BR>significant saving.<BR><BR>Tutorials should be benefited as well. Now they have the option of<BR>telling people to stick code right into the Scratch
class instead of<BR>having them open a browser, do "add item", create a class, etc. That's<BR>a lot of little steps when you stop and consider it!<BR><BR>Finally, to help your intuition, please consider what Squeak should look<BR>like if we consider code as the document and the browser as an<BR>application that edits that document. In most such software, the editor<BR>starts up viewing a scratch document where users can immediately start<BR>scribbling. Consider word processors, spreadsheets, drawing programs,<BR>music notation generators, movie editors, .... Consider these programs<BR>both with and without an automatic scratch area, and I think you'll<BR>agree that it is nice to have an automatic scratch area pop up when you<BR>start the program.<BR><BR><BR><BR>Lex Spoon<BR></BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
Exclusive Video Premiere - <a href="http://launch.yahoo.com/video/?1093432&fs=1&redirectURL=http://launch.yahoo.com/promos/britneyspears/">Britney Spears</a>