doxygen-develop — List for discussing new features, submitting patches, etc.

Re: [Doxygen-develop] feature suggestion

[<at...@ko...>]

I was thinking about the arrows=2E

"Of the latter I'm not so sure=2E" ?

Message Original:
-----------------
A partir de: Dimitri van Heesch dimitri@stack=2Enl
Date: Sat, 11 Dec 2004 10:46:11 +0100
A: atandin@komodosoft=2Ecom, doxygen-develop@lists=2Esourceforge=2Enet
Sujet: Re: [Doxygen-develop] feature suggestion


On Fri, Dec 10, 2004 at 12:19:06PM -0500, atandin@komodosoft=2Ecom wrote:
> What do you think about creating hyperlink on class attributes in the
> class' collaboration graphs ?

You mean the attributes that appear when UML_LOOK is enabled or the
ones along the arrows?
=20
It makes sence indeed to link them to the documentation, provided=20
there is documentation of course and the dot tool supports such links=2E
Of the latter I'm not so sure=2E

Regards,
  Dimitri



--------------------------------------------------------------------
mail2web - V=E9rifiez votre courrier =E9lectronique depuis le web sur
http://mail2web=2Ecom/ =2E

Re: [Doxygen-develop] feature suggestion

[Dimitri v. H. <di...@st...>]

On Fri, Dec 10, 2004 at 12:19:06PM -0500, at...@ko... wrote:
> What do you think about creating hyperlink on class attributes in the
> class' collaboration graphs ?

You mean the attributes that appear when UML_LOOK is enabled or the
ones along the arrows?
 
It makes sence indeed to link them to the documentation, provided 
there is documentation of course and the dot tool supports such links.
Of the latter I'm not so sure.

Regards,
  Dimitri

Re: [Doxygen-develop] Build libraries on Solaris (sparc)

[Dimitri v. H. <di...@st...>]

On Thu, Dec 09, 2004 at 09:44:16PM +0100, Maik Hinrichs wrote:
> Hello,
> 
> I had to make a small change in file tmake.conf of target solaris-cc to 
> translate the libraries.
> 
> I changed value of TMAKE_AR from "CC -xar -o" to "ar cqs".
> 
> System: SunOS 5.9 (sparc)
> Compiler: CC (gcc 3.3.2)

If you use gcc, you should use solaris-g++ as a target, this should have
the correct TMAKE_AR setting.

Regards,
  Dimitri

[Doxygen-develop] Supporting Verilog

[Mohammad M. <moh...@xi...>]

Hello All,

I am new to this list and I'm interested in adding verilog support to
doxygen. No one is working on supporting verilog currently. Is that corre=
ct?

I would appreciate any help guiding me on how and where to start this
project.

Thanks,
Mohammad

"at...@ko..." wrote:

> What do you think about creating hyperlink on class attributes in the
> class' collaboration graphs ?
>
> --------------------------------------------------------------------
> mail2web - V=E9rifiez votre courrier =E9lectronique depuis le web sur
> http://mail2web.com/ .
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users=
.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop

--
---------------------------------------------------
/ /\ / Mohammad Musa       moh...@xi...
\ \    Xilinx              Telephone:  408-559-7778
/ /    2100 Logic Drive    Direct:     408-626-6484
\_\/ \ San Jose, CA 95124  FAX:        408-377-9013

[Doxygen-develop] feature suggestion

[<at...@ko...>]

What do you think about creating hyperlink on class attributes in the
class' collaboration graphs ?

--------------------------------------------------------------------
mail2web - V=E9rifiez votre courrier =E9lectronique depuis le web sur
http://mail2web=2Ecom/ =2E

[Doxygen-develop] Const test cases working fine -- Re: [Doxygen-users] Doxygen-1.3.9.1-20040612 in CVS

[<enn...@t-...>]

Hi

Am Montag, 6. Dezember 2004 19:38 schrieb Dimitri van Heesch:
=2E..
> + BUG: id 157085: Autolinks for const/volatile operators didn't work.
> + BUG: id 157433: Multi-variable declarations were not parsed
> properly.=20
=2E..
Thank you very much for solving this nasty bug.
Now I can use "const" without breaking the doxy docu!


I think this has even solved the following bug
http://bugzilla.gnome.org/show_bug.cgi?id=3D120389


I did test this with the following test cases and
everyone was working fine (for the first time) !

