doxygen-users Mailing List for Doxygen (Page 32)
Brought to you by:
dimitri
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(118) |
Jun
(150) |
Jul
(115) |
Aug
(75) |
Sep
(92) |
Oct
(102) |
Nov
(139) |
Dec
(87) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(131) |
Feb
(60) |
Mar
(114) |
Apr
(83) |
May
(125) |
Jun
(82) |
Jul
(95) |
Aug
(98) |
Sep
(109) |
Oct
(97) |
Nov
(72) |
Dec
(70) |
2003 |
Jan
(117) |
Feb
(122) |
Mar
(187) |
Apr
(114) |
May
(154) |
Jun
(131) |
Jul
(130) |
Aug
(98) |
Sep
(121) |
Oct
(107) |
Nov
(80) |
Dec
(54) |
2004 |
Jan
(78) |
Feb
(71) |
Mar
(118) |
Apr
(56) |
May
(56) |
Jun
(64) |
Jul
(164) |
Aug
(104) |
Sep
(101) |
Oct
(69) |
Nov
(107) |
Dec
(98) |
2005 |
Jan
(75) |
Feb
(77) |
Mar
(107) |
Apr
(114) |
May
(142) |
Jun
(106) |
Jul
(79) |
Aug
(108) |
Sep
(115) |
Oct
(140) |
Nov
(128) |
Dec
(63) |
2006 |
Jan
(86) |
Feb
(71) |
Mar
(125) |
Apr
(55) |
May
(48) |
Jun
(143) |
Jul
(99) |
Aug
(91) |
Sep
(93) |
Oct
(82) |
Nov
(46) |
Dec
(45) |
2007 |
Jan
(69) |
Feb
(97) |
Mar
(125) |
Apr
(112) |
May
(65) |
Jun
(80) |
Jul
(82) |
Aug
(84) |
Sep
(56) |
Oct
(74) |
Nov
(63) |
Dec
(74) |
2008 |
Jan
(161) |
Feb
(115) |
Mar
(58) |
Apr
(73) |
May
(58) |
Jun
(79) |
Jul
(57) |
Aug
(115) |
Sep
(79) |
Oct
(62) |
Nov
(93) |
Dec
(37) |
2009 |
Jan
(69) |
Feb
(115) |
Mar
(77) |
Apr
(85) |
May
(124) |
Jun
(58) |
Jul
(44) |
Aug
(85) |
Sep
(90) |
Oct
(80) |
Nov
(87) |
Dec
(48) |
2010 |
Jan
(52) |
Feb
(71) |
Mar
(54) |
Apr
(37) |
May
(66) |
Jun
(86) |
Jul
(84) |
Aug
(68) |
Sep
(94) |
Oct
(66) |
Nov
(36) |
Dec
(53) |
2011 |
Jan
(59) |
Feb
(77) |
Mar
(59) |
Apr
(67) |
May
(76) |
Jun
(54) |
Jul
(95) |
Aug
(92) |
Sep
(84) |
Oct
(72) |
Nov
(46) |
Dec
(60) |
2012 |
Jan
(43) |
Feb
(77) |
Mar
(88) |
Apr
(121) |
May
(81) |
Jun
(69) |
Jul
(97) |
Aug
(64) |
Sep
(55) |
Oct
(55) |
Nov
(38) |
Dec
(60) |
2013 |
Jan
(85) |
Feb
(70) |
Mar
(81) |
Apr
(83) |
May
(51) |
Jun
(65) |
Jul
(71) |
Aug
(39) |
Sep
(47) |
Oct
(32) |
Nov
(43) |
Dec
(28) |
2014 |
Jan
(64) |
Feb
(22) |
Mar
(54) |
Apr
(20) |
May
(59) |
Jun
(20) |
Jul
(50) |
Aug
(17) |
Sep
(37) |
Oct
(56) |
Nov
(40) |
Dec
(24) |
2015 |
Jan
(51) |
Feb
(29) |
Mar
(57) |
Apr
(31) |
May
(23) |
Jun
(50) |
Jul
(30) |
Aug
(66) |
Sep
(59) |
Oct
(21) |
Nov
(29) |
Dec
(12) |
2016 |
Jan
(33) |
Feb
(30) |
Mar
(19) |
Apr
(23) |
May
(16) |
Jun
(31) |
Jul
(17) |
Aug
(19) |
Sep
(21) |
Oct
(20) |
Nov
(15) |
Dec
(6) |
2017 |
Jan
(16) |
Feb
(13) |
Mar
(16) |
Apr
(23) |
May
(16) |
Jun
(5) |
Jul
(14) |
Aug
(13) |
Sep
(12) |
Oct
(11) |
Nov
(3) |
Dec
(6) |
2018 |
Jan
(4) |
Feb
(6) |
Mar
(5) |
Apr
(11) |
May
(26) |
Jun
(5) |
Jul
(10) |
Aug
(7) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
(7) |
2019 |
Jan
(17) |
Feb
(18) |
Mar
(5) |
Apr
(6) |
May
(3) |
Jun
|
Jul
(9) |
Aug
(19) |
Sep
(3) |
Oct
(1) |
Nov
(23) |
Dec
(5) |
2020 |
Jan
(7) |
Feb
(1) |
Mar
(7) |
Apr
(11) |
May
(8) |
Jun
(7) |
Jul
(10) |
Aug
(3) |
Sep
(4) |
Oct
(7) |
Nov
(6) |
Dec
|
2021 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(4) |
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(8) |
Dec
(3) |
2022 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(2) |
2023 |
Jan
(2) |
Feb
(5) |
Mar
(3) |
Apr
(7) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(5) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Christoph L. <chr...@li...> - 2015-11-25 19:42:44
|
Am 25.11.2015 um 12:58 schrieb Yngve Inntjore Levinsen: > Hi, > > Thanks for the suggestion. Yes that works, but the same readme file is > also used by e.g. the web page of the git repository. This web page > only understands markdown, not doxygen commands. > > My solution in the end was to rename the example scripts. I still > think this is somehow incorrect behaviour by doxygen though. I'm 100% with you there -- a similar issue that I've run into is that Doxygen tries to interpret tags within Markdown inline code (i.e. text delimited with backquotes), which makes it a PITA to write guidelines on how Doxygen should be used within a project. |
From: Yngve I. L. <yng...@es...> - 2015-11-25 11:58:24
|
<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi,<br> <br> Thanks for the suggestion. Yes that works, but the same readme file is also used by e.g. the web page of the git repository. This web page only understands markdown, not doxygen commands.<br> <br> My solution in the end was to rename the example scripts. I still think this is somehow incorrect behaviour by doxygen though.<br> <br> Cheers,<br> Yngve<br> <br> <div class="moz-cite-prefix">On 24/11/15 20:05, Albert wrote:<br> </div> <blockquote cite="mid:CAB...@ma..." type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <div dir="ltr"> <div>Yngve,<br> </div> <div><br> When there is is no objection to using normal doxygen commands you could use \code and \endcond or \verbatim \endverbatim<br> <br> </div> Albert<br> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Tue, Nov 24, 2015 at 12:05 PM, Yngve Inntjore Levinsen <span dir="ltr"><<a moz-do-not-send="true" href="mailto:yng...@es..." target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:yng...@es...">yng...@es...</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div bgcolor="#FFFFFF" text="#000000"> Hi all,<br> <br> I am having an issue with backslash in markdown file which I am starting to wonder if is a bug. My README.md which I want to include as front page looks like this (simplified to make it clear):<br> <br> <blockquote type="cite"># MyCode Version 1.0.0<br> <br> <br> ## INSTALLATION INSTRUCTIONS<br> <br> The compiling is based on CMake. To build the executables, run<br> ```<br> mkdir build<br> cd build<br> cmake ..<br> make<br> ```<br> <br> ## EXAMPLES<br> <br> <br> Run examples by typing:<br> ```<br> build\mycode examples\<a moz-do-not-send="true" href="http://example1.in" target="_blank">example1.in</a><br> ```<br> and<br> ```<br> build\mycode examples\<a moz-do-not-send="true" href="http://example2.in" target="_blank">example2.in</a><br> ```<br> <br> Some other information...</blockquote> <br> The trouble here I suspect, is that \example <file> is a <a moz-do-not-send="true" href="http://www.stack.nl/%7Edimitri/doxygen/manual/commands.html#cmdexample" target="_blank">command in Doxygen</a>. Doxygen thinks I want to include files <a moz-do-not-send="true" href="http://1.in" target="_blank">1.in</a> and <a moz-do-not-send="true" href="http://2.in" target="_blank">2.in</a> as examples (?). I should escape this by using \\ if I understand correctly. This does work in markdown if I do it outside the 'code-block', but inside the code block I then see two backslash also in the generated output. I tried to find a way to globally ignore backslash in doxygen (and only rely on @), but I could not find that.<br> <br> Could someone perhaps help me explain what I do wrong?<br> <br> Cheers,<br> Yngve<br> <br> </div> <br> ------------------------------------------------------------------------------<br> Go from Idea to Many App Stores Faster with Intel(R) XDK<br> Give your users amazing mobile app experiences with Intel(R) XDK.<br> Use one codebase in this all-in-one HTML5 development environment.<br> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.<br> <a moz-do-not-send="true" href="http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140" rel="noreferrer" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140</a><br> _______________________________________________<br> Doxygen-users mailing list<br> <a moz-do-not-send="true" href="mailto:Dox...@li...">Dox...@li...</a><br> <a moz-do-not-send="true" href="https://lists.sourceforge.net/lists/listinfo/doxygen-users" rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/doxygen-users</a><br> <br> </blockquote> </div> <br> </div> </blockquote> <br> </body> </html> |
From: Albert <alb...@gm...> - 2015-11-24 19:05:35
|
Yngve, When there is is no objection to using normal doxygen commands you could use \code and \endcond or \verbatim \endverbatim Albert On Tue, Nov 24, 2015 at 12:05 PM, Yngve Inntjore Levinsen < yng...@es...> wrote: > Hi all, > > I am having an issue with backslash in markdown file which I am starting > to wonder if is a bug. My README.md which I want to include as front page > looks like this (simplified to make it clear): > > # MyCode Version 1.0.0 > > > ## INSTALLATION INSTRUCTIONS > > The compiling is based on CMake. To build the executables, run > ``` > mkdir build > cd build > cmake .. > make > ``` > > ## EXAMPLES > > > Run examples by typing: > ``` > build\mycode examples\example1.in > ``` > and > ``` > build\mycode examples\example2.in > ``` > > Some other information... > > > The trouble here I suspect, is that \example <file> is a command in > Doxygen > <http://www.stack.nl/%7Edimitri/doxygen/manual/commands.html#cmdexample>. > Doxygen thinks I want to include files 1.in and 2.in as examples (?). I > should escape this by using \\ if I understand correctly. This does work in > markdown if I do it outside the 'code-block', but inside the code block I > then see two backslash also in the generated output. I tried to find a way > to globally ignore backslash in doxygen (and only rely on @), but I could > not find that. > > Could someone perhaps help me explain what I do wrong? > > Cheers, > Yngve > > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple > OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
From: Yngve I. L. <yng...@es...> - 2015-11-24 11:05:47
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi all,<br> <br> I am having an issue with backslash in markdown file which I am starting to wonder if is a bug. My README.md which I want to include as front page looks like this (simplified to make it clear):<br> <br> <blockquote type="cite"># MyCode Version 1.0.0<br> <br> <br> ## INSTALLATION INSTRUCTIONS<br> <br> The compiling is based on CMake. To build the executables, run<br> ```<br> mkdir build<br> cd build<br> cmake ..<br> make<br> ```<br> <br> ## EXAMPLES<br> <br> <br> Run examples by typing:<br> ```<br> build\mycode examples\example1.in<br> ```<br> and<br> ```<br> build\mycode examples\example2.in<br> ```<br> <br> Some other information...</blockquote> <br> The trouble here I suspect, is that \example <file> is a <a href="http://www.stack.nl/%7Edimitri/doxygen/manual/commands.html#cmdexample">command in Doxygen</a>. Doxygen thinks I want to include files 1.in and 2.in as examples (?). I should escape this by using \\ if I understand correctly. This does work in markdown if I do it outside the 'code-block', but inside the code block I then see two backslash also in the generated output. I tried to find a way to globally ignore backslash in doxygen (and only rely on @), but I could not find that.<br> <br> Could someone perhaps help me explain what I do wrong?<br> <br> Cheers,<br> Yngve<br> <br> </body> </html> |
From: Zack S. <za...@gm...> - 2015-11-18 21:45:40
|
Hi there, what is the best way to embed the html output of doxygen on a website directly? That means, I have my website with its own navigation bar and then I place below the html output. Preferred in a similar style like the website. Regards, Zack |
From: Ron W <ron...@gm...> - 2015-11-17 16:46:39
|
On Mon, Nov 16, 2015 at 11:59 PM, < dox...@li...> wrote: > > Date: Mon, 16 Nov 2015 20:58:50 -0800 > From: "Monique Semp" <mon...@ea...> > Subject: [Doxygen-users] different editor colors for Doxygen comments > vs. "regular" comments ? > > Does anyone have recommendations for editors that have syntax highlighting > that differentiates between Doxygen block comments and other comments? > > Recently I found that Notepad++ makes it easy to choose different colors > for ?regular? comments vs. ?other comments?, such as Doxygen blocks. It?s > quite a nice thing to be able to quickly scroll through a file and see > which functions/etc. have Doxygen blocks and which ones don?t. > Eclipse (eclipse.org) supports different highlighting for different comment type. Also, any editor or IDE base on Scintilla (like notepad++ is) should, too. See: http://www.scintilla.org/ScintillaRelated.html |
From: Monique S. <mon...@ea...> - 2015-11-17 16:33:56
|
Ah, I’ll check that (EMACS color coding for Doxygen) out. And I just discovered this useful page in the Doxygen documentation: https://www.stack.nl/~dimitri/doxygen/helpers.html#dox_editoraddons. (I’m a tech writer; I should know to read the documentation!) So lots to try. -Monique |
From: Peter B. <pd...@ma...> - 2015-11-17 14:54:55
|
There is a syntax file for emacs which recognizes Doxygen blocks, as well as all the keywords and some syntax (such as "\param variable The foobar argument...") Just search the web for emacs Doxygen and you'll find the file. Peter ------------------ pd...@ma... > On Nov 16, 2015, at 8:58 PM, Monique Semp <mon...@ea...> wrote: > > Hello, Doxygen users, > > Does anyone have recommendations for editors that have syntax highlighting that differentiates between Doxygen block comments and other comments? > > Recently I found that Notepad++ makes it easy to choose different colors for “regular” comments vs. “other comments”, such as Doxygen blocks. It’s quite a nice thing to be able to quickly scroll through a file and see which functions/etc. have Doxygen blocks and which ones don’t. > > But I prefer to use a more project-oriented coding editor, such as Sublime Text. Sublime Text is infinitely customizable, with tons of color and syntax themes. But I haven’t found a way to achieve different syntax colors for the Doxygen blocks than for the other comment blocks. I have some leads that I might try (https://packagecontrol.io/packages/DoxyDoc and https://github.com/hsmederod/DoxygenSyntax), but I thought it worth querying this list before investing a lot of time. > > Thanks for your advice and info, > -Monique > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users |
From: Leif J. <le...@cr...> - 2015-11-17 10:32:05
|
Hi, I want to make some of my Doxygen document "put in a box" so it clearly stands out from the rest of the document. I still want processing of doxygen commands within that block. I tried with '<div align=center style="..."><div align=left style="...."> block contents </div></div>' which worked fine for the first block, but when I have more of this kind of constructs, doxygen mixes up the <div...></div> and indents blocks within each other. I don't seem to be able to find 'native' doxygen commands to do this. I tried \code and \verbatim but those do not process doxygen commands (obviously). Any ideas ? Leif |
From: Monique S. <mon...@ea...> - 2015-11-17 04:59:08
|
Hello, Doxygen users, Does anyone have recommendations for editors that have syntax highlighting that differentiates between Doxygen block comments and other comments? Recently I found that Notepad++ makes it easy to choose different colors for “regular” comments vs. “other comments”, such as Doxygen blocks. It’s quite a nice thing to be able to quickly scroll through a file and see which functions/etc. have Doxygen blocks and which ones don’t. But I prefer to use a more project-oriented coding editor, such as Sublime Text. Sublime Text is infinitely customizable, with tons of color and syntax themes. But I haven’t found a way to achieve different syntax colors for the Doxygen blocks than for the other comment blocks. I have some leads that I might try (https://packagecontrol.io/packages/DoxyDoc and https://github.com/hsmederod/DoxygenSyntax), but I thought it worth querying this list before investing a lot of time. Thanks for your advice and info, -Monique |
From: Juan P. R. B. <jpr...@ho...> - 2015-11-16 20:42:04
|
Hi everybody, I used @defgroup and @ingroup in order to create a nested-group hierarchy for my documentation. It works perfectly for the html output but it doesn't work at all for the LaTex output since all the groups are documented at the same hierarchy level. Does anybody know how to solve this problem? Thanks! |
From: <c....@po...> - 2015-11-15 23:13:59
|
On 2015-11-08 13:15 <c....@po...> wrote: > I try to use Doxygen with Python-code. But I have some problems with > the inheritance and how this is displayed in the generated docs. Could someone please test this if she/he has the same problems? -- GnuPGP-Key ID 0751A8EC |
From: Albert <alb...@gm...> - 2015-11-15 13:06:19
|
Regarding the problem of showing non documented functions etc. in the brief description section I've pushed a proposed solution github (pull request 411) Albert On Tue, Oct 13, 2015 at 3:13 PM, Petr Parik <pet...@se...> wrote: > Hi all, > > It seems Doxygen 1.8.10 does not work properly on Fortran modules. > > A. If a module is not documented it is not listed on the "file > reference" page (as expected) but all its functions/variables are (bug!). > > B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as > expected) but module private variables are (bug!). > > C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as > expected but are not "appended" to function/variable documentation. This > is only a nuisance. > > D. If a documented function (inside or outside a module) is followed by > one or more undocumented functions, the function calls in the following > undocumented functions are listed in "References" of the documented > function (bug!). > > Could this issues be adressed in the next version? Thanks :) > > Best regards, > > Petr > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Fabian N. <fab...@sc...> - 2015-11-10 11:27:41
|
Hi everyone, is there a way to visualize the dependencies between modules in a Fortran Code? I.e. visualize which module uses which other modules? Similar to a call-graph so to say. Regards, Fabian. |
From: Leif J. <le...@cr...> - 2015-11-10 10:15:02
|
Hi Clayton, Thanks that helped :-). I thought I already did that, but I was using a filter that didn't work. Leif ----- Original Message ----- > Leif, > > This worked recently for me: > > FILE_PATTERNS = *.js > > If you build the latest Doxygen from source, it should Just Work, no > FILE_PATTERNS required. Javascript is actually handled by core Doxygen, > and the above FILE_PATTERNS line is a work-around for a recently fixed > bug. > > Clayton > > On Mon, 9 Nov 2015 18:38:56 +0100 > Albert <alb...@gm...> wrote: > > > Leif, > > > > Did you try *.js with the input patterns? > > > > Albert > > > > On Mon, Nov 9, 2015 at 2:29 PM, Leif Jensen <le...@cr...> wrote: > > > > > Hello, > > > > > > We have used doxygen in many years for our C and java projects. > > > Now we got a new relative big project, that will be javascript (and > > > HTML5). I was looking at the home page (doxygen.org), but the links > > > for Extensions/Javascript (berlios.de) lead nowhere :-(. > > > > > > How do we make doxygen work with javascript code ? > > > > > > Leif > > > > > > > > > ------------------------------------------------------------------------------ > > > Presto, an open source distributed SQL query engine for big data, > > > initially developed by Facebook, enables you to easily query your > > > data on Hadoop in a more interactive manner. Teradata is also now > > > providing full enterprise support for Presto. Download a free open > > > source copy now. > > > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > > > _______________________________________________ Doxygen-users > > > mailing list Dox...@li... > > > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Clayton <cla...@gm...> - 2015-11-10 09:07:57
|
Leif, This worked recently for me: FILE_PATTERNS = *.js If you build the latest Doxygen from source, it should Just Work, no FILE_PATTERNS required. Javascript is actually handled by core Doxygen, and the above FILE_PATTERNS line is a work-around for a recently fixed bug. Clayton On Mon, 9 Nov 2015 18:38:56 +0100 Albert <alb...@gm...> wrote: > Leif, > > Did you try *.js with the input patterns? > > Albert > > On Mon, Nov 9, 2015 at 2:29 PM, Leif Jensen <le...@cr...> wrote: > > > Hello, > > > > We have used doxygen in many years for our C and java projects. > > Now we got a new relative big project, that will be javascript (and > > HTML5). I was looking at the home page (doxygen.org), but the links > > for Extensions/Javascript (berlios.de) lead nowhere :-(. > > > > How do we make doxygen work with javascript code ? > > > > Leif > > > > > > ------------------------------------------------------------------------------ > > Presto, an open source distributed SQL query engine for big data, > > initially developed by Facebook, enables you to easily query your > > data on Hadoop in a more interactive manner. Teradata is also now > > providing full enterprise support for Presto. Download a free open > > source copy now. > > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > > _______________________________________________ Doxygen-users > > mailing list Dox...@li... > > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
From: Leif J. <le...@cr...> - 2015-11-10 08:56:58
|
Hi Albert, Yes, I already tried that, but I can't see any effect :-(. Leif ----- Original Message ----- > Leif, > > Did you try *.js with the input patterns? > > Albert > > On Mon, Nov 9, 2015 at 2:29 PM, Leif Jensen <le...@cr...> wrote: > > > Hello, > > > > We have used doxygen in many years for our C and java projects. Now we > > got a new relative big project, that will be javascript (and HTML5). I was > > looking at the home page (doxygen.org), but the links for > > Extensions/Javascript (berlios.de) lead nowhere :-(. > > > > How do we make doxygen work with javascript code ? > > > > Leif > > > > > > ------------------------------------------------------------------------------ > > Presto, an open source distributed SQL query engine for big data, initially > > developed by Facebook, enables you to easily query your data on Hadoop in a > > more interactive manner. Teradata is also now providing full enterprise > > support for Presto. Download a free open source copy now. > > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > > _______________________________________________ > > Doxygen-users mailing list > > Dox...@li... > > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > > |
From: Albert <alb...@gm...> - 2015-11-09 17:39:04
|
Leif, Did you try *.js with the input patterns? Albert On Mon, Nov 9, 2015 at 2:29 PM, Leif Jensen <le...@cr...> wrote: > Hello, > > We have used doxygen in many years for our C and java projects. Now we > got a new relative big project, that will be javascript (and HTML5). I was > looking at the home page (doxygen.org), but the links for > Extensions/Javascript (berlios.de) lead nowhere :-(. > > How do we make doxygen work with javascript code ? > > Leif > > > ------------------------------------------------------------------------------ > Presto, an open source distributed SQL query engine for big data, initially > developed by Facebook, enables you to easily query your data on Hadoop in a > more interactive manner. Teradata is also now providing full enterprise > support for Presto. Download a free open source copy now. > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Leif J. <le...@cr...> - 2015-11-09 13:44:01
|
Hello, We have used doxygen in many years for our C and java projects. Now we got a new relative big project, that will be javascript (and HTML5). I was looking at the home page (doxygen.org), but the links for Extensions/Javascript (berlios.de) lead nowhere :-(. How do we make doxygen work with javascript code ? Leif |
From: Albert <alb...@gm...> - 2015-11-08 18:30:03
|
I've just pushed a proposed patch to github (pull request 409). This request is regarding the problems B and C. Albert On Sun, Nov 8, 2015 at 11:11 AM, Albert <alb...@gm...> wrote: > Dear Petr, > > Regarding problem A: > Can you please attach a self-contained example (source+config file in a > tar or zip) that allows me to reproduce the problem? > (Preferably as bug report at bugzilla ( > https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen) > > (It looks like that I can reproduce the problems B and C) > > Albert > > > On Tue, Oct 13, 2015 at 3:13 PM, Petr Parik <pet...@se...> wrote: > >> Hi all, >> >> It seems Doxygen 1.8.10 does not work properly on Fortran modules. >> >> A. If a module is not documented it is not listed on the "file >> reference" page (as expected) but all its functions/variables are (bug!). >> >> B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as >> expected) but module private variables are (bug!). >> >> C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as >> expected but are not "appended" to function/variable documentation. This >> is only a nuisance. >> >> D. If a documented function (inside or outside a module) is followed by >> one or more undocumented functions, the function calls in the following >> undocumented functions are listed in "References" of the documented >> function (bug!). >> >> Could this issues be adressed in the next version? Thanks :) >> >> Best regards, >> >> Petr >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Doxygen-users mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-users >> > > |
From: <c....@po...> - 2015-11-08 12:31:20
|
I try to use Doxygen with Python-code. But I have some problems with the inheritance and how this is displayed in the generated docs. I generated documentation with Doxygen (in default configuration) for the code below. But the problem is that a.ABase in the inheritance tree of B-docu is not linkable/clickable. Even when you look at the tree for a.ABase the class B is not shown. This depends on the existence of the __init__.py file. I don't know why. When I delete the __init__.py everything is fine. This are the files [__init__.py] #!/usr/bin/env python3 # -*- coding: utf-8 -*- [/__init__.py] [a.py] # -*- coding: utf-8 -*- """ classes of """ class ABase: """ bla """ pass class A(ABase): """ bla """ pass [/a.py] [b.py] # -*- coding: utf-8 -*- from .a import ABase class B(ABase): """ bla """ pass [/b.py] -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1 mQENBFQIluABCACfPwAhRAwFD3NXgv5CtVUGSiqdfJGVViVBqaKd+14E0pASA0MU G0Ewj7O7cGy/ZIoiZ0+lIEZmzJKHfuGwYhXjR/PhnUDrQIHLBvh9WuD6JQuULXfH kXtVm/i9wm76QAcvr2pwYgNzhcJntUHl2GcgnInYbZDeVmg+p9yIPJjuq73/lRS3 0/McgNoFOBhKK/S6STQuFyjr9OyJyYd1shoM3hmy+kg0HYm6OgQBJNg92WV9jwGe GzlipvEp2jpLwVsTxYir2oOPhfd9D1fC9F/l/3gXbfjd5GIIVrZFq2haZmoVeJ33 LJxo3RA5Tf9LoUeels1b4s9kFz6h7+AHERUpABEBAAG0IUNocmlzdGlhbiBCdWh0 eiA8YnVodHpAcG9zdGVvLmRlPokBPgQTAQIAKAUCVAiW4AIbAwUJAeEzgAYLCQgH AwIGFQgCCQoLBBYCAwECHgECF4AACgkQZLsXsAdRqOxNUAf/V/hDA5zGDpySuCEj DhjiVRK74J9Wd8gfH0WAf1Co5HZ24wZH8rgOIVIgXw8rWkOw/VA6xfdfT+64xjTY Fhkpbrk199nDzp72F7Jc4NC+x8xac2e3rK5ifSWhZx7L5A32pGYE+d16m3EEqImK D4gcZl38x9zdUnD4hHyXkIPz1uCfuMuGgWEnaUk4Wbj41CBZr3O0ABue6regV15U jaes8r+B8iCcY+0yP2kse+3iaCaMqNv5FgQZ9+b2Cql8pFkZJVtBVUw4GW3DWZJi du0O/YrC9TgS+xY9ht/MD2qSHwjcK1sdImjqBO7xP8TIOwKeYyDvGKnSO3EJ/sSA UPGEPrkBDQRUCJbgAQgA0k/Qg67CCUJE2/zuxBEoK4wLJpDRJzh8CQPZpjWx8VP0 KL892jwfxymXn8KNhuy1SgCBFSeV9jg4VZNWDlUGJc2lo82ajr9PzIsrQwu4lf0B zrUWV5hWepKu/kb8uSjx58YYfx0SFz4+9akX3Wwu9TUHntzL5Gk3Q26nnsr1xEJ+ VEumvCH9AE0Tk0K7dQpJ2/JcLuO+uhrpd/lHFDYVN5NsG3P015uFOkDI6N/xNFCj v95XNR93QlfKpK3qWlFGescfG+o/7Ub6s67/i/JoNbw0XgPEHmQfXpD7IHO4cu+p +ETb11cz+1mmi96cy98ID+uTiToJ8G//yD9rmtyxoQARAQABiQElBBgBAgAPBQJU CJbgAhsMBQkB4TOAAAoJEGS7F7AHUajs6sQH/iKs6sPc0vkRJLfbwrijZeecwCWF blo/jzIQ8jPykAj9SLjV20Xwqg3XcJyko8ZU6/zuRJq9xjlv9pZr/oVudQAt6v+h 2Cf4rKEjmau483wjMV2xjTXQhZi9+ttDbia4fgdmGtKsOicn5ae2fFXcXNPu3RiW sZKifWdokA6xqMW6iIG9YjjI5ShxngHWp2xfPscBFMDRtFOMags/Yx+YvwoyEZ4A dURYMFHFqpwILEc8hIzhRg1gq40AHbOaEdczS1Rr3T7/gS6eBs4u6HuY5g2Bierm lLjpspFPjMXwJAa/XLOBjMF2vsHPrZNcouNKkumQ36yq/Pm6DFXAseQDxOk= =PGP9 -----END PGP PUBLIC KEY BLOCK----- |
From: Albert <alb...@gm...> - 2015-11-08 10:11:50
|
Dear Petr, Regarding problem A: Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem? (Preferably as bug report at bugzilla ( https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen) (It looks like that I can reproduce the problems B and C) Albert On Tue, Oct 13, 2015 at 3:13 PM, Petr Parik <pet...@se...> wrote: > Hi all, > > It seems Doxygen 1.8.10 does not work properly on Fortran modules. > > A. If a module is not documented it is not listed on the "file > reference" page (as expected) but all its functions/variables are (bug!). > > B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as > expected) but module private variables are (bug!). > > C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as > expected but are not "appended" to function/variable documentation. This > is only a nuisance. > > D. If a documented function (inside or outside a module) is followed by > one or more undocumented functions, the function calls in the following > undocumented functions are listed in "References" of the documented > function (bug!). > > Could this issues be adressed in the next version? Thanks :) > > Best regards, > > Petr > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Albert <alb...@gm...> - 2015-11-08 09:41:32
|
Dear Petr, I looked at problem D, but was not able to reproduce it. I used the attached source file and the default Doxyfile with the following items set to YES: - EXTRACT_ALL - REFERENCED_BY_RELATION - REFERENCES_RELATION Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem? (Preferably as bug report at bugzilla (https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen) Albert On Tue, Oct 13, 2015 at 3:13 PM, Petr Parik <pet...@se...> wrote: > Hi all, > > It seems Doxygen 1.8.10 does not work properly on Fortran modules. > > A. If a module is not documented it is not listed on the "file > reference" page (as expected) but all its functions/variables are (bug!). > > B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as > expected) but module private variables are (bug!). > > C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as > expected but are not "appended" to function/variable documentation. This > is only a nuisance. > > D. If a documented function (inside or outside a module) is followed by > one or more undocumented functions, the function calls in the following > undocumented functions are listed in "References" of the documented > function (bug!). > > Could this issues be adressed in the next version? Thanks :) > > Best regards, > > Petr > > > ------------------------------------------------------------------------------ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Jayty <ja...@su...> - 2015-11-04 19:35:58
|
Ah I read this and actually misunderstood the documentation. Thanks for the clarification, I'll get on that now. - Jay -- View this message in context: http://doxygen.10944.n7.nabble.com/Classes-being-missed-due-to-having-symbol-in-document-tp7446p7448.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Peter B. <pd...@ma...> - 2015-11-04 19:30:27
|
Use the PREDEFINED configuration option: http://www.doxygen.nl/manual/config.html#cfg_predefined In your case, PREDEFINED = IsServer IsClient Peter > On Nov 4, 2015, at 10:37 AM, Jayty <ja...@su...> wrote: > > Apologies if this has already been asked, or if I'm asking a silly question > although I'm new to doxygen and must be missing something :) > > So the issue I'm having is this. I'm using doxygen to produce documentation > for my Unity3D project, everything works well until I make use of unity's > code separation setup which involves using a tags throughout my documents to > separate server and client code. > > For example - > > #if IsServer > server classes here, > #end if > > #if IsClient > Client stuff here > #endif > > The issue I'm having is that as soon as doxygen hits a #, it seems to avoid > the document in its entirety :/ I can't get around having to use the symbols > either since separating the server/client code into their own scripts is a > pain. > > I'm sure I'm just missing the process to stop doxy having this behaviour, > any insight would be greatly appreciated. > > Jay > > > > -- > View this message in context: http://doxygen.10944.n7.nabble.com/Classes-being-missed-due-to-having-symbol-in-document-tp7446.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 ____________ Peter Barnes pd...@ma... |