Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!newsfeed.internetmci.com!EU.net!peer-news.britain.eu.net!sunsite.doc.ic.ac.uk!susx.ac.uk!news.bton.ac.uk!Simon.Shurville
From: sjs16@bton.ac (Simon John Shurville)
Subject: Re: Why is VisualWorks SO complicated? Now also about VW 
 books.
X-Nntp-Posting-Host: tomcat.itri.bton.ac.uk
Message-ID: <DKwtq8.4p2@bton.ac.uk>
X-Posted-From: InterNews 1.0@diamond.bton.ac.uk.
Lines: 14
Sender: -Not-Authenticated-[3206]
Organization: The Composer Project
References: <4ccumk$ldv@news2.ios.com> 
 <4crce7$sl2@newsbf02.news.aol.com>  <DKvEzx.IsI@news.thomson-lcr.fr>
Date: Tue, 9 Jan 1996 10:42:08 GMT
Xdisclaimer: No attempt was made to authenticate the sender's name.

I don't think that the software is SO complicated but the documentation
is the real problem. As soon as you want to step outside the PP
examples you are deep in a cold snowdrift without mittens or boots.
Moreover trying to piece together an understanding of say VisualPart
without clear documentation is just harder than it ought to be. In HCI
they say 'The user should not have to remember something that the
computer already knows.  In VW one might argue 'The programmer should
not have to work out what PP already know.'

I have been trying to collect additional documentation. Trevor Hopkins
and Bernard Horan's 'Smalltalk: an introduction to application
development using visual works' is full of handy tips (a great chapter
on VisualPart) and Simon Lewis  book is great too. Can someone provide
pointers to Tim Howard's books please?