1.  int charp_fctCall (char *)
2.  int charpconst_fctCall (char *const)
3.  int=A0constcharp_fctCall (const char *)
4.  int=A0constcharpconst_fctCall (const char *const)
5.  int constconst_fctCall (MyType *const)
6.  int constcharpconst_fctCall (const char *const)
7.  int=A0intp_fctCall (int *)
8.  int=A0intpconst_fctCall (int *const)

On my CVS copy of doxygen I do have an additional test
directory for my test cases. And with "make test" it
will generate the docu and check if it =20
has the right elements inside.

Maybe it would be wise to add my and even more=20
test cases to the doxgen cvs version. So a new version
of doxygen could be tested automaticly for old/new=20
problems very easyly!

Thanks for listening=20
Enno

RE : [Doxygen-develop] new feature discussion

[Antoine T. <at...@ko...>]

diff file attached for an implementation of those 4 features. Critics
are welcome :)

Following an example in compiled html.

-----Message d'origine-----
De=A0: Antoine Tandin [mailto:at...@ko...]=20
Envoy=E9=A0: mardi 7 d=E9cembre 2004 18:29
=C0=A0: dox...@li...
Objet=A0: [Doxygen-develop] new feature discussion

Hello, I would like to discuss about some new options(features) for
doxygen.
All of them are triggered by the configuration file.

So I introduce them by there configuration name.

1 - NO_TYPEDEF_REFERENCED_BY_RELATION
Just don't produce the "Referenced by" paragraph for typedef.
Most of the time, this paragraph is long and useless.
There is no "reference by" for classes... so why for typedef.

The patch is very simple :
Just add a condition in the function addDocCrossReference
static void addDocCrossReference(MemberDef *src,MemberDef *dst)
{
  //printf("addDocCrossReference
src=3D%s,dst=3D%s\n",src->name().data(),dst->name().data());
  if ( dst->isTypedef() &&
Config_getBool("NO_TYPEDEF_REFERENCED_BY_RELATION") ) //+++ added line
    return;
//+++ added line
  if (Config_getBool("REFERENCED_BY_RELATION") &&=20
      (src->isFunction() || src->isSlot())=20
     )
  {
    dst->addSourceReferencedBy(src);
  }
  if ((Config_getBool("REFERENCES_RELATION") ||
Config_getBool("CALL_GRAPH")) &&=20
      (src->isFunction() || src->isSlot())
     )
  {
    src->addSourceReferences(dst);
  }
}

2 - GROUP_COLLABORATION_GRAPH
Create a dot graph on the top of each group page.
The graph shows relations between groups :
- is the group is part of an other group
- is the group contains other groups
- all members (class, namespace ...) share with other groups

3 - ALLOW_MEMBER_MULTIGROUP
This change the behavior of group pages.
With this option set, group page don't contain member documentation but
only a link to the member documentation.
With this option set, a function can be part of more than one groups.
With this option set, function documentation are no more moved to the
group page, so for a class member, the documentation stays in the class
file...

4 - SHOW_GROUPLINKS
Just add in the documentation of members a link to the group(s) they are
part of. (like for classes)

Please tell me what you think about those features.
Keep in mind that they don't change anything if the options are not set.

All of those 4 features are independent, but 2 and 4 are more relevant
with the 3 set.

Thanks



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.=20
http://productguide.itmanagersjournal.com/
_______________________________________________
Doxygen-develop mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-develop

[Doxygen-develop] Build libraries on Solaris (sparc)

[Maik H. <ma...@hi...>]

Hello,

I had to make a small change in file tmake.conf of target solaris-cc to 
translate the libraries.

I changed value of TMAKE_AR from "CC -xar -o" to "ar cqs".

System: SunOS 5.9 (sparc)
Compiler: CC (gcc 3.3.2)

Please find attached diff file.

Cu,
Maik

[Doxygen-develop] make clean and make distclean in src

[Maik H. <ma...@hi...>]

Hello,

I would like to suggest following small changes in src/Makefile.in:

1. "make clean" should remove generated source files by lex and bison, so I 
moved files from distclean to clean.

2. "make distclean" should remove file lang_cfg.h (generated by configure).

Please find attached diff file.

Cu,
Maik

Re: [Doxygen-develop] new feature discussion

[Dimitri v. H. <do...@gm...>]

On Tue, 7 Dec 2004 18:29:13 +0100, Antoine Tandin
<at...@ko...> wrote:
> Hello, I would like to discuss about some new options(features) for
> doxygen.
> All of them are triggered by the configuration file.
> 
> So I introduce them by there configuration name.
> 
> 1 - NO_TYPEDEF_REFERENCED_BY_RELATION
> Just don't produce the "Referenced by" paragraph for typedef.
> Most of the time, this paragraph is long and useless.
> There is no "reference by" for classes... so why for typedef.

