On 10.01.2011 18:02, Albrecht Schlosser wrote: > MacArthur, Ian (SELEX GALILEO, UK) wrote: >> >>> Just thought you should know that the file main.html is >>> missing from the RC3 documentation tarball. >> >> Yes - this one is a puzzle to me: >> >> - In the fltk-1.1 docs, the entry point was index.html. >> >> - in the 1.3-rc2 tarball docs the entry point was main.html. >> >> - in the 1.3-rc3 tarball docs the entry point is index.html. >> >> >> Fluid in 1.3 expects to find main.html, whilst fluid in 1.1 looks for >> index.html. >> >> So, um... What's going on with this? >> >> I'd guess that index.html is the "natural" place for the docs to start, >> why did we change it to main.html? And what has it (partly) changed >> back? > > I'm in a hurry, so this is only quick and short answer and needs to > be checked (will do later). > > I think that ... > > - main.html is the non-frame version (see online docs). > - index.html is the version with frames (see online docs). > - rc2 was probably wrong, since it may have had the non-frame docs (only). > - 1.1 was different (you know). > - fluid and help-view should probably use the non-frame version.
Checked. It's not a bug, it's a feature ;-) Doxygen 1.7.3 (the version Matt used to generate the docs) uses a new HTML technique to create the html layout with frames. This looks much better than before (IMHO), but there's no "embedded" non-frame layout. All pages include the frames, and therefore main.html is missing. Personally I don't like the new inheritance graphics (since doxygen version 1.5.8 or 1.6 - compare with the still older online docs), but I see that the new layout is much better and we should use it. Thus, we shouldn't bother to provide a main.html file, but rather add a sample html page for the html viewer test (as Greg volunteered to do already) and add appropriate browser links where needed. I don't know what to do with fluid, but I think that fluid should probably use an external browser for its docs as well. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
