From: Pistos Christou <jesusrubsyou.5.pistos@...>
Date: 2006-05-17T01:21:44+09:00
Subject: Re: Ruby & Emacs

Eric Armstrong wrote:
> Next, Pistos:
> After many years coding, I became a writer. But I
> still code whenever I can. But the result of the
> writing experience led me to start writing the user
> guide as part of the design process.
>    * Since a project was never really "finished", it
>      was hard to define that point at which I really
>      /should/ write the guide.
>    * When I was coding, a myriad of ideas would occur
>      to me about things the users ought to know. When
>      I wrote at the end of a project, I always had the
>      nagging feeling that I was only recalling a fraction
>      of the things I wanted to say.
> I've used that strategy successfully on several projects.
> The user guide lets people give me feedback on how they
> want to work even before it's written. And you never
> find yourself in that awful position where you've created
> something great, but no one uses it because they can't
> find out how.

Interesting points; thanks for sharing.  I've absorbed them, and will 
change the development process of Diakonos a bit.

I've recently released 0.8.1, and with it, I've begun growing a Diakonos 
wiki: http://wiki.purepistos.net/doku.php?id=Diakonos  At the moment, 
there is a Getting Started page, as well as a larval "Tips and Tricks" 
section which describes some perhaps unobvious features of Diakonos.

I still would like to follow through on the claim/goal that Diakonos is 
(will be) a "usable" editor.  Part of that is making the learning curve 
shallow and the first-impression Ruby-like.

Pistos

-- 
Posted via http://www.ruby-forum.com/.