Hi *,
On Sat, Feb 19, 2005 at 08:36:39PM -0800, Jonathon Blake wrote:
> 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.
No you will keep getting complaints and start over and over again
because nobody tells you what is wrong.
I know did understand that it is not mainly the instructions contained
in the documentation, but the info that is missing from it (the
putty-configuration is not doable without knowledge)
> If a person does not know what the problem is, there is no way to for
> them to say what causes the problem.
? Who else could tell where the problem is if not the user that fails to
succeed?
They can say (as Jean now did) where the problem is. In this case: It is
anything but clear how to configure puTTY.
> > 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.
Because they only know the dos-promt if at all.
> b) Cygwin requires users to learn what is effectively another language.
? Another language?
Klicking the launcher and insert the ssh-command using copy'n'paste is
learning another language?
You don't have to use cygwin to work with it, it is sufficient if you
use it to establish the tunnel.
> 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.
german-lang has references to two commerial solutions. They are about
$100 each. Noone will invest this much money only to set up a tunnel.
Thanks to the description of the problem it gets clear what is lacking.
It is best if those having the problem will write the instructions after
they suceeded.
> > 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.]
Daniel already complained that the documentation would be too long.
> b) Add screenshots for Putty, CygWin, F-Secure, etc.
Screenshots for cygwin? -OK :-)
> c) Cover all potential problems, and their solutions.
You cannot cover all potential problems.
> 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.
No. It is not.
You don't have to know what a "exe" is to klick on it and run the
program.
> Alex wrote:
> >Or use a shell script
>
> which is something that is going to be alien to windows users.
So what?
> ***
> So what you'd end up with is a webpage that says.
>
> Ïnstructions for How to place things in CVS.
This is already an extra-document.
> And that page would have a break down of operating system, and SSH
> programs that are used.
>
> EG:
> [...]
There are no generic instructions per platform. The generic instructions
for all platfrom is: "Set up a ssh2 tunnel forwarding port 2401 to
openoffice.org port 2401"
ciao
Christian
--
NP: Kittie - Do You Think I'm A XXXXX?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
