doxygen-users — List for users of doxygen

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Sparr <sp...@gm...>]

I want to give this a try, but apparently GitHub won't let me give your app
permission to access just one of the organizations I'm part of. That's a
deal breaker for me; not that I don't trust your app, but I don't give any
access to some organizations.

On Tue, Jan 5, 2016 at 5:56 PM, Paul Novotny <pa...@pa...> wrote:

> Hello,
>
> I put together a GitHub integration for generating and hosting Doxygen
> docs for your public GitHub repositories. Consider this an early
> prototype, but I would like to get some testers and feedback. Just go
> to:
>
>   https://codedocs.xyz/
>
> You should see a list of your public repositories. Then enable the
> repositories you want Doxygen generated for. A GitHub hook is added, so
> the documentation is rebuilt every time you push changes to GitHub. You
> can add badges to your README.md (like Coverity, Travis-CI, etc) that
> point to the documentation that is hosted on codedocs.xyz. For example,
> look at my OpenSceneGraph and Doxygen forks:
>
>   https://github.com/paulnovo/osg
>   https://github.com/paulnovo/doxygen
>
> I added the "code: documented" badges to the README.md that point to the
> latest Doxgyen documentation:
>
>   https://codedocs.xyz/paulnovo/osg/
>   https://codedocs.xyz/paulnovo/doxygen/
>
> Let me know what you think. Hopefully this will be useful for Doxygen
> users.
>
> -Paul
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Paul N. <pa...@pa...>]

On Thu, 2016-01-07 at 11:49 -0500, Allen Winter wrote:
> On Wednesday, January 06, 2016 10:59:07 PM Paul Novotny wrote:
> > On Wed, Jan 6, 2016, at 06:51 PM, Allen Winter wrote:
> > > I have a lot of ideas and thoughts.
> > > Here are a few:
> > > 1) some of my repos are under my github login I'd like to be able
> > > to create codedocs for my other projects that are not under my
> > > login.
> > > For example: https://github.com/libical/libical
> > 
> > Currently, you could do this by forking these repositories. But I
> > also
> > would like some way to have the Doxgyen docs for repos that aren't
> > mine.
> > Like OpenSceneGraph. I'll think about this a bit.
> > 
> see travis-ci.org which allows me to choose repos from any
> organization I belong to.

Oh, I misunderstood your question. Yes, there is no support for
repositories in organizations you belong to, but it is what I am
working on now. So stay tuned.

-Paul

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Allen W. <wi...@kd...>]

On Wednesday, January 06, 2016 10:59:07 PM Paul Novotny wrote:
> On Wed, Jan 6, 2016, at 06:51 PM, Allen Winter wrote:
> > I have a lot of ideas and thoughts.
> > Here are a few:
> > 1) some of my repos are under my github login I'd like to be able
> > to create codedocs for my other projects that are not under my login.
> > For example: https://github.com/libical/libical
> 
> Currently, you could do this by forking these repositories. But I also
> would like some way to have the Doxgyen docs for repos that aren't mine.
> Like OpenSceneGraph. I'll think about this a bit.
> 
see travis-ci.org which allows me to choose repos from any organization I belong to.

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Paul N. <pa...@pa...>]

On Thu, 2016-01-07 at 09:47 +0100, Baptiste Wicht wrote:
> Hi Paul,
> 
> This is an excellent idea :)
> 
> I may be doing something wrong, but when I go on the site, only some
> of
> my repositories are displayed, it seems the first X in alphabetical
> order. Is there a limit ?
> 
> The projects I wanted to tests are not displayed.

112 repositories, wow, you are a good tester. :-) It looks like github
is sending me repositories in bunches, but I never knew that since all
the repositories always fit into the first bunch. I should have a fix
up shortly.

-Paul

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Baptiste W. <bap...@gm...>]

On Tue, Jan 05, 2016 at 08:56:26PM -0500, Paul Novotny wrote:
> Hello,
>
> I put together a GitHub integration for generating and hosting Doxygen
> docs for your public GitHub repositories. Consider this an early
> prototype, but I would like to get some testers and feedback. Just go
> to:
>
>   https://codedocs.xyz/
>
> You should see a list of your public repositories. Then enable the
> repositories you want Doxygen generated for. A GitHub hook is added, so
> the documentation is rebuilt every time you push changes to GitHub. You
> can add badges to your README.md (like Coverity, Travis-CI, etc) that
> point to the documentation that is hosted on codedocs.xyz. For example,
> look at my OpenSceneGraph and Doxygen forks:
>
> ....
>
> Let me know what you think. Hopefully this will be useful for Doxygen
> users.
>
> -Paul

