doxygen-users — List for users of doxygen

RE: [Doxygen-users] (no subject)

[Kris T. <kri...@cs...>]

>
> Here is one solution, all the following is in the
> header file -
>
> ------------------------------
> class A
> {
> public:
>   int method1 ();
>   void method2 ();
> };
>
> /**
>  * Blah
>  * @return blah
> */
> int A::method1 () const {return simple_thing;}
>
> /**
>  * Blah2
>  */
> void A::method2 () {do_something_simple ();}
> --------------------------------
>
> But I have a question about inlining - will some
> compilers fail to inline methods because the
> definition is now separate from the declaration?

You HAVE to say
class A
{
 public:
   int method1 ();
   void method2 ();
};

Otherwise the compiler won't know you want to inline, and it will generate a
A::method1 implementation in every object file whose source happens to
include your header (think about what #include does and it will make sense).
This will give you lots of linking problems.

Aside from that, personally, I prefer my documentation in the class
definition, while I put the inline implementations somewhere else. In that
way, people reading the source only have to check the class definition and
nothing else.
(I put the inlines in a spearate file blabla.inl to stress that fact). But
that's up to you of course.

All the best,

Kris Thielemans
Imaging Research Solutions Ltd
Cyclotron Building
Hammersmith Hospital
Du Cane Road
London W12 ONN, United Kingdom

web site address:
http://www.irsl.org/~kris

[Doxygen-users] (no subject)

[Paul B. <pee...@ya...>]

Hi,

Basic question about Doxygen.  Say I have a class
like this

---------------------------
class A
{
public:
  int method1 () const {return simple_thing;}
  void method2 () {do_something_simple ();}
};
---------------------------

I would like to (a) add Doxygen comments
to the methods, but (b) not
clutter up my source code with interspersed
comments.

Here is one solution, all the following is in the
header file -

------------------------------
class A
{
public:
  int method1 ();
  void method2 ();
};

/** 
 * Blah
 * @return blah
*/
int A::method1 () const {return simple_thing;}

/**
 * Blah2
 */
void A::method2 () {do_something_simple ();}
--------------------------------

But I have a question about inlining - will some
compilers fail to inline methods because the
definition is now separate from the declaration?  i.e.
assuming method1 and method2 are inlined in the first
case above, might they be not-inlined in the second
case?

Thanks,
Paul.


__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

[Doxygen-users] HTML markup after @par broken?

[Peter S. <pet...@hu...>]

Just after a @par tag doxygen doesn't interpret HTML tags. See the
following example:

/**
 * @mainpage Example
 *
 * <tt>this works</tt>
 *
 * @par <tt>why do we see the "tt" tag here?</tt>
 */

I'm working with doxygen 1.2.13.1

Regards, Peter
-- 
    _   _        Peter Steiner <pet...@hu...>
  / /_/ /        Hug-Witschi AG <http://www.hugwi.ch/>
 /  _  /         Electronic Engineering
/_/ /_/  _   _   Industriestrasse 12
   / / / / / /   CH-3178 Boesingen
  / /_/ /_/ /    Tel  +41 31 740 44 44
 /_ _ _ _ _/     Fax  +41 31 740 44 45

[Doxygen-users] rtf output NOT support ONE complete Globals index? but html OK!

[chen b. <ch...@ya...>]

UHJvYmxlbToNCioqKioqKioqDQpJIG91dHB1dCB0aGUgaHRtbCBkb2N1bWVudCBhbmQgcnRmIGRv
Y3VtZW50IGF0IHRoZSBzYW1lIHRpbWUuDQpidXQgcnRmIGRvIG5vdCBwcm9kdWNlIEdsb2JhbHMo
SSBtZWFuIGdsb2JhbCBmdW5jdGlvbnMgYW5kIHZhcmlhYmxlcy4uLikgDQppbmRleCENCg0KYnV0
IGh0bWwgdmVyc2lvbiBkbyBpdC4NCg0KSSBtZWFuIHJ0ZiBwcm9kdWNlIHRoZSBnbG9iYWxzIGlu
ZGV4IGZvciBFVkVSWSBmaWxlKGZvciBleGFtcGxlLCBtYWluLmMpLA0KYnV0IEkgYWxzbyB3YW50
IGEgQ09NUExFVEUgZ2xvYmFscyBpbmRleCBmb3IgdGhlIHdob2xlIHByb2plY3QuDQoNCg0KSSBj
aGVja2VkIHRoZSBkb3h5d2l6YXJkJ3MgR2VuZXJhbCB0YWIncyBvcHRpb25zIGJ1dCBubyBpZGVh
Lg0KDQpFbnZpcm9ubWVudDoNCioqKioqKioqKioqKg0KRG94eWdlbiB2ZXJzaW9uIDEuMi4xMy4x
Ow0Kb24gVHVyYm9saW51eCBTZXJ2ZXIgNi41Ow0KRW5nbGlzaCBsYW5ndWFnZSBydGYgb3V0cHV0
Ow0KDQp0aGUgdGVzdCBzb3VyY2UgY29kZToNCioqKioqKioqKioqKioqKioqKioqKg0KDQovKi0t
LS0tLS0tLS0tLS0tLXNvdXJjZSBjb2RlLS0tLS0tLS0tLS0tLWJlZ2luICovDQojaW5jbHVkZSA8
c3RkaW8uaD4NCiNpbmNsdWRlICJtYWluLmgiDQoNCmludCBtYWluKHZvaWQgKQ0Kew0KIHByaW50
ZigiaGVsbG8gd29ybGRcbiIpOw0KIC8qIG5vdyBwcmVwYXJlZCBjYWxsIGZuKCkgKi8NCiBmbigp
Ow0KDQp9DQoNCmludCBkLGUsZjsgLyohPCBoZXkhIGxldCB1cyBkZWZpbmUgZCwgZSwgZiAqLw0K
DQovKiFcdmVyYmF0aW0NCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioNCnwgRnVuY3Rpb24gbmFtZSAgICAgOiBmbg0KfCBEZXNjcmlw
dGlvbiAgICAgOiANCnwgUmV0dXJuICAgIDogc3RhdGljIHZvaWQgDQp8IEFyZ3VtZW50ICAgICAg
ICAgIDogdm9pZA0KfCBDYXV0aW9uICAgICAgICAgICA6IA0KfC0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KfCBDcmVhdGUgICAgICAg
ICAgICA6IDIwMDItMS0xNSBieSBDaGVuIEJpbg0KICoqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKlxlbmR2ZXJiYXRpbQ0KKi8NCnN0YXRp
YyB2b2lkIGZuKHZvaWQgKQ0Kew0KIGludCBhLGIsYzsNCiBwcmludGYoIm5vdyBjYWxsaW5nIGZu
KCkiKTsNCg0KfQ0KLyotLS0tLS0tLS0tLS0tLS1zb3VyY2UgY29kZS0tLS0tLS0tLS0tLS1lbmQg
Ki8NCg==

[Doxygen-users] Why is Japanese RTF output broken ?

[Haruyuki O. <oh...@is...>]

Hello

Why are Japanese characters(Kanji)  in RTF output broken ?
What is a difference in treating Japanese characters in between outputing
HTML  and outputing RTF ?
In outputing HTML, Japanese characters are correctlly treated.
Any idea ?

---
Haru

[Doxygen-users] Typedef of a std::vector

[Kevin W. <KWi...@vi...>]

Looking for a recommendation here...  I've got a typedef that looks
something like this:

  /** A standard C++ vector of MyClass objects */
  Typedef std::vector<MyClass> MyClassList

By default, Doxygen displays this typedef description as an entry on the
namespace page.  I'd really like to "promote" this typedef so that it
appears as a full-blown compound just like the MyClass class itself.  The
only way I could think of to do this was to use the \class command in my
comment.  This works, but doesn't feel right (it ISN'T a class <smile>).
Any suggestions?

