A manual...

[delley]

Every piece of good software needs a manual. And this is good software, so where is the manual???

And even though a lot of the things is pretty straight forward, it seems to me there is a lot of hidden features that could be used if you only knew about them...

If help is needed to write it. I'd be happy to

delley

[sub]

I you feel the urge to write a manual, I'm sure a lot of users would be happy.

Its on my to-do list, but I dont see me getting to it in the next six months.

[krypton_john]

Typical developer!

[sub]

Hey, I'm not paid to do it, and I dont like writing documents, so why should I?

[delley]

ok sub - I will start work right away...

Which format do you want it in (word, pdf, html)?

How do we organise knowledge transfer? Should I just start writting, and then you can review?

BTW I was thinking that the manual should be an installation and configuration guide, not a "and_click_left_mouse" user guide - agree?

To everybody else - all input is welcome!!!

L8r,

delley

[sub]

Either PDF or HTML would be good. Its probably best to use heaps of screenshots. This means less writing, and most people find it generally easier to understand.

Cheers
sub

[joecru]

Yes Sub,

theres nothing like a diagram to get your info accross.

Regards
Joe

[Jean-Christophe]

Why not a wiki?

[Remco]

Here's another documentation-volunteer.
I think a wiki would be a good start; but i haven't got any experience in setting up one...anybody?

[reven]

i say go with a pdf, they're easy to use, everyone knows how to use it, search is nice, can print the whole thing out with one button, only one file to download etc, wiki is more difficult.