Praise: Rev Documentation to the rescue

[Jon]

"Oh dear, oh dear oh dear! What is it with people and the docs? The docs 
work perfectly well when you know where to look for information."

If I knew what a facility's name was, or even whether such a facility 
existed, I would be most of the way there.  The fact is that most 
newbies have no clue about any of this.  Saying the "docs work 
perfectly" misses most of the point.

For me, the biggest problem I have with the docs, aside from not being 
able to find things, is that when I get to a topic, there are not enough 
examples to indicate exactly how a facility might be used.  Whether this 
belongs in the "docs" or in something else is beside the point.  If I'm 
struggling with how to use a REPEAT, I need examples.

:)

Jon


Michael J. Lew wrote:

> Oh dear, oh dear oh dear! What is it with people and the docs? The 
> docs work perfectly well when you know where to look for information. 
> That may not always be immediately obvious, but I think that some 
> don't spend enough time looking at the arrangement of the information 
> before they claim the docs are too hard, or a bottleneck.
>
> In Rev it is very easy to experiment with commands to see how they 
> work. Try it.
>
> In Rev it is fairly easy to guess what a command might be. Just try it 
> out and see if it works. If it doesn't then type it into the 
> dictionary filter and see what comes up.
>
> This list is part of the effective documentation of Revolution (look 
> up "effective" keyword in the dictionary ;-). Ask a question here and 
> you will generally get a useful answer.
>
> Don't try to tell me that Rev is not good for non-professionals. This 
> list is full of non-professionals who are making good things with it.
>
> Regards,
> Michael Lew
>
> At 2:29 PM -0500 25/7/05, use-revolution-request at lists.runrev.com wrote:
>
>>
>> But Rev is advertised as "enterprise-ware" if I'm not mistaken. In
>> theory, Rev is great for pros, great for novices, and great for
>> do-it-yourself end-users, who possess a modicum of intelligence,
>> motivation and computer experience.
>>
>> Maybe it's fine for Pros, but it's too damned hard for everyone else.
>> The documentation presently available is the biggest bottleneck, in
>> my opinion. It still seems to me that it just wouldn't be that hard
>> or expensive to make it a whole lot better.
>
>