I agree, but I don't think is it needed to have an option for this:
just always turn this on.
 
> The patch is very simple :
> Just add a condition in the function addDocCrossReference

> 
> 2 - GROUP_COLLABORATION_GRAPH
> Create a dot graph on the top of each group page.
> The graph shows relations between groups :
> - is the group is part of an other group
> - is the group contains other groups
> - all members (class, namespace ...) share with other groups

This could be useful, but how are you going to express to containment relations.
A "boxes in boxes" approach (which would be natural) doesn't work well with dot.

> 3 - ALLOW_MEMBER_MULTIGROUP
> This change the behavior of group pages.
> With this option set, group page don't contain member documentation but
> only a link to the member documentation.
> With this option set, a function can be part of more than one groups.
> With this option set, function documentation are no more moved to the
> group page, so for a class member, the documentation stays in the class
> file...

This feature has been discussed and requested before, but I don't think it
will work with the current implementation. If you have an undocumented file
with a member in multiple groups and this member is referred to in some place
to which group would you point? (if the file that actually contains
the member was
documented, the file could be a good candidate, but this is not guaranteed. 

> 
> 4 - SHOW_GROUPLINKS
> Just add in the documentation of members a link to the group(s) they are
> part of. (like for classes)

This could be useful (but less so if the member can be in one group only).

Regards,
  Dimitri

[Doxygen-develop] new feature discussion

[Antoine T. <at...@ko...>]

Hello, I would like to discuss about some new options(features) for
doxygen.
All of them are triggered by the configuration file.

So I introduce them by there configuration name.

1 - NO_TYPEDEF_REFERENCED_BY_RELATION
Just don't produce the "Referenced by" paragraph for typedef.
Most of the time, this paragraph is long and useless.
There is no "reference by" for classes... so why for typedef.

The patch is very simple :
Just add a condition in the function addDocCrossReference
static void addDocCrossReference(MemberDef *src,MemberDef *dst)
{
  //printf("addDocCrossReference
src=%s,dst=%s\n",src->name().data(),dst->name().data());
  if ( dst->isTypedef() &&
Config_getBool("NO_TYPEDEF_REFERENCED_BY_RELATION") ) //+++ added line
    return;
//+++ added line
  if (Config_getBool("REFERENCED_BY_RELATION") && 
      (src->isFunction() || src->isSlot()) 
     )
  {
    dst->addSourceReferencedBy(src);
  }
  if ((Config_getBool("REFERENCES_RELATION") ||
Config_getBool("CALL_GRAPH")) && 
      (src->isFunction() || src->isSlot())
     )
  {
    src->addSourceReferences(dst);
  }
}

2 - GROUP_COLLABORATION_GRAPH
Create a dot graph on the top of each group page.
The graph shows relations between groups :
- is the group is part of an other group
- is the group contains other groups
- all members (class, namespace ...) share with other groups

3 - ALLOW_MEMBER_MULTIGROUP
This change the behavior of group pages.
With this option set, group page don't contain member documentation but
only a link to the member documentation.
With this option set, a function can be part of more than one groups.
With this option set, function documentation are no more moved to the
group page, so for a class member, the documentation stays in the class
file...

4 - SHOW_GROUPLINKS
Just add in the documentation of members a link to the group(s) they are
part of. (like for classes)

Please tell me what you think about those features.
Keep in mind that they don't change anything if the options are not set.

All of those 4 features are independent, but 2 and 4 are more relevant
with the 3 set.

Thanks

Re: [Doxygen-develop] sending code

[Dimitri v. H. <do...@gm...>]

On Tue, 7 Dec 2004 12:54:39 +0100, Antoine Tandin
<at...@ko...> wrote:
>=20
> The code I've send is still not in cvs and I have no feedback to know if
> there is a problem with my code.
>=20
> I even don't know if the code has been received.
>=20
> Do di...@st... is the good address to send code ?
>=20
> Should I use a special mail title for submitting code ?
>=20

The address is ok, and the mail has been received. I just haven't
gotten around to it yet.
I did have a brief look and if the patch was trivial to apply I would
have done so, but
that was not the case. The main reasons are:
- The patch contains 4 or so features combined in one. So it is a all
or nothing approach.
- The new features/fixes were not discussed on forehand, and I do not
agree with the
   implementation in all cases.

> I did diff =E2=80=93u on /src directory with the lastest cvs snapshot aft=
er merging
> my code with the new snapshot.
>=20
> Do I need to merge my code with the lastest cvs snapshot until my code ha=
s
> been merged ?

No not necessarily, but if you could split the patch up into more managable=
=20
parts that would help.

Regards,
  Dimitri

[Doxygen-develop] sending code

[Antoine T. <at...@ko...>]

The code I've send is still not in cvs and I have no feedback to know if
there is a problem with my code.
I even don't know if the code has been received.
Do  <mailto:di...@st...> di...@st... is the good address to
send code ?
Should I use a special mail title for submitting code ?
 
I did diff -u on /src directory with the lastest cvs snapshot after
merging my code with the new snapshot.
Do I need to merge my code with the lastest cvs snapshot until my code
has been merged ?
 
Does the web interface of the cvs is up-to-date ?

Re: [Doxygen-develop] .l and .cpp

[Dimitri v. H. <do...@gm...>]

On Tue, 30 Nov 2004 11:06:50 +0100, Antoine Tandin
<at...@ko...> wrote:
>  
>  
> 
> How do I generate .cpp files  from .l files with MicrosoftVisual C ? 
> 

Get a windows version of flex (see for instance
http://unxutils.sourceforge.net/) and use it
in the same way as is done in the makefiles (from the command line you
should be able to use "make.bat msvc" to compile doxygen).

Regards,
  Dimitri

[Doxygen-develop] .l and .cpp

[Antoine T. <at...@ko...>]

How do I generate .cpp files  from .l files with MicrosoftVisual C ?
Thanks.

[Doxygen-develop] Adding a compiler flag to the doxygen build?

[Thomas C. <oo...@ma...>]

Is there a way to add a compiler flag to the doxygen build via congure?

I'm building on MacOS X 10.3.6 on a G4 PowerBook and I'd like to add 
"-mcpu=G3 -mtune=G4" or maybe even "-mcpu=G4 -mtune=G4" to the compiler 
flags for the build at configure time to get a faster Doxygen for my 
machine.

Also, I'd like to see if anyone has gotten XCode 1.5 debugging working 
with the Doxygen code base.

Re: [Doxygen-develop] Style bug: In need of a nest list class in CSS

[Dimitri v. H. <di...@st...>]

Hi Jeff,

On Wed, Nov 17, 2004 at 02:45:41PM +1100, Jeff Franks wrote:
> I have come across a style bug with unumbered lists. It's only a bug if 
> you try to set a custom style on <ul>. I use doxygen  to document a  
> large C++ project - it's great, thank you! I want to give the unnumbered 
> lists that are used to list the class members at the top of the 
> generated HTML pages a custom background color, so they stand out more 
> as a group. I added an entry for <ul> to my custom CSS file. I use a 
> light page background color (darker than white) and have the list 
> background color a few shades lighter. On its own it doesn't look good 
> but when you give the list a much darker one pixel border I looks great. 
> The subtle difference in shades becomes more obvious and the lists 
> appears to stand out from the page.

Can you give an example CSS so I can try it?

> Unfortunately this is where the style bug occurs. The custom style also 
> gets applied to the nested <ul> that are used to display the class 
> hierarchy entries in the 'hierarchy.html' file. Not only does the top 
> level <ul> have a border but all the nested <ul> do as well - and it 
> looks ugly. So I have to manually edit the file to remove the borders, 
> and its a long file - about 420 classes across two libraries. Everywhere 
> else top level lists look OK.
> 
> Would it be possible to implement a nested <ul> class in the CSS that 
> could be used to reverse any style changes applied to a top level <ul>. 
> Then all nested <ul> could be generated with this nested <ul> class 
> instead of a standard <ul>. I don't know if you ever intended such a 
> style to be applied to lists but it looks good, and I'm sure it would 
> add new design possibilites to Doxygen documentation.

I think that what you want is to have the top level <ul> looking something
like <ul class="top"> so you can style it via CSS in a different way as
the nested <ul>'s? For lists defined inside comment blocks this is already
possible. For the hierarchy.html it is not. 

If you want to help to fix this, please look for startItemList() in 
startIndexHierarchy() of index.cpp. It should be passed the level 
parameter. In htmlgen.h you can then change the implementation to 
include the proper class in case the level is 0.

Regards,
  Dimitri

Re: [Doxygen-develop] Comment diagrams

[Dimitri v. H. <di...@st...>]

Hi Stathis,

On Fri, Nov 19, 2004 at 06:53:18PM +0000, Stathis Sideris wrote:
> Hello,
> 
> I'm really glad that you liked ditaa, and that you tought it would be
> useful. :-)
> 
> Before diving too deep into the (120k lines!) code to add the \ditaa and
> \endditaa tags, I would like to ask for some pointers so that I don't
> get lost.
> 
> It seems that I would need to add ditta and edditta to to cmdmapper.cpp
> and cmdmapper.h.

Yes.

> Then I would need to modify config.l I'm not familiar with flex, so this
> will be tricky...

If you look for "dot" in scanner.l and replace it by ("dot"|"ditta")
and cases where "dot" is part of a or'ed construction already just append
a |"ditta" it should be fine. The part in scanner.l is just to skip 
\\ditta (i.e. the escaped version of the command), and not to 
interpret the section in between. I'll review if before including it.

> I would propose to add the following entries in the configuration:
> 
> HAVE_DITAA: whether ditaa processing occurs (like HAVE_DOT)
> DITAA_JAR: filename (with full path) of the ditaa jar file

Ok, just enter a section for these in config.l (one of type bool and the
other of type string). Then you can use Config_getBool("HAVE_DITAA") and
Config_getString("DITAA_JAR") in the rest of code.

> Another thing is how you would pass command line parameters to ditaa
> itself. How about the line after the \ditaa tag being reserved for that?
> Example:
> 
> \ditaa no-shadows round-corners
> +--+
> |  |
> +--+
> \endditaa
> 
> or something of the kind.
> 
> Then I would probably have to add something to docparser.cpp so that
> ditaa starts if the \ditaa tag is found in a comment. Also the
> appropriate changes in htmlgen.cpp for the <img> tags to be inserted (I
> suppose ditta would not be possible for other formats, it doesn't make
> postscript yet!),

Indeed. There are several commands with parameters already, so just look
at handleCommand in docparser.cpp.

> Am I making any sense at all? :-) Any tips/help would be very welcome.