Hi Paul,

This is an excellent idea :)

I may be doing something wrong, but when I go on the site, only some of
my repositories are displayed, it seems the first X in alphabetical
order. Is there a limit ?

The projects I wanted to tests are not displayed.

Thanks

Baptiste Wicht

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Paul N. <pa...@pa...>]

On Wed, Jan 6, 2016, at 06:51 PM, Allen Winter wrote:
> I have a lot of ideas and thoughts.
> Here are a few:
> 1) some of my repos are under my github login I'd like to be able
> to create codedocs for my other projects that are not under my login.
> For example: https://github.com/libical/libical

Currently, you could do this by forking these repositories. But I also
would like some way to have the Doxgyen docs for repos that aren't mine.
Like OpenSceneGraph. I'll think about this a bit.

> 2) I wonder if you could look for an existing Doxyfile at the top-level
> instead of looking at .codedocs.  one of my projects has a docs/Doxyfile

See my previous email in response to Peter. I think his idea of putting
in a config file that points to the Doxyfile location is probably the
way to handle this.

> 3) could we start collect project tags files and somehow automatically
> (or at least by Doxyfile) start linking together the dox of all projects
> from one convenient location :)

Oh boy! The master-dox.

> This is most wonderful idea and I'm happy to continue testing.

Thank you!

-Paul

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Paul N. <pa...@pa...>]

Allen and Peter, thanks for trying it out. Yes, at the moment, the
.codedocs is a minimal set of Doxygen configuration settings. Partly
because I am hesitant to allow them all without looking into them first
and making sure they work (ie, I have the environment setup correctly
for them to work). So please suggest options you would like and I will
enable them.

Creating an option to point to the location of the doxygen config file
is a good idea. I still would have to parse the pointed to doxygen
config file to make sure there aren't any issues, ie having an unchecked
INPUT setting is not a great idea.

-Paul


On Wed, Jan 6, 2016, at 07:17 PM, Peter Barnes wrote:
> +1.  Ours is at doc/doxygen.conf
> 
> It looks like the .codedocs file is intended to be a minimal Doxygen configuration.  What about adding a (non-Doxygen) keyword to point to the project-specific Doxygen configuration file?
> 
> P
> 
>> On Jan 6, 2016, at 3:51 PM, Allen Winter <wi...@kd...> wrote:
>> 
>> 2) I wonder if you could look for an existing Doxyfile at the top-level
>> instead of looking at .codedocs.  one of my projects has a docs/Doxyfile
> 
> ____________
> Peter Barnes
> pd...@ma...
> ------------------------------------------------------------------------------
> _________________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Peter B. <pd...@ma...>]

+1.  Ours is at doc/doxygen.conf

It looks like the .codedocs file is intended to be a minimal Doxygen configuration.  What about adding a (non-Doxygen) keyword to point to the project-specific Doxygen configuration file?

P

> On Jan 6, 2016, at 3:51 PM, Allen Winter <wi...@kd...> wrote:
> 
> 2) I wonder if you could look for an existing Doxyfile at the top-level
> instead of looking at .codedocs.  one of my projects has a docs/Doxyfile

____________
Peter Barnes
pd...@ma... <mailto:pd...@ma...>

Re: [Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Allen W. <wi...@kd...>]

On Tuesday, January 05, 2016 08:56:26 PM Paul Novotny wrote:
> Hello,
> 
> I put together a GitHub integration for generating and hosting Doxygen
> docs for your public GitHub repositories. Consider this an early
> prototype, but I would like to get some testers and feedback. Just go
> to:
> 
>   https://codedocs.xyz/
> 
Most awesome idea.
I successfully created apidox from one of my forks.

I have a lot of ideas and thoughts.
Here are a few:
1) some of my repos are under my github login I'd like to be able
to create codedocs for my other projects that are not under my login.
For example: https://github.com/libical/libical

2) I wonder if you could look for an existing Doxyfile at the top-level
instead of looking at .codedocs.  one of my projects has a docs/Doxyfile

3) could we start collect project tags files and somehow automatically
(or at least by Doxyfile) start linking together the dox of all projects
from one convenient location :)

This is most wonderful idea and I'm happy to continue testing.