Also, since some of the users of my documentation are likely to not be
familiar with a C++ standard vector, I'm thinking it would be helpful for me
to include documentation for std::vector and link to it from my typedefs.
What would be the best way to do that?  Again - any suggestions?

Thanks!

-- Kevin Williams
   Visionael Corporation
   kwi...@vi...

 

[Doxygen-users] page, section and subsection

[Peter S. <pet...@hu...>]

Hello!

Doxygen seems not to distinguish @page from @section with respect to
HTML header tags, both get a <h2> (subsection gets a <h3>). Similar problem
in LATEX output, @page and @section are on the same hierarchical level.

I don't understand the reason for this; for now i have to remember that
(for my uses) I must not use @section on @page blocks; they make sense
only in a @mainpage block.

Am I missing something obvious here?

Regards
-- 
    _   _        Peter Steiner <pet...@hu...>
  / /_/ /        Hug-Witschi AG <http://www.hugwi.ch/>
 /  _  /         Electronic Engineering
/_/ /_/  _   _   Industriestrasse 12
   / / / / / /   CH-3178 Boesingen
  / /_/ /_/ /    Tel  +41 31 740 44 44
 /_ _ _ _ _/     Fax  +41 31 740 44 45

Re: [Doxygen-users] Segmentation fault with binaries on SOS 5.8

