Actually, I think that the optimal way to learn ST is to combine 
learning about the existing library and writing your own code for your 
own problems at the same time. There are a number of books that will 
teach you about the most important of the existing classes.

So go ahead, try your own solutions, and the same time learn about 
what experience has proved to be good approaches, and compare this 
with your own solutions.

Ivan


> >>>>> "Ken" == Ken collins <bibsybabs at hotmail.com> writes:
> 
> Ken> Maybe if I knew ST as well as I'd like, I would have known which Ken>
> non-queer methods to use and not have needed to ask. I didn't Ken> find
> any that did exactly what I wanted, so I started some of my Ken> own. I
> have heard that the best way to learn ST is to just jump Ken> in and start
> coding. How long should I refrain from creating my Ken> own methods?
> 
> You can create your own methods, but as a beginner, you should think
> LONG and HARD before adding methods to any of the existing system
> classes.  In fact, the Squeak license requires any such method to be
> put up on a public webserver or submitted to the Squeak team for
> inclusion in a future release.
> 
> Consider this - most of those classes have been around for 20 years
> now.  Do you really think you have thought of something unique to do
> to an Array that hadn't been done in the prior 20 years? :)
> 
> -- 
> Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
> Keywords: Perl training, UNIX[tm] consulting, video production, skiing,
> flying Email: <merlyn at stonehenge.com> Snail: (Call) PGP-Key: (finger
> merlyn at teleport.com) Web: <A HREF="http://www.stonehenge.com/merlyn/">My
> Home Page!</A> Quote: "I'm telling you, if I could have five lines in my
> .sig, I would!" -- me
> 



Ivan Tomek,

Jodrey School of Computer Science
Acadia University
Wolfville,
Nova Scotia, Canada, B0P 1X0

fax: (902) 585-1067
voice: (902) 585-1467