-Allen



> You should see a list of your public repositories. Then enable the
> repositories you want Doxygen generated for. A GitHub hook is added, so
> the documentation is rebuilt every time you push changes to GitHub. You
> can add badges to your README.md (like Coverity, Travis-CI, etc) that
> point to the documentation that is hosted on codedocs.xyz. For example,
> look at my OpenSceneGraph and Doxygen forks:
> 
>   https://github.com/paulnovo/osg
>   https://github.com/paulnovo/doxygen
> 
> I added the "code: documented" badges to the README.md that point to the
> latest Doxgyen documentation:
> 
>   https://codedocs.xyz/paulnovo/osg/
>   https://codedocs.xyz/paulnovo/doxygen/
> 
> Let me know what you think. Hopefully this will be useful for Doxygen
> users.
> 
> -Paul
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Looking for beta testers of a Doxygen GitHub integration

[Paul N. <pa...@pa...>]

Hello,

I put together a GitHub integration for generating and hosting Doxygen
docs for your public GitHub repositories. Consider this an early
prototype, but I would like to get some testers and feedback. Just go
to:

  https://codedocs.xyz/

You should see a list of your public repositories. Then enable the
repositories you want Doxygen generated for. A GitHub hook is added, so
the documentation is rebuilt every time you push changes to GitHub. You
can add badges to your README.md (like Coverity, Travis-CI, etc) that
point to the documentation that is hosted on codedocs.xyz. For example,
look at my OpenSceneGraph and Doxygen forks:

  https://github.com/paulnovo/osg
  https://github.com/paulnovo/doxygen

I added the "code: documented" badges to the README.md that point to the
latest Doxgyen documentation:

  https://codedocs.xyz/paulnovo/osg/
  https://codedocs.xyz/paulnovo/doxygen/

Let me know what you think. Hopefully this will be useful for Doxygen
users.

-Paul

[Doxygen-users] unsubscribe

[Alfredo P. <mas...@ma...>]

unsubscribe


-- 
Alfredo Palhares
GPG/PGP Key Fingerprint
68FC B06A 6C22 8B9B F110
38D6 E8F7 4D1F 0763 CAAD

Re: [Doxygen-users] call graph problems

[Albert <alb...@gm...>]

Lorenz,

I've tested it with the 1.8.10 version now as well and I see that here the
graphs for method3/4 and method9/10 are missing. So I think it was a bug in
the 1.8.10 version.
(I don't think you were using 1.8.11 but 1.8.10 as doxygen 1.8.11 was
released on December 30,2015 and you didn't mentioning using the git
repository version.)

Albert

On Sat, Jan 2, 2016 at 8:49 PM, lorenz <lor...@ya...> wrote:

> Albert <albert.tests <at> gmail.com> writes:
> >
> > Lorenz,
> > Which version of doxygen are you using?
>
> I'm using 1.8.11 to on a win7-64 workstation
>
>
> > What are your flags that are different from the default Doxyfile?
>
>
> I'll post the doxyfile and the generated html as soon as I have access to
> the my workstation again (I tried to post them including the bitmaps, but
> that failed due to the size. And then I got distracted). But that won't be
> before the 11th (on vacation in the moment 8-)
>
>
> > Using version 1.8.11 I see all graphs.
> > Note: why/what are the last 2 non-blank lines in your doxytest.cpp
> > pasted code.
>
> looks like remnants of a previous test.
>
>
> Thanks for looking into this.
> --
>
> Lorenz
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] call graph problems

[lorenz <lor...@ya...>]

Albert <albert.tests <at> gmail.com> writes:
> 
> Lorenz,
> Which version of doxygen are you using?

I'm using 1.8.11 to on a win7-64 workstation


> What are your flags that are different from the default Doxyfile?


I'll post the doxyfile and the generated html as soon as I have access to
the my workstation again (I tried to post them including the bitmaps, but
that failed due to the size. And then I got distracted). But that won't be
before the 11th (on vacation in the moment 8-)


> Using version 1.8.11 I see all graphs.
> Note: why/what are the last 2 non-blank lines in your doxytest.cpp
> pasted code.

looks like remnants of a previous test.


Thanks for looking into this.
-- 

Lorenz

Re: [Doxygen-users] call graph problems

[Albert <alb...@gm...>]

Lorenz,

Which version of doxygen are you using?
What are your flags that are different from the default Doxyfile?

