[Coco] nitrOS-9 documentation

Frank Pittel fwp at deepthought.com
Tue Jul 5 09:13:59 EDT 2005


The problem is that there isn't much available to read. While "hacking"
away at a problem might work in some situations it is a non-starting
solution in another. One of the things that I commonly see in the
documentation that I have for nitros and other software for it is the
passing comment to edit a file. That sounds easy enough until one goes
ahead and fires up edit. The poke at it until you figure out how it works
is a non-starter with edit. :-(

As a unix admin I agree that not every situation can be documented and that
for some things the trial and error approach to solving problems can be a
good learning experience. However there are other times that it can be
dangerous to go plodding through some things with no idea of what you're
doing.

Frank


On Tue, Jul 05, 2005 at 02:18:51PM +1000, Bob Devries wrote:
> You know, a lot of people have said that the OS-9 docs are not for the 
> feint hearted, and yet, it is all most of us have used to get to the 
> knowledge level we are at.
> 
> I believe that persistence, and constant "hacking" at it is the way to 
> learn how it works. I started (way back when OS-9 level 1 came out) by just 
> reading the OS-9 manuals, particularly the tech ref manual, and trying 
> different things until it was working, and most important of all, read, 
> read, read.
> 
> Also, I was never afraid to ask silly questions. :P
> 
> --
> Regards, Bob Devries. Dalby, Queensland, Australia.
> Faith isn't faith until it's all you're holding on to.
> http://e4god.com/freeblogs/bdevries/
> 
> 
> ----- Original Message ----- 
> From: "Frank Pittel" <fwp at deepthought.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Tuesday, July 05, 2005 1:48 PM
> Subject: Re: [Coco] nitrOS-9 documentation
> 
> 
> >On Mon, Jul 04, 2005 at 11:09:17PM -0400, RJRTTY at aol.com wrote:
> >>In a message dated 7/4/05 10:39:30 PM Eastern Daylight Time,
> >>theother_bob at yahoo.com writes:
> >>
> >><<  The lack of NOS documentation is what drove me to work on this in the
> >> first place... I'll get back on it!
> >>
> >> cheers,
> >> Bob >>
> >>
> >>       We need more like you Bob.    Everybody who loves the coco
> >>should try to make a like contribution to the community.   Find a
> >>need and meet it!!
> >
> >I agree completely. After reading Bob's mail I wanted to offer to help
> >until I realized that I was the one asking for the documentation!! :-)
> >It is important that we all remember that writing the documentation for
> >a software application such as nitros-9 is not a very glamorous job while
> >at the same time it's vital to the success of the application.
> >
> >I would like to offer to proof read the documentation. What I offer is the
> >opinion of someone that knows little about nitros-9 but wants to learn. I
> >have found that much of the available documentation is written for people
> >that already have a strong understanding of it. This leaves the newbie 
> >like
> >myself scratching our heads trying to make sense of it.
> >
> >Frank
> >
> >-- 
> >Coco mailing list
> >Coco at maltedmedia.com
> >http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



More information about the Coco mailing list