On 4/8/10, Randal L. Schwartz <
[hidden email]> wrote:
> Back when I was first learning technical writing from some very smart
> people, our mantra was:
>
> The manual *is* the product.
>
> As in, if it's not documented, it *doesn't* exist for the user. And if
> it's a good product but badly documented, it will be *perceived* as a
> bad product.
VERY true.
On a practical level -- which additional basic texts (readMe files,
help pages) do we need to write within the next two weeks for
including into the release 4.1? I am not thinking of long winded
documents but short text snippets containing essential information.
What are the basic questions?
One which quickly comes to my mind (from another thread) is
How do we get additional "stuff" into Squeak? What are the options?
A more specialised question is - how to I prepare an HTML page with
Squeak code to put on my web site and how can people easily load it in
case I do not want to go for squeaksource?
Something like
LoadFromWeb url: '
http://www.mysite.com/aSqueakProgram.html'I assume the answer is there but I do not know it....
Now as Squeak has such a nice MSWindows installer and look right out
of the box it is possible to think of asking regular users of a wider
audience to download and use it.
For example for me it was not obvious how to install Seaside. It
seemed hard. In the meantime I know it and it is straightforward (see
thread 'Installing Seaside' / Metacello). There is even a video which
demonstrates it nicely.
Hannes
Locked