[Lars v. W. <von...@lf...>]

Hi,

Sorry for the late reply. After the output of 'Possible candidates:'
doxygen
prints a method header with the same name but different arguments. I
admit
that the file is actually incorrect (the compiler would complain about
the
same thing), but this shouldn't cause a seg fault!

Removing the pair of .cc/.hh files actually seems to work fine. However,
on Linux the error does not occur, even with the incorrect method names.

Lars


John Sturton wrote:
> 
> Lars von Wedel wrote:
> >
> > Hello,
> >
> > we're using doxygen for quite some time now. Yesterday, I downloaded a
> > new binary
> > 1.2.13 for Solaris 8 from the doxygen pages. It gives me a segmentation
> > fault in the
> > middle of the process:
> >
> > > Searching for enumerations...
> > > Searching for member function documentation...
> > > /users/modkit/RealmsDevelopment/Source/Cheops/src/cheops/numeric/eso_variable_i.cc:72: Warning: no matching class member found for
> > >   EsoVariable_i::EsoVariable_i(const string &name, long index, long dimension, Cheops::Eso::Eso *eso, vector< double > initial_coefficients, Numeric::SupportType support_type=Numerics::UNSPECIFIED)
> > > Possible candidates:
> > > Segmentation Fault (core dumped)
> >
> > Anyone knows help? Doxygen 1.2.5 on Linux works fine with more or less
> > the same set of C++ sources.
> >
> 
> What is the next message after "Possible candidates:" that the Linux
> version squirts out?
> 
> John

[Doxygen-users] #defined size of array as link: how?

[Thomas Z. <zi...@co...>]

Please consider the following code fragment:

#define SIZE 256

int array[SIZE];


When creating html output with the standard doxygen settings (doxygen -g),
int array[SIZE] is part of the 'Variables'-section.

array is a link into the section 'Detailed Description'. SIZE is not a link
into this section.

Is it possible to configure doxygen to generate links if the size of an
array is a #define?

Thanks in advance,
Thomas

PS: tested with 1.2.12. I've attached test.cpp test.dox and the
    doxgen-1.2.12 output test_cpp.html


-- 
Dr.-Ing. Thomas Ziegler            |
Senior Research Engineer           | Coding Technologies
phone: +49 (0) 911 92891 -27       | Deutschherrnstr. 15-19
fax:   +49 (0) 911 92891 -99       | D-90429 Nürnberg, Germany
mailto:zi...@Co...  | http://www.CodingTechnologies.com

