Date: Mon, 23 Dec 2002 08:13:36 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com Subject: Re: dynamic gotos possible with djgpp? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 22 Dec 2002, Lars O. Hansen wrote: > FAQ: too much in one file: web browsers scrollbar is tiny; difficult to > move up and down You should use the Info version. Not only is it free of this drawback, but Info readers have advanced search methods that HTML browsers lack. See the description of the index search in the README.1ST file for details. > The FAQ's content is actually quite good, but the name FAQ doesn't suggest all the content which can > be found in the FAQ, so it should perhaps renamed to sth. like "djgpp Usage reference" (not thought > about that name)? I think the name FAQ is okay, since the document is actually constructed by reading questions on this news group. It's true that some of the stuff there should migrate to some other document, but no one has stepped forward and volunteered to write such a document. It's IMHO better to have the material in the FAQ than nowhere at all. > projectct overview shortcomings: too much on 1 html page! I'm not sure what you mean: that document is divided into chapters and sections, so ``1 html page'' sounds like some kind of misunderstanding. > the web version is too much interdivided!! (each 0.1 on one page That's so the load time is faster. Not everyone is connected to a T1 backbone, you know; there are people around the globe sitting behind a 33K modem. > GNU manuals: coming from Ms world, one has no idea > what gnu is and what djgpp has got to do with it The overview of the DJGPP project should explain some of that. > overall problem: too much information, the docs don't get to the point > fast enough; one doesn't know where to reliably find the information > one needs. There's an explanation of this in README.1ST, if you read far enough. > but from the readme it looks as if one > has to know the info file one wants to read and that one has to learn > its keyboard navigation interface. There are more than one Info reader. There's one in RHIDE, another one in Emacs. Those two are more GUI oriented, and still have the advantages of the Info system, like trhe index search (that's the most efficient means of finding information quickly). > If it needs pure keyborad navigation and if it doesn't lay out the > whole doc structire clearly before me The main menu shows that structure. Please spend some time reading some large Info document, such as the GCC manual, before jumping to conclusions.