headers
David Wilson | 15 Jun 2005 05:56
Picon

[PATCH] Word wrapping long class names in DOT diagrams

I have noticed that when using the doxygen-generated inheritance
diagrams and collaboration diagrams, class names are always drawn on a
single line.  This can lead to needlessly large diagrams (4000+ pixels
wide) if you have a C++ class with several template arguments, for
example.

The following patch to doxygen 1.4.3 solves this problem for many of the
cases I tried, by trying to word-wrap the class name once it exceeds 30
characters.  Line breaks are inserted after space or comma.  The same
line-breaking method will also be used for arrow labels. 

One inheritance graph (for a template class instantiated with 8 template
parameters) went from 4010 to 979 pixels width after this patch and is
much more readable.

Also, this patch corrects a small bug with collaboration diagrams.  When
multiple member variables have the same type, this was showing up in the
collaboration diagram as "m_one\nm_two\nm_three" next to the dashed
purple arrow, rather than showing "m_one", "m_two", "m_three" on
separate lines.

Regards

Dave

diff -ur doxygen-1.4.3.orig/src/dot.cpp doxygen-1.4.3/src/dot.cpp
--- doxygen-1.4.3.orig/src/dot.cpp      2005-04-18 02:55:55.000000000
+1000
+++ doxygen-1.4.3/src/dot.cpp   2005-06-14 12:41:17.000000000 +1000
 <at>  <at>  -561,15 +561,27  <at>  <at>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Michael McTernan | 22 Jun 2005 15:31

Spell checking

Hi there,

I'm starting to build up a bit of documentation using Doxygen, and realise
that I've made the odd spelling mistake.  It would help me if Doxygen would
check spellings while generating documentations and produce warnings.

Checking the lists archives, I haven't found anything significant about
spell checking in Doxygen.  Surely this has been considered before?

I was thinking that it would be simple to make a DocVisitor that together
with something like GNU aspell, could check all the observable text and
produce warnings for misspelt words.

Particularly this would be better than extracting the comments from the
source, and then running a spell checker as things like \a words or \code
blocks could automatically be skipped.

Anyone have any comments on this?  If I made such a DocVisitor, would it be
welcomed?

Cheers,

Mike

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
(Continue reading)

Permalink | Reply | 5 comments |
headers
Duane Ellis | 22 Jun 2005 15:38

Re: Spell checking

> Anyone have any comments on this?  If I made such a DocVisitor, would it 
be
> welcomed?

Although - I'm concerned about "feature creep" in a package like doxygen.

The people I work with would love for me to us a spell checker on the
documentation i write...

-Duane

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Permalink | Reply | 0 comments |
headers
Dimitri van Heesch | 22 Jun 2005 16:28
Picon
Gravatar

Re: Spell checking

On 6/22/05, Michael McTernan <Michael.McTernan <at> ttpcom.com> wrote:
> Hi there,
> 
> I'm starting to build up a bit of documentation using Doxygen, and realise
> that I've made the odd spelling mistake.  It would help me if Doxygen would
> check spellings while generating documentations and produce warnings.
> 
> Checking the lists archives, I haven't found anything significant about
> spell checking in Doxygen.  Surely this has been considered before?
> 
> I was thinking that it would be simple to make a DocVisitor that together
> with something like GNU aspell, could check all the observable text and
> produce warnings for misspelt words.
> 
> Particularly this would be better than extracting the comments from the
> source, and then running a spell checker as things like \a words or \code
> blocks could automatically be skipped.
> 
> Anyone have any comments on this?  If I made such a DocVisitor, would it be
> welcomed?

I like the idea of using the DocVisitor class in combination with a
user-specified
external tool. So please go ahead and implement this. 

I think it would require two new string-type config options, i.e
something like:
SPELL_CHECKER_CMD  - command to execute, empty => no spell checking
SPELL_CHECKER_LOG   - log file to write the results to.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chris Croughton | 22 Jun 2005 18:43
Picon

Re: Spell checking