[Doxygen-users] setEncoding ?

[Haruyuki O. <oh...@is...>]

Hello

I think the latest doxygen generates ISO-8859-1 encoding for XML output.
But it does not seem to call QTextStream::setEncoding(QTextStream::Latin1)
in genarateXML function.
Is it correct ?

---
Haru

[Doxygen-users] Is it better to add IO_Translate option for output text files ?

[Haruyuki O. <oh...@is...>]

I think it is better to add IO_Translate open file option for all output
*text* files.
I've checked the latest source code, but this option is rarely used.

Any suggestion ?

---
Haru

Re: [Doxygen-users] C++ template documentation

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

On Mon, Jan 14, 2002 at 09:48:52AM -0000, Kris Thielemans wrote:
> 
> > 
> > Something along the lines of '\templatearg' is what I'd like to be able
> > to do.
> > 
> > 
> I'd like that as well...

This is quite easy to add. Just look for "param" or "retval" in src/doc.l
and add a similar section. If anyone wants to do this, I'll include the
patch ;-)

Regards,
  Dimitri

Re: RE: [Doxygen-users] why detailed documentation replace linefeed with space?

[Fred I. T. <fre...@jo...>]

Hi Doxygen users

I have recently tried out Doxygen, and I must say that I also miss the =
possibility to take with me the comments in front of a function into my =
documentation. I have also tried out CCrider, which have this option. I =
used Doxygen on a project which was finished, and I wouldn't change too =
much in the code to get Doxygen to work. The only way I could get it as I =
wanted, was to implement the comments as this:

/*!\verbatim
************************************************************
 | Function name     : fn
 | Description     :=20
 | Return   : static void=20
 | Argument          : void
 | Caution           :=20
 |------------------------------------------------------------
 | Create            : 2002-1-14 by Chen Bin
 ************************************************************\endverbatim
*/

and since I used fixed with fonts in my programming editor, the coloums =
was also preserved using this method.=20
But if I intend to use Doxygen on a new project, maybe I would try to =
write my comments more according to what Doxygen needs.


Fred I Tallaksen
R & D JOTRON electronics a.s




>>> "Prikryl,Petr" <PRI...@sk...> 14.01.02 11:03 >>>
Hi Chen,

Please, read the documentation.  Doxygen intentionally does not preserve=20=

formatting of the comments (if not prescribed).  In your case, you have
probably generated HTML output.  The HTML document ignores spaces
and linebreaks in your output.  The bar character '|' is not given any
special meaning, nor any other character that is used inside your
comment.  You have to use special doxygen commands to mark=20
the arguments, the returned value, etc.

Petr

--=20
Petr Prikryl, Skil, spol. s r.o., (pri...@sk...)


> -----Original Message-----
> From:	chen bin [SMTP:ch...@ya...]=20
> Sent:	Monday, January 14, 2002 9:34 AM
> To:	dox...@li...=20
> Subject:	[Doxygen-users] why detailed documentation replace =
linefeed
> with space?
>=20
> my source code looks like this way:
> =20
> /*!************************************************************
> | Function name     : fn
> | Description     :=20
> | Return   : static void=20
> | Argument          : void
> | Caution           :=20
> |------------------------------------------------------------
> | Create            : 2002-1-14 by Chen Bin
>  *************************************************************/
> static void fn(void )
> {
>  int a,b,c;
>  printf("now calling fn()");
> =20
> }
> =20
> the output documentation:
>=20
> | Function name : fn | Description : | Return : static void | Argument :
> void | Caution :
> |------------------------------------------------------------ | Create :
> 2002-1-14 by Chen Bin=20
>=20
> why?
>=20
> regards
>=20
> chen bin
>=20

_______________________________________________
Doxygen-users mailing list
Dox...@li...=20
https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] why detailed documentation replace linefeed w ith space?

[Prikryl,Petr <PRI...@sk...>]

Hi Chen,

