Christian wrote:
> Don't take this personal, but people always complain "this is to complicated"
> but usually don't tell what exactly causes the trouble.
If that happens, then the only thing to do is to throw out the entire
document, and rewrite it from scratch. And keep repeating that
process, until people can understand it.
If a person does not know what the problem is, there is no way to for
them to say what causes the problem.
If, after the fifth rewrite, the same complaint occurs, fire
_everybody_ who is connected with the writing of that documentation.
And repeat that process until that documentation is clearly
understandable by your great aunt Martha.
> When using cygwin, you have all the comfort that a unix-shell offers.
a) For most Windows users, "Unix shell" and "comfort" are mutually
exclusive terms.
b) Cygwin requires users to learn what is effectively another language.
I will grant that OOo is FLOSS, and FLOSS solutions are the preferred
way to do things. It would be useful if it at least listed, if not
described other SSH programs --- at least the two or three most
commonly bought ones. I will grant that most people who bought an SSH
program probably don't know that they did so.
> But how can the documentation be any simpler than it is now, explaining and
> mentioning each single step?
a) Add a detailed glossary.{Define _every_ word that contains more
than one glyph. Have at least three examples, as well aas a
definition, for _every_ listing in that glossary.]
b) Add screenshots for Putty, CygWin, F-Secure, etc.
c) Cover all potential problems, and their solutions.
d) One tool per webpage, and everything related to that webpage is on
that webpage.
>You don't have to know to set up your system.
That is completely, utterly, and absolutely inane.
You are asking users to install something that they have never heard
of before, in a system that they may, but probably don't understand.
And doing all that in terminology that is foreign to them.
>How can one have trouble following this instructions?
Because what you describe should be happening at that point does not happen.
Alex wrote:
>Or use a shell script
which is something that is going to be alien to windows users.
***
So what you'd end up with is a webpage that says.
�nstructions for How to place things in CVS.
And that page would have a break down of operating system, and SSH
programs that are used.
EG:
Windows
F-Secure
Putty
generic_instructions_for_this_platform
Macintosh X
name_of_program
generic_instructions_for_this_platform
Macintosh 9.0
name_of_program
generic_instructions_for_this_platform
Unix & Linux
SSH
generic_instructions_for_this_platform
BSD
name_of_program
generic_instructions_for_this_platform
OS/2
name_of_program
generic_instructions_for_this_platform
Generic instructions for other platforms.
generic_instructions
- - -
And each tool would be a link that covered how to commit something to
CVS using that tool.
xan
jonathon
--
Want a Gmail account?
send me a request.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