Perfect sense. I think you covered all places where changes are needed.

Regards,
  Dimitri

Re: [Doxygen-develop] Todo list item 42

[Dimitri v. H. <di...@st...>]

On Fri, Nov 19, 2004 at 12:18:20AM +0100, Carsten Stiborg wrote:
> Hello everybody
> 
> Unless anybody else is working on todo list item 42, integration of
> cvs/subversion file information, I would like to take on that particular
> feat.

I do not know of someone who is working on that, so go ahead!
Can you explain what you had in mind when it comes to integration?

> As far as I've seen from the mailing list no-one is working with this
> issue. But people may have been working in the secret. ;)

If so, they better speak up now ;-)

Regards,
  Dimitri

[Doxygen-develop] Comment diagrams

[Stathis S. <im...@sa...>]

Hello,

I'm really glad that you liked ditaa, and that you tought it would be
useful. :-)

Before diving too deep into the (120k lines!) code to add the \ditaa and
\endditaa tags, I would like to ask for some pointers so that I don't
get lost.

It seems that I would need to add ditta and edditta to to cmdmapper.cpp
and cmdmapper.h.

Then I would need to modify config.l I'm not familiar with flex, so this
will be tricky...

I would propose to add the following entries in the configuration:

HAVE_DITAA: whether ditaa processing occurs (like HAVE_DOT)
DITAA_JAR: filename (with full path) of the ditaa jar file

