Re: [colorforth] RFC: Primary ColorForth

[Eric Lindahl <lindahl@xxxxxxxxxxxxxxxxxxxx>]

Jeff,

Good work Jeff Fox.  Your description of the editor is so complete, in a 
programming sense, that it can stand alone.

I still remember my struggle with the editor when I first got my CM color 
forth running.  A wonderful bunch of surprises.  Since I have some 
familiarity with other Fourths, I fairly easily accepted the simplicity 
and *no* fatness of the design.  Once it was demonstrated that I could do 
OK without using the Enter key, etc. etc., I was thrilled.

The point of my note is that someone new to the minimalist philosophy of 
color forth could be aided in their leap by the addition of a one or two 
paragraph introduction about the whys of the differences from traditional 
editor's , or about the advantages of use.  Something which answers the 
immediate question: "Why should I bother learning yet another editor?" or 
just "What the???".

Adding that intro, in my opinion, would help the reader formulate a 
mental picture of the editor upon which your existing text's detail would 
naturally fall.

So I have suggested a little task that someone might undertake.  I don't 
feel qualified to do that but I might be able to provide a 
minimalist paragraph for you to consider placing there.   I am qualified 
in one sense...  I remember my first trials at forming a mental picture of 
the CM color forth editor.

I would not feel slighted if someone else wanted to take this on.

Thanks all, eric-


On Fri, 21 Jul 2006, Jeff Fox wrote:

> initial colorforth editor page in simple html with jpegs
> http://www.ultratechnology.com/editor/editor.htm
> zip file
> http://www.ultratechnology.com/editor/colorforth editor chapter.zip
>
> it doesn't go into how blocks are just 1k aligned pages of ram
> or that block 0 is ram 0
> or that they are 256 words in colorforth addressing
> or that BLOCK and BLOCKS do the same thing, 256 *
> or that nc 18 block cyl get loaded at boot
> or that the first cyl is the boot sector, kernel, font
>
> or get into how to write programs, it just goes over the
> keyboard menus, functions in the editor, and some related
> command line functions.
>
> maybe next I should do a chapter on how to do file IO
> using the utility word "file" "reads" "writes" "stop"
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
> Main web page - http://www.colorforth.com

--


---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com