Quote:
Originally Posted by Uncle Robin
This would be a very useful enhancement. Also, thanks for confirming that, at least on this occasion, I had not missed some feature or functionality. I would have been happy to RTFM if only there were one - the wiki not exactly setting the benchmark for comprehensiveness and/or usefulness.
|
A manual would be awesome, indeed. Much better than the wiki for new users.
The raison d'ętre of the wiki is documenting specific features. Most of these features are quite advanced, like
dictionary support,
keymapping or
gestures.
Also, since KOReader is a very hacked up reader, nobody expects than the average user/contributor/maintainer actually knows (or wants to know) more than 10% of that extra stuff.
Personally I think new users are the best to write end user documentation, if that's something in the scope of the program. I would doubt it sometimes. It was a hacked reader for its author at first. Then others used (and hacked) it.
Mainstream, even in a niche product like aftermarket ebook readers, was never a goal. It was and still is an ebook playground. So no doubt why nobody writes end user documentation. Actual users are more interested in writing code or just use the program to read. After all they all know how to handle the program.
So my approach with the RTFM would be: some new user with genuine interest and a few hours of free time writes glue code on a few topics, and that, paired with some info of the wiki, makes a manual to read. See
my suggestion
Once there's a manual it is way easier for others to tell the manual isn't good enough and suggest changes.
