From: Gijs de R. <gij...@ho...> - 2011-09-02 20:21:29
|
Hi Jörg! I only checked the English manual and did not read it thoroughly (way too much text. I got my (aerospace engineering!) study books last week and I decided that I should save my eyes/mind for the millions of pages (those books are way too heavy!) that I'll have to read the upcoming five years :P). Some comments though: What I miss:a link to the forum, for further support (when the wiki/manual are not sufficient).an index that can be viewed anywhere on the page. Right now it's just at the top of each "chapter". I don't want to scroll up, just to skip some subjects. Maybe a dropdown list from the main menu? Or some Adobe Reader-like sidebar. Just thinking out loud here ;)most screenshots have no description. As an user I'd like to know the name of the aircraft I'm seeing; so I can launch it up in FlightGear!capital consistency in enumerations. If your second point starts with a lower font, the third should as well. A good example can be seen under "Takeoff" at http://www.emmerich-j.de/Handbuch/EN/4_Solo.html 1,4,5,6 start with a capital letter, while 2 and 3 don't.would be nice if clicking an abbreviation doesn't bring you to a long list, instead show a little popup/hover explaining the abbreviation. Typos/faults/mistakes I found:at http://www.emmerich-j.de/Handbuch/EN/2_Install.html the image description is Deutsch :)links to the wiki link to German articles. For example: http://www.emmerich-j.de/Handbuch/EN/B9_Features.html#mozTocId507437the appendix doesn't list all the contributors. Better list none then some IMO. Rather than giving an incomplete list of "The following individuals have contributed to the scenery object database" you might link to the authors page of the database. What I am worried about:Altough I really like this manual, I have some worries on how you'll keep it up to date. As we see at the wiki, it's very hard to keep up with FlightGear's pace. And that's on a place anyone can edit easily...Your version is much more up to date than the current manual, but I wonder if that's just because you spend so much time on writing it (I guess you won't spend that much time updating it on every release). If this doesn't end up being used as an official manual in the base package, do consider copying stuff to the wiki. You've got some subjects that aren't covered there as of yet ;) Thanks a lot for the hardwork! It's really appreciated (I do at least)! I'm sure we'll be able to use most of it (if not all) in some way or another! Cheers,Gijs |