Using version 1.8.11 I see all graphs.

Note: why/what are the last 2 non-blank lines in your doxytest.cpp pasted
code.

Albert

On Fri, Dec 11, 2015 at 1:26 PM, Lorenz <lor...@ya...> wrote:

> Hi all,
>
> I have a problem with call graph generation in a Cpp project.
>
> I some cases calls to methodes of the same class are not reflected in
> the graph.
>
> In the example below, call(er) graphs for method1/2, method 5/6 and
> method7/8 are generated, but not for method3/4 and method9/10.
>
>
> I would like to provide the complete example (including doxyfile and
> the generated html), but I don't seem to be able to attach it to my
> message (at least not when posting via gmane.org).
>
> So here is at least the sample source code:
>
> ===== doxytest.h =====
>
> namespace doxytest
> {
>
>   //! test class for doxygen experiments
>   //
>   class doxytest1
>   {
>     public:
>       void method1 (void);
>       void method2 (void);
>       void method3 (void);
>       void method4 (void);
>       void method5 (void);
>       void method6 (void);
>       void method7 (void);
>       void method8 (void);
>       void method9 (void);
>       void method10 (void);
>   };
>
> } //namepspace
>
> ===== doxytest.cpp =====
>
> #include "doxytest.h"
>
> void doxytest::doxytest1::method1 (void)
> {
>   method2();
> }
>
> void doxytest::doxytest1::method2 (void)
> {
> }
>
> void doxytest::doxytest1::method3 (void)
> {
>   method4();
> }
>
> void doxytest::doxytest1::method4 (void)
> {
> }
>
> namespace doxytest
> {
>   void doxytest1::method5 (void)
>   {
>     method6();
>   }
>
>   void doxytest1::method6 (void)
>   {
>   }
> }
>
> void doxytest::doxytest1::method7 (void)
> {
>   method8();
> }
>
> void doxytest::doxytest1::method8 (void)
> {
> }
>
> void doxytest::doxytest1::method9 (void)
> {
>   method10();
> }
>
> void doxytest::doxytest1::method10 (void)
> {
> }
> namespace doxytest
> {
>
> ==========
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] "Modules" main display not fully detailed...

[Monique S. <mon...@ea...>]

Hello, Doxygen Users,

(Using Doxygen 1.8.10, on Windows 7, 64-bit)

When I started this message, it was about my old wish to suppress the automatic prepending of the \brief to the \details in the output of a \page block.

But as I looked more closely so I could explain it all in detail, I realized that I’ve got a bigger issue to solve: the display of the Modules tab, even when showing the most detail available (for my output, detail level 3), is incomplete, even though it’s complete in the left pane’s treeview. (I have GENERATE_TREEVIEW = YES.)

That is, the left treeview shows everything as expected:
* Modules > <product-that-I-treat-as-module> > Functions > <function-groups> > <individual-functions>
* Modules > <product-that-I-treat-as-module> > Pages > <page-groups> > <individual-pages>

But in the right pane, accessed by clicking the Modules tab, the Functions and Pages groups expand *only if* there are more *groups* underneath them, but not down to the level of the <individual-functions> or <individual-pages>. And if there are no <page-groups>, the right pane goes only to the level of “Pages” (not the <individual-pages>). Likewise for <function-groups>: if there are no function groups, the right pane goes only to the level of “Functions”.

I guess it isn’t really necessary for the right Modules pane to show the <individual-functions> or <individual-pages>, but I’d like to know if this is by-design or if there’s a configuration setting that controls this?

If I can’t display the <individual-functions> or <individual-pages>, then it seems that the \brief description for \page blocks doesn’t actually appear anywhere?

If that’s the case, then I can simply not use the \brief for the \page comments, and the issue I was facing (having the \brief prepended to the \details in the output of a \page) disappears :-).

But if I can get the Modules pane to show the <individual-functions> or <individual-pages>, I’d need to try to suppress the \brief prepending.

The reason that I think I should be able to get this to work is that it works properly for the \dir comment block. For \dir comments, the \brief appears in the Modules pane as expected, and as expected (and preferred) it does not appear in the Detailed Description output for the \dir display.

Thoughts?

----
Following are things that were mentioned/tried when I first posted the problem of trying to suppress the prepended \brief for a \page so that it behaved the same as a \dir comment:

(Using Doxygen 1.8.10)