On Wed, Jun 22, 2005 at 02:31:11PM +0100, Michael McTernan wrote:

> I was thinking that it would be simple to make a DocVisitor that together
> with something like GNU aspell, could check all the observable text and
> produce warnings for misspelt words.

What's a misspelt (or misspelled) word in a program?  I must have
thousands, just in comments where I refer to variables and functions,
hardware, and things in external specifications.

> Particularly this would be better than extracting the comments from the
> source, and then running a spell checker as things like \a words or \code
> blocks could automatically be skipped.

That would cut down on some, but by no means all.

> Anyone have any comments on this?  If I made such a DocVisitor, would it be
> welcomed?

It sounds like a useful thing if it is optional and doesn't add even
more to the bulk.

Chris C

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Kost | 24 Jun 2005 13:52
Picon
Favicon

Re: Spell checking

hi hi,
aspell already has a c/c++ comment mode. One idea for improvment I have for that
is to filter the wors against the TAGS database before spell-checking. This
would get dis of all the warning regarding mispelled words which are in fact
symbols (function names etc.).

Stefan

Michael McTernan wrote:
> Hi there,
> 
> I'm starting to build up a bit of documentation using Doxygen, and realise
> that I've made the odd spelling mistake.  It would help me if Doxygen would
> check spellings while generating documentations and produce warnings.
> 
> Checking the lists archives, I haven't found anything significant about
> spell checking in Doxygen.  Surely this has been considered before?
> 
> I was thinking that it would be simple to make a DocVisitor that together
> with something like GNU aspell, could check all the observable text and
> produce warnings for misspelt words.
> 
> Particularly this would be better than extracting the comments from the
> source, and then running a spell checker as things like \a words or \code
> blocks could automatically be skipped.
> 
> Anyone have any comments on this?  If I made such a DocVisitor, would it be
> welcomed?
> 
> Cheers,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Michael McTernan | 24 Jun 2005 15:16

RE: Spell checking

Hi,

What I had in mind was using a DocVisitor to dump a file of the words (with
some file/line information) that should be spell checked.  This can then be
checked with something like aspell, perhaps using a small bit of script to
manage the error reporting etc...  Any other spelling tool could be used;
that's not for Doxygen to worry about :)

I think that this should not affect Doxygen very much at all, but has the
advantage of generating documents and spell checking in one step, while also
being sensitive to Doxygen mark-up, and as you say, removing symbols and the
like.

Cheers,

Mike

> -----Original Message-----
> From: doxygen-develop-admin <at> lists.sourceforge.net [mailto:doxygen-develop-
> admin <at> lists.sourceforge.net] On Behalf Of Stefan Kost
> Sent: 24 June 2005 12:53
> To: Michael McTernan
> Cc: doxygen-develop <at> lists.sourceforge.net
> Subject: Re: [Doxygen-develop] Spell checking
> 
> hi hi,
> aspell already has a c/c++ comment mode. One idea for improvment I have
> for that
> is to filter the wors against the TAGS database before spell-checking.
> This
(Continue reading)

Permalink | Reply | 0 comments |
headers
Janvier Anonical | 30 Jun 2005 09:03
Picon

Documenting methods inherited from <base class> and others

Hi!

I am resubmitting my query since it has been more than a week now and I 
still got no answers.

I am new to doxygen and I like to use it document my projects. 
Currently, I am looking
for a way to produce a documentation similar to a section produced by 
javadoc. That section
is the "Methods inherited from class ...". Then under this section, it 
lists (with appropriate
links) the methods that the current class being documented inherited 
from its parent class.

Is there a way to do this in doxygen?

Is it also possible to list automatically a nested class?

Is it also possible to list all the classes that was derived from class 
that is currently
being documented?

Another program called cppdoc does this. Is there a way to emulate this 
in doxygen?

Thanks!

--

-- 
To mess up a Linux box, you need to work at it; to mess up your Windows box, you just need to work on it.  - Scott
Granneman, Security Focus
(Continue reading)

Permalink | Reply | 0 comments |

Gmane