Dear Dimitri,
>>>> As you may have gathered by my sudden appearance on this forum, I have been >>>> setting up doxygen 1.8.4 on my code base (this is actually a second attempt >>>> to get doxygen into the workflow). >>>> >>>> I have pretty much beaten doxygen and my code into some sort of general >>>> agreement and now have a reasonably clean build of doxygen. I must commend >>>> Dimitri on the improvements in the look of the generated site since about >>>> 1.6. It is very nice. One excellent feature is the navigation tree. >>>> After >>>> some experimentation, I have managed to get our \pages into a bit of a >>>> hierarchy such that we now have the beginnings of a Programmer's Manual in >>>> addition to the doxygen generated Reference Document. >>>> >>>> One pretty big problem I am having however is the amount of time to load a >>>> page. When I click on a link in the Classes part of the tree, it takes >>>> about 8 seconds for the page to load (1 Mississippi, 2 Mississippi...). If >>>> I click in the "Programmer's Manual" section (i.e. my hierarchy of >>>> \subpages) it loads instantly. >>>> >>>> I tracked this down via the Firefox profiler to navtree.js showNode. >>>> Actually the real culprit is getNode. >>>> >>>> As you might guess, the project I am documenting is enormous. I am sure >>>> the >>>> issue is looping over the data structures for the tree. From what I can >>>> tell from single stepping, I think it starts suffering when it gets to the >>>> dynamic bits of the tree (rather than the static NAVTREE). >>>> >>>> I do notice that this seems to be limited to Classes. If I click on a >>>> Files >>>> link, it is pretty fast. I assume this is because the Files tree nodes are >>>> subdivided by the directory structure they mimic and thus are smaller. >>>> >>>> The only thing I can do to reduce the problem is to split the doxygen >>>> output >>>> up into smaller sections. However I am loathe to do that because one of >>>> the >>>> most powerful aspects of doxygen is the global dependencies it generates >>>> that let you see the "big picture". >>>> >>>> >>>> Any other things to try? >>> >>> You could try Chrome, it is faster at Javascript processing. >> >> Ah, that is something indeed to try. >> >> >> >>> I still have to look into a way to allow the browser to fully load and >>> render the >>> page and only then expand the dynamic part of the tree view. >>> That way a processing delay is much less annoying. >> >> I see. I was wondering also about some sort of directive to make doxygen >> "tree-ify" that list in some fashion or another (alphabetically, by some >> user defined module grouping, etc) so your script would not need to loop >> over such a monster list. > > If you would group classes into namespaces, then that would indeed help. > Doxygen makes separate files for each level in the tree and loads them on > demand. Ahh. We have just switched over from a much older compiler that was not really savvy with namespaces so we are all in the global space now. But knowing this is an impetus to change that. > Since you are using Windows, another thing you could look into is disabling > the > tree view and use HTML help compiler to compile the HTML into a .chm file, > which includes a navigation tree and search function. > See http://www.doxygen.org/manual/config.html#cfg_generate_htmlhelp Great idea. I will look into it. Thanks. All the best, Tom ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