* Standard behavior of the \brief and \details commands for class and file members is to prepend the \brief to the \details, described here: https://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmdbrief.

* Set REPEAT_BRIEF=NO. This works for the .c/.h files’ Doxygen-comment blocks, as well as \dir comment blocks. But it’s not working for \page blocks (which are in separate .page files, parsed as .c files via the EXTENSION_MAPPING setting, “page=C”).

* Someone suggested that I have a look at the possibilities of the doxygen layout file? (doxygen -l and the LAYOUT_FILE setting in the Doxyfile). I did, but none of the existing layouts seem applicable. There are layout definitions for the following types of pages: class, namespace, file, group, and directory. But nothing for a “page” page. Nonetheless, I tried creating a new element, <pages> (because this is the value of “type” for one of the <tab> elements in the <navindex>), at the same level as <directory>, with all the same values except for setting the <briefdescription> element’s “visible” attribute value to “no”. But then when I run doxygen with this layout file (via the doxywizard), I get error like this:

“Unexpected start tag ‘page’ found in scope=’(null)’!

So the layout of a \page page file seems to be controlled by some other mechanism?

* I tried setting the <briefdescription> element’s “visible” attribute to “no” for the <file> layout, on the supposition that perhaps the file page layout might also apply to any page that’s created by the \page command, but it had no apparent effect.

* I’m guessing that to do what I’m wishing, I’d have to go the XML route, as the manual describes: http://www.stack.nl/~dimitri/doxygen/manual/customize.html#xmlgenerator. My wish is pretty small, though, and certainly too small to justify a big effort to customize XML parsing.
----

Thanks very much,
-Monique

Re: [Doxygen-users] js files not included in jenkins

[incady <an...@sg...>]

The issue is that the most recent Jenkins build has default security settings
that disable the loading of javascript.



--
View this message in context: http://doxygen.10944.n7.nabble.com/js-files-not-included-in-jenkins-tp7487p7492.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Problems by new exit code 2 if warnings found

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

Hi Jens,

> On 19 Dec 2015, at 22:15 , Schleusener, Jens <Jen...@t-...> wrote:
> 
> Hi,
> 
> after I installed at last Thursday evening doxygen's latest Github version 
> on a server that offers FOSS software I got errors while the 
> semi-automatic generation of the according Doxygen documentation for new 
> added software packages.
> 
> It takes me some time to find out that doxygen after the recent addition 
> of the WARN_AS_ERROR option now set a return code of 2 instead of before 0 
> if some warnings occur and WARN_AS_ERROR is set to NO (the default).

I've just reverted the change that caused doxygen to return error code 2 on a warning.

Regards,
  Dimitri

[Doxygen-users] Problems by new exit code 2 if warnings found

[Schleusener, J. <Jen...@t-...>]

Hi,

after I installed at last Thursday evening doxygen's latest Github version 
on a server that offers FOSS software I got errors while the 
semi-automatic generation of the according Doxygen documentation for new 
added software packages.

It takes me some time to find out that doxygen after the recent addition 
of the WARN_AS_ERROR option now set a return code of 2 instead of before 0 
if some warnings occur and WARN_AS_ERROR is set to NO (the default).

Since for some software packages doxygen ends errorneously with the error 
message

  input buffer overflow, can't enlarge buffer because scanner uses REJECT

that is caused (as described in the FAQ) probably by doxygen's lexical 
scanner I checked in my self-written according wrapper script for the 
heuristically found exit code 2 and try than to exclude all member files 
of the processed package files with the problematic too long input lines 
(> 256K characters, checked in the script by "wc -L") and try to run then 
doxygen again. That exit code "2" I found also described at

  http://marc.info/?l=doxygen-users&m=126909030104387&w=2

as set especially for "flex internal errors", all other errors got "1".

But nearly for all packages on the mentioned server doxygen issues some 
warnings so that the described check now fails since doxygen nearly always 
ends with an exit code of 2.

If I change just for testing in src/message.cpp

  Doxygen::exitCode = 2;

to

  Doxygen::exitCode = 0;

in order to force the old behaviour all works well again.

Maybe it is meaningful to choose for doxygen warnings an alternate exit 
code different to "2"?

Regards

Jens

Re: [Doxygen-users] js files not included in jenkins

[Albert <alb...@gm...>]

I think searching for Chrome and allow scripts will give some hints.
Google Chrome the option --allow-file-access-from-files should be used to
overcome the problem that javascript is not executed as Google Chrome
browser will not load local file by default due to security reason.