Another thing is how you would pass command line parameters to ditaa
itself. How about the line after the \ditaa tag being reserved for that?
Example:

\ditaa no-shadows round-corners
+--+
|  |
+--+
\endditaa

or something of the kind.

Then I would probably have to add something to docparser.cpp so that
ditaa starts if the \ditaa tag is found in a comment. Also the
appropriate changes in htmlgen.cpp for the <img> tags to be inserted (I
suppose ditta would not be possible for other formats, it doesn't make
postscript yet!),

Am I making any sense at all? :-) Any tips/help would be very welcome.

Thanks

Stathis


-- 
________

Efstathios Sideris
Biomolecular Structure and Modelling Unit
Department of Biochemistry and Molecular Biology
University College London
Darwin Building, Gower Street
London WC1E 6BT, UK

[Doxygen-develop] Todo list item 42

[Carsten S. <ca...@st...>]

Hello everybody

Unless anybody else is working on todo list item 42, integration of
cvs/subversion file information, I would like to take on that particular
feat.

As far as I've seen from the mailing list no-one is working with this
issue. But people may have been working in the secret. ;)

-CS

RE: [Doxygen-develop] how to contribute ?

[Guy H. <guy...@or...>]

Seeing this post come up has reminded me that I had sent a patch to
v1.3.8 (obviously a couple of months back) which improved, hopefully,
the way Class Member Function subsections are formatted in latex output
in cases where they run onto multiple lines.

