[EMAIL PROTECTED] wrote:
John Meyer wrote:
I guess
the whole moral of this is that if we actually put a detailed
explanation of what happens for a computer user of average knowledge,
we'd fill up a couple of screens.
-
I tend to agree. You have to have a mid-point. You can't have a help
screen for everyone. Sometimes people are going to have to break down
and simply read the manual. The fact that SO many have asked questions
like "My files have been changed to OOo" as if they truly do not
understand about file associations -- that is not an indication of bad
programming or not enough help screens. I believe it is an indication
of the user not bothering to learn enough about his computer. Not only
that, most of the time, if you can find the OOo website, AND you are
able find the proper file to download and install to your computer AND
you can find this forum to ask a question, what is so hard about finding
the User Manuals?
I run across this at work. I give "Avery return address labels" out of
employees and tell them the name and location of the file they need to
print. They call and tell me the file does not exist. I ask them "did
you open up Word and search for the file in correct folder?" After
trying to talk them thru this procedure several times, I leave my office
to find them at their desk. About 1/2 of the time, I have to have them
close Excel and then OPEN UP WORD! The fact that this has happened with
several of the employees several times each (with different Avery
labels) just tells me that no amount of "help" screen will work, nor
will a wizard or any other form of a pop-up. It will be up to each
individual to further his knowledge. Some will go the extra distance to
learn something new. Some will forever wish to be lead around by
leading strings.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I first want to say that I think that it is a wonderful achievement that
something like OO is available to the public. Thank you>
You are right that too much detail would be too much.
However, I think the fact that so many people have a problem with this
issue, indicates that something needs to be done.
I avoid reading the manual, because it is not a "good read"
Part of the problem is the writing itself. For example, some books
published by MS Press put me right to sleep, while others are so well
written, that I could sit down and read them for pleasure.
Another example of a well written technical tome is The Complete PC
Upgrade and Maintenance Guide (various editions) by Mark Minasi. Too bad
he is not in the open source camp.
I broke my first computer, a 486DX clone about a week after a friend
gave it to me. I knew little about computers, but was able to get
crossed linked references in win 3.1 un linked. the book was so well
written, that I sat down and read straight thru the 1000+ pages.
Perhaps its not the quantity of detailed explanation, but the quality of
explanation that is needed. Maybe what is needed is a well turned
phrase. Take a little advice from Stephen King "kill your darlings"
I do not mean to demean anyones efforts. I would be hard pressed to
offer a well written explanation myself.
*
<http://www.amazon.com/exec/obidos/tg/detail/-/0782144314/qid=1138742138/sr=1-4/ref=sr_1_4/002-7527417-0346468?v=glance&s=books>*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