Please, read the documentation.  Doxygen intentionally does not preserve 
formatting of the comments (if not prescribed).  In your case, you have
probably generated HTML output.  The HTML document ignores spaces
and linebreaks in your output.  The bar character '|' is not given any
special meaning, nor any other character that is used inside your
comment.  You have to use special doxygen commands to mark 
the arguments, the returned value, etc.

Petr

-- 
Petr Prikryl, Skil, spol. s r.o., (pri...@sk...)


> -----Original Message-----
> From:	chen bin [SMTP:ch...@ya...]
> Sent:	Monday, January 14, 2002 9:34 AM
> To:	dox...@li...
> Subject:	[Doxygen-users] why detailed documentation replace linefeed
> with space?
> 
> my source code looks like this way:
>  
> /*!************************************************************
> | Function name     : fn
> | Description     : 
> | Return   : static void 
> | Argument          : void
> | Caution           : 
> |------------------------------------------------------------
> | Create            : 2002-1-14 by Chen Bin
>  *************************************************************/
> static void fn(void )
> {
>  int a,b,c;
>  printf("now calling fn()");
>  
> }
>  
> the output documentation:
> 
> | Function name : fn | Description : | Return : static void | Argument :
> void | Caution :
> |------------------------------------------------------------ | Create :
> 2002-1-14 by Chen Bin 
> 
> why?
> 
> regards
> 
> chen bin
> 

Re: [Doxygen-users] why detailed documentation replace linefeed with space?

[Olivier P. <pa...@la...>]

chen bin wrote:

> my source code looks like this way:


[...]

 
> the output documentation:
> 
> | Function name : fn | Description : | Return : static void | Argument : 
> void | Caution : 
> |------------------------------------------------------------ | Create : 
> 2002-1-14 by Chen Bin
> 
> why?


I think I can answer this one : embedding documentation
in doxygen comments isn't enought to get them formatted
properly. If you insist on keeping your data this way,
inserting "<br>" or somethink like that should give you
proper linefeeds.

But I think a better way would be to use Doxygen's
habilities by expressing things like that :

/*!
A short description.
A long description of what this function do.
\arg <name> <comment>
\returns <comment>
\warning <comment>
\author Chen Bin
*/

Etc (have a look at the documentation for more commands).
Note that the function name and the type of return don't
have to be documented, doxygen will extract them anyway.

Regards,
Olivier.

RE: [Doxygen-users] C++ template documentation

[Kris T. <kri...@cs...>]

> 
> Something along the lines of '\templatearg' is what I'd like to be able
> to do.
> 
> 
I'd like that as well...
 
Kris Thielemans 
(kris.thielemans<at>ic.ac.uk)
Imaging Research Solutions Ltd
Cyclotron Building
Hammersmith Hospital
Du Cane Road
London W12 ONN, United Kingdom
web site address:
http://www.irsl.org/~kris  

[Doxygen-users] why detailed documentation replace linefeed with space?

[chen b. <ch...@ya...>]

bXkgc291cmNlIGNvZGUgbG9va3MgbGlrZSB0aGlzIHdheToNCg0KLyohKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQp8IEZ1bmN0aW9u
IG5hbWUgICAgIDogZm4NCnwgRGVzY3JpcHRpb24gICAgIDogDQp8IFJldHVybiAgIDogc3RhdGlj
IHZvaWQgDQp8IEFyZ3VtZW50ICAgICAgICAgIDogdm9pZA0KfCBDYXV0aW9uICAgICAgICAgICA6
IA0KfC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KfCBDcmVhdGUgICAgICAgICAgICA6IDIwMDItMS0xNCBieSBDaGVuIEJpbg0KICoq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KiovDQpzdGF0aWMgdm9pZCBmbih2b2lkICkNCnsNCiBpbnQgYSxiLGM7DQogcHJpbnRmKCJub3cg
Y2FsbGluZyBmbigpIik7DQoNCn0NCg0KdGhlIG91dHB1dCBkb2N1bWVudGF0aW9uOg0KfCBGdW5j
dGlvbiBuYW1lIDogZm4gfCBEZXNjcmlwdGlvbiA6IHwgUmV0dXJuIDogc3RhdGljIHZvaWQgfCBB
cmd1bWVudCA6IHZvaWQgfCBDYXV0aW9uIDogfC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSB8IENyZWF0ZSA6IDIwMDItMS0xNCBieSBD
aGVuIEJpbiANCg0Kd2h5Pw0KDQpyZWdhcmRzDQoNCmNoZW4gYmluDQoNCg==

