Nikolay Metchev | 2 Aug 2005 11:31

Firefox performance

Is there anything that could be done to the HTML output of doxygen to improve performance on Firefox?
 
On projects with lots of source code doxygen seems to generate JavaScript which makes Firefox struggle.
 
Here is the bug report in mozilla:
 
That bug report suggests one improvement comment 6. But perhaps a rework of the html is more desirable?
Ethan Tira-Thompson | 6 Aug 2005 23:31
Picon

suggestion: latex formula tags (f$,f[,f{) should imply verbatim

It's really annoying when you try to do stuff like this:
/*!
   <at> brief Delta torque due to delta joint position.
  This function computes \f$S_2(q, \dot{q}, \ddot{q})\delta q\f$.
*/

but that "\dot" in the formula causes doxygen to complain:
Warning: reached end of file while inside a dot block!
...and then the documentation gets hosed.

I don't know how best to fix this -- if I try to manually stick 
\verbatim in the fomula:
/*!  \f$\verbatim S_2(q, \dot{q}, \ddot{q})\delta q\endverbatim\f$  */
then somehow latex gets ahold of the verbatim tag and has throws its own 
error.  So perhaps the formula is already verbatim, and just the \dot 
command is getting through somehow?

Anyway, a work around would be nice if I'm missing something.

Thanks
 -ethan

PS I just updated my patch for bug 162968 to work with 1.4.4:
  http://bugzilla.gnome.org/show_bug.cgi?id=162968
If there's any feedback on that, I'm the one to talk to, though probably 
should do it through the bugzilla page.

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Michael McTernan | 7 Aug 2005 22:24

RE: suggestion: latex formula tags (f$,f[,f{) should imply verbatim

Hi there,

This is listed as a bug in Bugzilla too:
http://bugzilla.gnome.org/show_bug.cgi?id=304339 

I wondered if a possible workaround would be to use the LaTeX \newcommand
option to alias \dot to something that Doxygen won't pick on.  The
\newcommand directive can be placed in some file that is then referenced
from the Doxygen input file using the EXTRA_PACKAGES, or it may be enough to
put it in a \latexonly ... \endlatexonly block. 

Alternatively from Bugzilla, it looks as though Dimitri is planning to fix
it by the next CVS update.

Regards,

Mike

> -----Original Message-----
> From: doxygen-develop-admin <at> lists.sourceforge.net [mailto:doxygen-develop-
> admin <at> lists.sourceforge.net] On Behalf Of Ethan Tira-Thompson
> Sent: 06 August 2005 22:32
> To: doxygen-develop <at> lists.sourceforge.net
> Subject: [Doxygen-develop] suggestion: latex formula tags (f$,f[,f{)
> should imply verbatim
> 
> It's really annoying when you try to do stuff like this:
> /*!
>    <at> brief Delta torque due to delta joint position.
>   This function computes \f$S_2(q, \dot{q}, \ddot{q})\delta q\f$.
> */
> 
> but that "\dot" in the formula causes doxygen to complain:
> Warning: reached end of file while inside a dot block!
> ...and then the documentation gets hosed.
> 
> I don't know how best to fix this -- if I try to manually stick
> \verbatim in the fomula:
> /*!  \f$\verbatim S_2(q, \dot{q}, \ddot{q})\delta q\endverbatim\f$  */
> then somehow latex gets ahold of the verbatim tag and has throws its own
> error.  So perhaps the formula is already verbatim, and just the \dot
> command is getting through somehow?
> 
> Anyway, a work around would be nice if I'm missing something.
> 
> Thanks
>  -ethan
> 
> PS I just updated my patch for bug 162968 to work with 1.4.4:
>   http://bugzilla.gnome.org/show_bug.cgi?id=162968
> If there's any feedback on that, I'm the one to talk to, though probably
> should do it through the bugzilla page.
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Doxygen-develop mailing list
> Doxygen-develop <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Kevin McBride | 8 Aug 2005 04:51

Another RPM Server

Hello everyone.

I'd like to tell everyone about my server that is hosting doxygen RPMs. 
  All RPMs on my server were built by me.  It's address is currently:

http://66.24.29.1/

You'll find doxygen RPMs for the i386 and the i686 platforms, as well as 
the source tarballs.  I hope my server gets added to the doxygen RPM 
list to make things more convenient to newbies.

I will also make RPMs for doxygen as new releases of doxygen come out, 
and keep releases as old as the current release (1.4.4) available to the 
general public.

- KJM

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Dimitri van Heesch | 11 Aug 2005 15:16
Picon
Favicon

Re: Firefox performance

On Tue, Aug 02, 2005 at 10:31:33AM +0100, Nikolay Metchev wrote:
> Is there anything that could be done to the HTML output of doxygen to
> improve performance on Firefox?
>  
> On projects with lots of source code doxygen seems to generate
> JavaScript which makes Firefox struggle.
>  
> Here is the bug report in mozilla:
> https://bugzilla.mozilla.org/show_bug.cgi?id=218308

Interesting!

> That bug report suggests one improvement comment 6. But perhaps a rework
> of the html is more desirable?

For quite some time (i.e more than 2 years) doxygen uses a completely 
different way of producing the tree view. Doxygen now generates all output 
in HTML form and uses a single Javascript function to toggle opening and 
closing of folders. So any performance issues mentioned in this bug
report do not apply anymore!

Regards,
  Dimitri

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Nikolay Metchev | 11 Aug 2005 15:23

RE: Firefox performance

Dimitri,

I am using the latest version of Doxygen 1.4.4 and the latest version of
Firefox 1.0.6 in Windows XP SP2. And I am still finding that IE (version
6) outperforms firefox by far. Do you have any clue why this is? This is
only really apparent on a large project. 

Nikolay

-----Original Message-----
From: Dimitri van Heesch [mailto:dimitri <at> stack.nl] 
Sent: 11 August 2005 2:16 PM
To: Nikolay Metchev
Cc: doxygen-develop <at> lists.sourceforge.net
Subject: Re: [Doxygen-develop] Firefox performance

On Tue, Aug 02, 2005 at 10:31:33AM +0100, Nikolay Metchev wrote:
> Is there anything that could be done to the HTML output of doxygen to 
> improve performance on Firefox?
>  
> On projects with lots of source code doxygen seems to generate 
> JavaScript which makes Firefox struggle.
>  
> Here is the bug report in mozilla:
> https://bugzilla.mozilla.org/show_bug.cgi?id=218308

Interesting!

> That bug report suggests one improvement comment 6. But perhaps a 
> rework of the html is more desirable?

For quite some time (i.e more than 2 years) doxygen uses a completely
different way of producing the tree view. Doxygen now generates all
output in HTML form and uses a single Javascript function to toggle
opening and closing of folders. So any performance issues mentioned in
this bug report do not apply anymore!

Regards,
  Dimitri

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Dimitri van Heesch | 11 Aug 2005 16:06
Picon
Favicon

Re: Firefox performance

On Thu, Aug 11, 2005 at 02:23:04PM +0100, Nikolay Metchev wrote:
> Dimitri,
> 
> I am using the latest version of Doxygen 1.4.4 and the latest version of
> Firefox 1.0.6 in Windows XP SP2. And I am still finding that IE (version
> 6) outperforms firefox by far. Do you have any clue why this is? This is
> only really apparent on a large project. 

I don't, so this may be seen as a different mozilla bug.

All I know is that the tree.html file can become quite large (the one for
doxygen own sources is already 300k), so this takes time to read and process. 
Maybe IE sees that all sections are hidden initially and does less 
processing in this case, but that's is just wild speculation...

I can't think of anything to make this faster however.

Regards,
  Dimitri

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Peter A. Kerzum | 16 Aug 2005 01:59
Picon

A way and place to modify internal program model

Greetings, doxygen developers!
Pleased to meet you here :) I'm new to this list, so please accept my excuses 
for potentially stupid questions :)
So, here's the thing that brought me here. I develop C++ and I like doxygen 
much for a pretty nice UML-like models it draws (especially with dot). But 
C++ modeling lacks one very important feature - consider following code:

class A { /* ... */};
typedef A A_alias;
class B { A_alias a; };

The collaboration diagram for B will not represent any usage of A, while it is 
obvious on the language side. While one might argue against aliasing, it is 
quite common while using STL, e.g.:

#include <vector>
class A { /* ... */ };
class B
{
	typedef vector<A> storage_t;
	storage_t storage;
};

So some time ago I implemented this feature by adding additional pass over 
entire model just after model is finished, but before any output generation. 
For each typedef that pass created a class with the same name and added a 
usage link to the real type. Unfortunately my implementation was so weird 
that I erased all the code I've written as soon as I made it up.

So, what I want to say is that this is quite handy feature that will help 
reverse analyzing a lot. And I would like to provide consistent 
implementation, but for that purpose I'll possibly require a bit of your 
attention. So, could you please point me the place to put this kind of code? 
I suppose parsing phase is more appropriate than additional loop, and I think 
that it might be more consistent way to extend typedef representation a bit 
and then extend typedef interpretation by graph subsystem.

Well, finally I am looking forward to receiving any guidelines from you.
Thanks in advance :)

--

-- 
Best Regards,
Peter A. Kerzum

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Nikolay Metchev | 16 Aug 2005 19:13

RE: Firefox performance

It turned out they were not aware of the problem. I have created a new
bug and the mozilla people seem to have responded by creating 3 new bugs
to fix it:
https://bugzilla.mozilla.org/show_bug.cgi?id=304683

It might be a while before they fix it.... 

-----Original Message-----
From: Dimitri van Heesch [mailto:dimitri <at> stack.nl] 
Sent: 11 August 2005 3:07 PM
To: Nikolay Metchev
Cc: doxygen-develop <at> lists.sourceforge.net
Subject: Re: [Doxygen-develop] Firefox performance

On Thu, Aug 11, 2005 at 02:23:04PM +0100, Nikolay Metchev wrote:
> Dimitri,
> 
> I am using the latest version of Doxygen 1.4.4 and the latest version 
> of Firefox 1.0.6 in Windows XP SP2. And I am still finding that IE 
> (version
> 6) outperforms firefox by far. Do you have any clue why this is? This 
> is only really apparent on a large project.

I don't, so this may be seen as a different mozilla bug.

All I know is that the tree.html file can become quite large (the one
for doxygen own sources is already 300k), so this takes time to read and
process. 
Maybe IE sees that all sections are hidden initially and does less
processing in this case, but that's is just wild speculation...

I can't think of anything to make this faster however.

Regards,
  Dimitri

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Robert G. Ristroph | 18 Aug 2005 20:27

How Doxygen uses graphviz -- links in html graph presentation


Hi,

    I would like to use graphviz to make graphs on a web page similar to the way
doxygen does (but I'm not parsing source code to make them, these are graphs of
other things).

    I want the nodes of the graph to be links, the way doxygen does.  I can see
that in the html output doxygen specifies certain areas of the graph image as
clickable, but I was wondering where in the source code of doxygen it figures
out what coordinates are associated with each node.

    I would like to look at doxygen to see how it is done, but I am having
trouble finding it.  If anyone could tell me where that functionality is in the
code, or how to achieve that result another way, or another example to look at,
I would really appreciate it.

    Thanks in advance for any help you can offer me.

--Rob

--

-- 
Robert G. Ristroph
Airlink Systems
rristroph <at> airlinksystems.com
(512) 231-1240 x103

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Gmane