For example, a member function previously shown like this...

virtual bool someMethod(int arg1, const char *arg2, const
ISomeInterface *arg3, bool arg4) [pure
virtual]

would be formatted to indent the second line onwards and to prevent
parameters being broken across lines, like this (hopefully the email
formatting doesn't screw this up)...

virtual bool someMethod(int arg1, const char *arg2,
     const ISomeInterface *arg3, bool arg4)
     [pure virtual]

I didn't hear anything and was busy with other stuff so didn't resend
the patch. Is this of interest? I'm afraid I only did this for the latex
output, not the others.

guy

BTW, even if this is not useful, I noticed that the method
LatexGenerator::WriteNonBreakableSpace() in latexgen.cpp uses '\\' as an
unbreakable space - shouldn't this be '~'?


-----Original Message-----
From: dox...@li...
[mailto:dox...@li...] On Behalf Of
Dimitri van Heesch
Sent: 18 November 2004 13:28
To: Antoine Tandin
Cc: dox...@li...
Subject: Re: [Doxygen-develop] how to contribute ?

On Thu, 18 Nov 2004 14:16:00 +0100, Antoine Tandin
<at...@ko...> wrote:
>  
> Sorry, I wanted to know how it is possible to contribute to doxygen
> developpement. 
> 
> How can I add code or patch ? 
> 

The preferred way, is to create a patch (using diff -u against the
latest CVS version) and send that to me (di...@st...) along with
a description of what the patch is supposted to do and a test file (if
relevant).

If you don't hear anything and the patch is not included after one or
two CVS updates then please send me a reminder.

It helps to first discuss what you want to add/change, since it may
already be possible or someone may already be working on it.

Regards,
  Dimitri


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Doxygen-develop mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-develop

Re: [Doxygen-develop] In need of a separate CSS class for nested lists

[Dimitri v. H. <do...@gm...>]

On Fri, 19 Nov 2004 00:58:03 +0000, Jeff Franks <jc...@tp...> wrote:
> Hi,
> 
> Sorry for the repost but I did not get a reply to my previous message a
> couple of days ago.
> 
> Is there any chance that nested lists could be created using a separate
> CSS class that is different from top level lists. I want to give the
> lists a border and background color. The problem is that nested lists in
> the C++ class hierarchy in hierarchy.html also have a border, and it
> looks ugly.
> 
> I looked at the Doxygen source code and I really wouldn't know where to
> begin to create a patch for the source code that does this.

Most of the indices (such as the class hierarchy) are generated in index.cpp. 
You should probably add a "topLevel" flag to one or more methods of the 
OutputList class that is used to generate the output for all formats.
I hope this
gives you a start.

Regards,
  Dimitri

[Doxygen-develop] In need of a separate CSS class for nested lists

[Jeff F. <jc...@tp...>]

Hi,

Sorry for the repost but I did not get a reply to my previous message a 
couple of days ago.

Is there any chance that nested lists could be created using a separate 
CSS class that is different from top level lists. I want to give the 
lists a border and background color. The problem is that nested lists in 
the C++ class hierarchy in hierarchy.html also have a border, and it 
looks ugly.

I looked at the Doxygen source code and I really wouldn't know where to 
begin to create a patch for the source code that does this.

Regards,
Jeff Franks.

Re: [Doxygen-develop] how to contribute ?

[Dimitri v. H. <do...@gm...>]

On Thu, 18 Nov 2004 14:16:00 +0100, Antoine Tandin
<at...@ko...> wrote:
>  
> Sorry, I wanted to know how it is possible to contribute to doxygen
> developpement. 
> 
> How can I add code or patch ? 
> 

The preferred way, is to create a patch (using diff -u against the
latest CVS version) and send that to me (di...@st...) along with
a description of what the patch is supposted to do and a test file (if
relevant).

If you don't hear anything and the patch is not included after one or
two CVS updates then please send me a reminder.

It helps to first discuss what you want to add/change, since it may
already be possible or someone may already be working on it.

Regards,
  Dimitri