[Doxygen-users] C++ template documentation

[David L. L. <da...@WP...>]

Does doxygen support the documentation of C++ template classes?  More
specificially, I want to be able to do something like this:

//! Template class for Foo things.
/*!
	\templatearg T A Foo thing.  Must contain a bar method.
*/
template <class T>
class Foo
{ public:
	void something() { T::bar(); }
};


Something along the lines of '\templatearg' is what I'd like to be able
to do.


Thanks for your time.

--
David Ludwig               | "The Linux philosophy is laugh in the face of
davidl<at>wpi.edu          | danger.  Oops.  Wrong One.  'Do it yourself.'
http://www.wpi.edu/~davidl | That's it."                  - Linus Torvalds

[Doxygen-users] Problems with XML output

[Jacob G. H. <jg...@io...>]

Hi,

I downloaded the Linux Intel binary from your site today, but I have various
problems with the XML output not being balanced. It seems to go wrong in a 
<detaileddescribtion>, but I am currently unable to produce a small testcase.

Since all I need is the inheritance structure for my own processing, and not
the docs themselves, is there a way of disabling them. This would also cut down
the size (119MB) of the resulting XML?

Thanks in advance,
Jacob

[Doxygen-users] Reference to figure in LateX

[Audrey S. <as...@ul...>]

Hi,
=20
I am a researcher at the Free University of Brussels.
=20
My question is : is it possible to reference the number of a figure for
LateX documentation?
=20
Audrey Simon
=20
---------------------------------
Audrey Simon
Service de m=E9canique analytique et CFAO
50, av. F.D. Roosevelt - CP 165/14
1050 Bruxelles
---------------------------------
T=E9l :  +32-2-650.47.66
Fax : +32-2-650.47.24
E-mail :  <mailto:aud...@ul...> aud...@ul...
=20

Re: [Doxygen-users] doxygen for CodeWarrior?

[Luigi B. <bal...@ma...>]

Hi Uwe,

At 11:20 PM 1/10/02 -0800, Uwe Behrens wrote:
>Now for my question: Is anybody aware of a port of doxygen as a plug-in
>for CodeWarrior on MacOS (pre OS X)?  I would like to use it on the
>Macintosh, and the most useful way of doing so seems to have it
>integrated in the IDE.