Albert

On Sat, Dec 19, 2015 at 12:39 AM, incady <an...@sg...> wrote:

> A bit more info - the developer tools in Chrome is showing this error:
>
> Blocked script execution in '...' because the document's frame is sandboxed
> and the 'allow-scripts' permission is not set.
>
>
>
>
>
> --
> View this message in context:
> http://doxygen.10944.n7.nabble.com/js-files-not-included-in-jenkins-tp7487p7488.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] js files not included in jenkins

[incady <an...@sg...>]

A bit more info - the developer tools in Chrome is showing this error:

Blocked script execution in '...' because the document's frame is sandboxed
and the 'allow-scripts' permission is not set.





--
View this message in context: http://doxygen.10944.n7.nabble.com/js-files-not-included-in-jenkins-tp7487p7488.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] js files not included in jenkins

[incady <an...@sg...>]

I'm running a Jenkins build with the Doxygen plugin on a Centos instance, and
for some reason, the js files aren't getting included. When I click on the
toggle arrows, nothing happens. If I load up the Chrome debugger, no js
files are loaded (ie, the dynsections.js file isn't listed as a source
file). I've set up Jenkins with Doxygen on my Mac, and it runs fine. Anyone
run into anything similar?



--
View this message in context: http://doxygen.10944.n7.nabble.com/js-files-not-included-in-jenkins-tp7487.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] SHOW_USED_FILES equivalent for C functions, pages, dirs ?

[Monique S. <mon...@ea...>]

Hello, Doxygen users,

In Doxygen 1.8.10 (on Windows 7, but I doubt that matters), setting SHOW_USED_FILES = YES results in a nice info message for classes and structs that tells which file/s were used to generate the Doxygen output page: “The documentation for this struct was generated from the following file: ”.

I’d like to get a similar message for functions (I’m documenting a C codebase, not C++, so no classes; and the OPTIMIZE_OUTPUT_FOR_C setting is YES), .page file output, and .dir file output. Is that possible with any existing Doxygen settings?

If not, I could manually add the text to all Doxygen blocks, but I’d like to avoid that!

I realize that users could navigate through the Files > Globals > Functions to get to the big index-like page that lists all the functions and in which file they are. But all the functions are in groups, under the Modules tab/left-nav-tree. And I believe readers are much more likely to be looking at the output that way than by using the Files navigation method, especially because I renamed the “Modules” tab to be “Function Lists by Product”.

Thanks for any tips,
-Monique

[Doxygen-users] image in a table that's an href to another image ?

[Monique S. <mon...@ea...>]

Hello, Doxygen users,

It’s easy to include an @image in a <table>. And it’s easy to have an href in a <table> that resolves to an otherwise-referenced image (so that the image gets copied from the IMAGE_PATH to the doxygen\output directory).

But I can’t figure out how to include an @image in a <table> that’s set up as an <a href> to a not-otherwise-referenced image. Any tips?

It’s ok if I need to manually (well, via batch file/shell script) copy the not-otherwise-referenced images to the doxygen\output directory. In fact, I’m already doing that for PDF files that I want to link to. But it’s getting the <a href> to work for an image as opposed to text that’s not working for me.

The use case I’m working with is a table of thumbnail images that when clicked resolve to their large, detailed (non-thumbnail) versions.

I’ve been using the <table class=”table”> coding for my tables, with the usual <tr> and <td> elements. But if markdown would work, I’d switch. But all the markdown tables I’ve used so far always have grid lines and a table heading, neither of which I want.

Thanks for any tips,
-Monique

[Doxygen-users] Any plans for 1.8.11?

[Ingolf S. <ing...@gm...>]

Hi,

are there any concrete plans with respect to a new doxygen release
(possibly bugfix only)? In particular, I'm looking forward to the fix
for https://bugzilla.gnome.org/show_bug.cgi?id=755783

Kind regards
Ingolf

Just in case... I'm just asking. It is not my intention to urge someone.

[Doxygen-users] Links to identically named global functions

[Petr P. <pet...@se...>]

Hi all,

suppose I have several global functions with the same name, each in a 
different file. A typical example may be main() - is it possible to 
create links to main() inside a specific file?

I know that in case of modules I can easily distinguish by saying 
"module_a::main()", but I would need something like file.f::main(). 
Thanks for any comments.

Best regards,

Petr