I would like to see this as well. However the main problem is, Doxygen 
delegates to other programs to do part of the work, such as ghostscript, 
dot, and epstopdf. Apart from the latter having been ported to the 
Macintosh (I'm aware of ghostscript and epstopdf ports, but not of dot), if 
I'm not mistaken, currently Doxygen drives the ancillary programs by 
building the corresponding command line and telling the system to execute 
it. But there's no such thing as a command line on MacOS classic---the way 
for programs to drive each other and in general to communicate is to 
exchange AppleEvents, which should be added to Doxygen from scratch.

However, there's always the possibility that you volunteer for that :)

Bye,
         Luigi

[Doxygen-users] doxygen for CodeWarrior?

[Uwe B. <ube...@d2...>]

Dear list!

Since I'm new on this list, let me briefly introduce myself: My name is
Uwe Behrens, and I'm a Graphics Engineer with Digital Domain, a major
Visual Effects Studio in Venice, California.  We use doxygen for all our
internal software projects.

Now for my question: Is anybody aware of a port of doxygen as a plug-in
for CodeWarrior on MacOS (pre OS X)?  I would like to use it on the
Macintosh, and the most useful way of doing so seems to have it
integrated in the IDE.

Thanks in advance.

-- 
______________________________________________________________________
Uwe Behrens <be...@ac...>                  (aka <ube...@d2...>)

RE: [Doxygen-users] Question on generated HTML header

[Glenn M. <gle...@vo...>]

Funny you should ask. I'm entering the final stages of documenting some
Perl code I wrote just for this task. I've gotten permission to
open-source it. (yeah!!!)

It does more than just remove the Doxygen navigation. It creates a
complete HTML system that can be comprised of multiple Doxygen builds as
well as single-sourced output from FrameMaker. It auto-generates the
table of contents and index. It handles navigation (buttons) at the top
of each file.

I hope to post it to this list.

Keep tabs on me... I'm getting close to getting it done in a releasable
fashion. We're talking, I hope to have a version for our internal
company review by next week. Then I can post it to this list (with the
admin's approval) and can send it to others.

Hasta luego,

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...


> -----Original Message-----
> From: Jaap Suter [mailto:s98...@ho...]
> Sent: Thursday, January 10, 2002 12:45 PM
> To: dox...@li...
> Subject: [Doxygen-users] Question on generated HTML header
>=20
>=20
> Hello,
>=20
> I have a question regarding the generated HTML header. I am=20
> already using=20
> the HTML_HEADER tag but below that I'm getting the by Doxygen=20
> generated bar=20
> with info which looks like this at the moment:
>=20
> Main Page   Modules   Data Structures   File List   Data=20
> Fields   Globals  =20
> Related Pages
=20
<snip>

> Is that even possible without building my own Doxygen, or=20
> fiddling with the=20
> HTML output myself?
>=20
> Maybe it's in the Docs, but I coulnd't find it. Sorry if it's=20
> actually=20
> there.
>=20
> Thanks for your help.
>=20
> Regards,
>=20
> Jape

[Doxygen-users] Question on generated HTML header

[Jaap S. <s98...@ho...>]

Hello,

I have a question regarding the generated HTML header. I am already using 
the HTML_HEADER tag but below that I'm getting the by Doxygen generated bar 
with info which looks like this at the moment:

Main Page   Modules   Data Structures   File List   Data Fields   Globals   
Related Pages

I'm using the OPTIMIZE_OUTPUT_FOR_C tag (Because I'm not using C++ at the 
moment), which explains the modules and data structures links there.

But I'm wondering whether I can influence what appears in that bar. For 
example the 'Globals' and 'Data fields' are not very handy/usefull imho. Now 
I could change every HTML file by hand (or write a little tool) to remove 
these, but maybe there is some setting for it?

But I'd like to go even further. I'd love to see a list of global functions 
only, instead of all globals (variables + functions). And have a new link in 
the top bar that says: Functions. It's very funny actually cause the 'Data 
fields' link points to a html file named functions.html. But it contains 
information on which member belongs to which datastructure (not very usefull 
imho).

Is that even possible without building my own Doxygen, or fiddling with the 
HTML output myself?

Maybe it's in the Docs, but I coulnd't find it. Sorry if it's actually 
there.

Thanks for your help.

Regards,

Jape

_________________________________________________________________
Chat on line met vrienden en probeer MSN Messenger uit: 
http://messenger.msn.nl

[Doxygen-users] (no subject)

[Audrey S. <as...@ul...>]

How can I do to create a reference to the number of a figure for LateX
documentation?
=20
---------------------------------
Audrey Simon
Service de m=E9canique analytique et CFAO
50, av. F.D. Roosevelt - CP 165/14
1050 Bruxelles
---------------------------------
T=E9l :  +32-2-650.47.66
Fax : +32-2-650.47.24
E-mail :  <mailto:aud...@ul...> aud...@ul...
=20