doxygen-develop Mailing List for Doxygen (Page 19)
Brought to you by:
dimitri
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(4) |
Jul
(29) |
Aug
(8) |
Sep
(8) |
Oct
(17) |
Nov
(34) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(20) |
Feb
(14) |
Mar
(11) |
Apr
(9) |
May
(8) |
Jun
(7) |
Jul
(25) |
Aug
(12) |
Sep
(12) |
Oct
(24) |
Nov
(27) |
Dec
(12) |
2003 |
Jan
(12) |
Feb
(14) |
Mar
(15) |
Apr
(11) |
May
(17) |
Jun
(20) |
Jul
(32) |
Aug
(13) |
Sep
(34) |
Oct
(12) |
Nov
(16) |
Dec
(33) |
2004 |
Jan
(20) |
Feb
(6) |
Mar
(20) |
Apr
(15) |
May
(16) |
Jun
(28) |
Jul
(7) |
Aug
(7) |
Sep
(17) |
Oct
(16) |
Nov
(17) |
Dec
(43) |
2005 |
Jan
(15) |
Feb
(5) |
Mar
(14) |
Apr
(4) |
May
(3) |
Jun
(8) |
Jul
(17) |
Aug
(16) |
Sep
(7) |
Oct
(17) |
Nov
(1) |
Dec
(7) |
2006 |
Jan
(7) |
Feb
(6) |
Mar
(10) |
Apr
(6) |
May
(3) |
Jun
(4) |
Jul
(3) |
Aug
(3) |
Sep
(18) |
Oct
(11) |
Nov
(10) |
Dec
(3) |
2007 |
Jan
(12) |
Feb
(12) |
Mar
(23) |
Apr
(5) |
May
(13) |
Jun
(6) |
Jul
(5) |
Aug
(4) |
Sep
(8) |
Oct
(10) |
Nov
(6) |
Dec
(7) |
2008 |
Jan
(7) |
Feb
(13) |
Mar
(35) |
Apr
(14) |
May
(13) |
Jun
(4) |
Jul
(9) |
Aug
(6) |
Sep
(12) |
Oct
(9) |
Nov
(6) |
Dec
(3) |
2009 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(15) |
May
(1) |
Jun
(2) |
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
2010 |
Jan
(4) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(5) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(11) |
Oct
(2) |
Nov
(1) |
Dec
(5) |
2011 |
Jan
(12) |
Feb
(3) |
Mar
(28) |
Apr
(4) |
May
(3) |
Jun
(4) |
Jul
(15) |
Aug
(12) |
Sep
(2) |
Oct
(3) |
Nov
(6) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(4) |
Mar
(9) |
Apr
(5) |
May
(6) |
Jun
(6) |
Jul
(3) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(9) |
Dec
(7) |
2013 |
Jan
(8) |
Feb
(14) |
Mar
(15) |
Apr
(21) |
May
(29) |
Jun
(34) |
Jul
(3) |
Aug
(7) |
Sep
(13) |
Oct
(1) |
Nov
(3) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(2) |
Jun
(4) |
Jul
(2) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(2) |
2015 |
Jan
(7) |
Feb
(4) |
Mar
(3) |
Apr
(15) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(3) |
Dec
(7) |
2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
2018 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
(7) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2021 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Grégoire S. <gre...@gm...> - 2011-01-05 09:04:45
|
Hi, I would like to help but I am not experienced in Debian packaging. However, I want to learn. Regards, Greg Dimitri van Heesch wrote: > Hi, > > See the message from Matthias below. If you are interested in helping then please let him know. > > Regards, > Dimitri > > Begin forwarded message: > >> From: Matthias Klose <do...@ub...> >> Date: January 4, 2011 21:59:07 GMT+01:00 >> To: Dimitri van Heesch <di...@st...> >> Subject: doxygen maintenance in Debian/Ubuntu >> >> Hi, >> >> do you know somebody who could be interested in co-maintaining doxygen in Debian? I realize that I'm leaving too many reports not forwarded. >> >> http://bugs.debian.org/src=doxygen >> >> I'll ask in Debian and Ubuntu too, but maybe you would know somebody. >> >> Thanks, Matthias >> > > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > -- Grégoire Scano Computer Science and Engineering Student ENSEIRB-MATMECA Bordeaux France |
From: Dimitri v. H. <di...@st...> - 2011-01-04 22:45:20
|
Hi, See the message from Matthias below. If you are interested in helping then please let him know. Regards, Dimitri Begin forwarded message: > From: Matthias Klose <do...@ub...> > Date: January 4, 2011 21:59:07 GMT+01:00 > To: Dimitri van Heesch <di...@st...> > Subject: doxygen maintenance in Debian/Ubuntu > > Hi, > > do you know somebody who could be interested in co-maintaining doxygen in Debian? I realize that I'm leaving too many reports not forwarded. > > http://bugs.debian.org/src=doxygen > > I'll ask in Debian and Ubuntu too, but maybe you would know somebody. > > Thanks, Matthias |
From: MB <Baj...@in...> - 2011-01-04 10:49:49
|
Hello All,I am using DOT graphs very often (using \dotfile). I miss functionality of copying function brief to tooltip or to label./** * Brief description to be added as label * * Detail description to be added as a tooltip */void Node1(void){}digraph G{ Node1 [label="\copybrief Node1", URL="\ref Node1" tooltip="\copydetails Node1"];}What do you think is it possible to add it?Regards,Marcin |
From: Albert <alb...@gm...> - 2011-01-03 21:18:02
|
Dear all, In the current version of Doxygen (1.7.3) there are, to the best of my knowledge, no easy facilities for underlining texts like it is possible for italic or bold. I think it would be good to have this possibility by means of the tags <u> </u>. Analogous to italic, the following would to the best of my knowledge valid for underline: For HTML the code to be generated will be the pair <u> </u> For Latex it will be \underline{ For RTF it will be \ul For the other output formats (XML, man, Perl) I don't know the values. Please comment, Albert |
From: MB <Baj...@in...> - 2010-12-23 10:42:59
|
Hello All, I am using doxygen extensivly but I miss some functionalities. Both seems to be simple to implement. 1) [not so important] Include tooltips for function parameters in Source Browser - When the function is commented the parameter should be blue and tooltip should be available. Maybe it is also reasonable to add functionality of documenting local function variables in such way (as far as I saw it is not possible now). 2) [very important] Add possibility to include function callergraph outside this function documentation. Currently there is only function \callergraph and this includes caller graph of the function where this block is placed. I suggest to add functionality to include caller graph i.e. in the @mainpage just by simple \addcallergraph NameOfFunction. Regards, Marcin ---------------------------------------------------------------------- Ile kosztuje mieszkanie w Twoim mieście? Sprawdź >> http://linkint.pl/f288a |
From: Rene Z. <r.z...@fr...> - 2010-12-22 19:30:13
|
Am Thursday 09 December 2010 20:20:27 schrieb Dimitri Van Heesch: > That is currently only needed and done for C/C++/ObjC (other languages > don't have a declaration and definition that needs to be matched). OK > > This is currently hardcoded for these languages in doxygen.cpp. > - Building a list of function/methods from Entry objects is done by > buildFunctionList(). > - Matching documentation blocks with function/methods is done by > findMemberDocumentation() > - copying documentation from declaration to definition and vise-versa is > done by transferFunctionDocumentation() > These are not the easiest and cleanest functions in doxygen I'm afraid. Thanks for the starting points. I used some code from transferFunctionDocumentation() to do the add of documentation inside my code. It is included in the new patch. Thank you rene |
From: Alexis R. <ro...@br...> - 2010-12-21 23:54:08
|
Hi all, I'd like to draw your attention to a patch I just attached to this bug report: https://bugzilla.gnome.org/show_bug.cgi?id=598481 This is my first attempt at flex/doxygen/etc, so please let me know if I missed anything obvious etc, especially if it means the patch can't be applied to the project. Note that the patch does not attempt to do anything clever with the type extension information, it just ensures doxygen doesn't choke when the EXTEND attribute is used. Hope this helps, Alexis |
From: Dimitri V. H. <do...@gm...> - 2010-12-09 19:20:38
|
Hi Rene, On Dec 9, 2010, at 8:58 , Rene Zaumseil wrote: > Hi all, > > I try to implement doxygen for a new language. I have parsed the language > and got the documentation in Entries. (entry.h) > > I have one Entry with documentation and declaration (like declaration in C++ > *.h file). The other Entry contains documentation and definition (like > definition in C++ *.cpp files). > > I can find the first Entry. But how can I bring these two together? That is currently only needed and done for C/C++/ObjC (other languages don't have a declaration and definition that needs to be matched). This is currently hardcoded for these languages in doxygen.cpp. - Building a list of function/methods from Entry objects is done by buildFunctionList(). - Matching documentation blocks with function/methods is done by findMemberDocumentation() - copying documentation from declaration to definition and vise-versa is done by transferFunctionDocumentation() These are not the easiest and cleanest functions in doxygen I'm afraid. I hope this helps, Dimitri |
From: Rene Z. <r.z...@fr...> - 2010-12-09 08:21:08
|
Hi all, I try to implement doxygen for a new language. I have parsed the language and got the documentation in Entries. (entry.h) I have one Entry with documentation and declaration (like declaration in C++ *.h file). The other Entry contains documentation and definition (like definition in C++ *.cpp files). I can find the first Entry. But how can I bring these two together? Regards rene |
From: Mark de W. <m.d...@da...> - 2010-11-08 12:42:28
|
Hi, I recently wanted to add the LaTeX output of Doxygen in the middle of a manual. So I wanted to have a Doxygen generated refman.tex that only adds the list of files needed to include the Doxygen output. With an empty LATEX_HEADER file I could skip the automatic preamble, but alas there was no LATEX_FOOTER option to avoid the generation of the final part (\makeindex\end{document}). So I wrote a small patch which adds a LATEX_FOOTER configuration option. The option allows you to use a file to generate the final part of the LaTeX file. If you deem it useful feel free to include it in Doxygen. Regards, Mark de Wever |
From: Rene Z. <r.z...@fr...> - 2010-10-29 11:36:22
|
Hi all, I have enhanced doxygen to parse/document tcl files. The patch can be found in the tracker as Bug #633448. How should I proceed to get the patch in the main branch? Regards, rene |
From: Peter M. <pm...@op...> - 2010-10-10 05:31:16
|
Hi Folks, I would like to develop a Pascal front-end for Doxygen. Can some-one please point me to the specification for the intermediate XML format? Regards Peter Miller <pm...@op...> /\/\* http://miller.emu.id.au/pmiller/ PGP public key ID: 1024D/D0EDB64D fingerprint = AD0A C5DF C426 4F03 5D53 2BDB 18D8 A4E2 D0ED B64D See http://www.keyserver.net or any PGP keyserver for public key. "Intellectual, n., a person who has found something that is more interesting than sex." -- Aldus Huxley |
From: Martin G. <mge...@gm...> - 2010-09-28 15:14:13
|
Hello, finally I found time to update the patch to newest doxygen svn. It still needs testing though. There was a conflict when I applied the patch to the newest version. I hope the resolution was correct. See also my first post to the mailing list for explanation. You should find the patch here. https://bugzilla.gnome.org/show_bug.cgi?id=630823 Regards, Martin. Am 09.09.2010 16:25, schrieb Arnold.Steve: > I only maintain the Gentoo package, but if I can grab the patch off a bug (or somewhere) then I can test it out there... > > Steve > > ________________________________________ > From: Jake Colman [co...@pp...] > Sent: Tuesday, September 07, 2010 6:26 PM > To: dox...@li... > Subject: Re: [Doxygen-develop] where? Patch for generating correct call/caller graphs and function references if conditional compilation is used > > Martin, > > Did you create a bug report and attach your patch to the report? Did > you email Dimitri and discuss the patch with him? I've submitted > patches to Doxygen and had them accepted into the code base but first I > discussed it with the "boss". > > ...Jake > > > >>>>>> "MG" == Martin Gerlach <mge...@gm...> writes: >>>>>> > MG> Hello, > > MG> I removed the patch because no one seemed to be interested. If > MG> you are interested, I can update it so it applies to the latest > MG> version and send it to the mailing list. > > MG> Regards, > MG> Martin. > > MG> Am 04.09.2010 12:36, schrieb PY: > >> Hello Martin. > >> > >> I came across to the same issue you described in your post: > >> https://sourceforge.net/mailarchive/message.php?msg_name=4B520F66.9010202%40gmx.net > >> > >> I would like to try your patch but your link doesnt seem to work. > >> > >> when this patch can be added to the next doxygen version? > >> > >> thanks! > >> > >> Py > >> > > MG> ------------------------------------------------------------------------------ > MG> This SF.net Dev2Dev email is sponsored by: > > MG> Show off your parallel programming skills. > MG> Enter the Intel(R) Threading Challenge 2010. > MG> http://p.sf.net/sfu/intel-thread-sfd > > -- > Jake Colman | Director, Software Development > Principia Partners LLC > 101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770 > t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929 > e: co...@pp... | w: www.principiapartners.com > Credit technology innovation awards winner 2008 and 2009 > > > The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited. > > The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws. > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
From: Albert <alb...@gm...> - 2010-09-26 15:25:33
|
Hi Dimitri, Thanks, this solves this issue. There are quite a few messages on the germinal and in the log file. Upon request I can send these as well (i.e. if you cannot reproduce these messages) Windows issue still exists Best regards, Albert On Sun, Sep 26, 2010 at 5:15 PM, Dimitri Van Heesch <do...@gm...> wrote: > Hi Albert, > > On Sep 26, 2010, at 16:52 , Albert_1 wrote: > >> >> Dear all, >> >> I just checked out the last version of Doxygen (1.7.1-20100920). >> Building Doxygen under cygwin (on 64-bit Vista system) does not give any >> problem. >> Building the Doxygen HTML documentation and the rtf documentation on cygwin >> (with this new version) is no problem either. >> Building the pdf documentation gives error messages: >> Chapter 28. >> (./langhowto.tex >> Underfull \vbox (badness 10000) detected at line 52 >> ./langhowto.tex:88: Missing $ inserted. >> <inserted text> >> $ >> l.88 ...rzegorz Kowal & {\tt\tiny [unreachable] g_ >> kowal at poczta dot onet >> d... >> >> >> I've attached the complete build log to this post (compressed tar). >> >> When generating the documentation directly on windows (also with this new >> doxygen version and with MikTex 2.8) I already get error message when >> generating the HTML ? RTF / latex documentation: >> Generating docs for page starting... >> epstopdf: The input file does not exist. >> error: Problems running epstopdf. Check your TeX installation! >> Generating docs for page docblocks... >> >> When generating documentation for my own code I do not have any problems >> (had to get some extra packages for MikTex) >> >> How can I solve this problem ? > > Edit doc/maintainers.txt and replace "g_kowal" by "g kowal", > then rerun make in the doc directory and then in the latex directory. > > Regards, > Dimitri > > |
From: Dimitri V. H. <do...@gm...> - 2010-09-26 15:15:20
|
Hi Albert, On Sep 26, 2010, at 16:52 , Albert_1 wrote: > > Dear all, > > I just checked out the last version of Doxygen (1.7.1-20100920). > Building Doxygen under cygwin (on 64-bit Vista system) does not give any > problem. > Building the Doxygen HTML documentation and the rtf documentation on cygwin > (with this new version) is no problem either. > Building the pdf documentation gives error messages: > Chapter 28. > (./langhowto.tex > Underfull \vbox (badness 10000) detected at line 52 > ./langhowto.tex:88: Missing $ inserted. > <inserted text> > $ > l.88 ...rzegorz Kowal & {\tt\tiny [unreachable] g_ > kowal at poczta dot onet > d... > > > I've attached the complete build log to this post (compressed tar). > > When generating the documentation directly on windows (also with this new > doxygen version and with MikTex 2.8) I already get error message when > generating the HTML ? RTF / latex documentation: > Generating docs for page starting... > epstopdf: The input file does not exist. > error: Problems running epstopdf. Check your TeX installation! > Generating docs for page docblocks... > > When generating documentation for my own code I do not have any problems > (had to get some extra packages for MikTex) > > How can I solve this problem ? Edit doc/maintainers.txt and replace "g_kowal" by "g kowal", then rerun make in the doc directory and then in the latex directory. Regards, Dimitri |
From: Albert_1 <alb...@gm...> - 2010-09-26 14:52:24
|
Dear all, I just checked out the last version of Doxygen (1.7.1-20100920). Building Doxygen under cygwin (on 64-bit Vista system) does not give any problem. Building the Doxygen HTML documentation and the rtf documentation on cygwin (with this new version) is no problem either. Building the pdf documentation gives error messages: Chapter 28. (./langhowto.tex Underfull \vbox (badness 10000) detected at line 52 ./langhowto.tex:88: Missing $ inserted. <inserted text> $ l.88 ...rzegorz Kowal & {\tt\tiny [unreachable] g_ kowal at poczta dot onet d... I've attached the complete build log to this post (compressed tar). When generating the documentation directly on windows (also with this new doxygen version and with MikTex 2.8) I already get error message when generating the HTML ? RTF / latex documentation: Generating docs for page starting... epstopdf: The input file does not exist. error: Problems running epstopdf. Check your TeX installation! Generating docs for page docblocks... When generating documentation for my own code I do not have any problems (had to get some extra packages for MikTex) How can I solve this problem ? Best Regards, Albert http://old.nabble.com/file/p29812102/latex_err.taz latex_err.taz -- View this message in context: http://old.nabble.com/Generating-latex---pdf--documentation-of-Doxygen-tp29812102p29812102.html Sent from the Doxygen - Development mailing list archive at Nabble.com. |
From: Albert_1 <alb...@gm...> - 2010-09-25 13:58:07
|
Dear all, I just filed bug 630573 in Bugzilla (see message below), as promised there I would also cross post to the doxygen-develop list because I'm not happy with my solution. In my solution I have to bring a language specific part into the docparser.cpp, I'd rather change the fortranscanner.l so a subroutine would be handled as a void function, I've not been able to do this yet. When I change in, in the subroutine addSubprogram, the value of current>-type to void (in case of a subroutine) I also get the word void in the documentation and this is not what I want. I see that there are 2 variables "type" and "mtype" both having for function and subroutines the same value (so both have eg. the value "subroutine" or when changed as described above the word "void"). The problem in my case is that I don't have enough (better said hardly any / no) experience with the fortranscanner. - How can I accomplish, in the FORTRAN scanner, that a subroutine is seen as a void function, without disrupting the output ? - what is the difference between type and mtype? In advance, Thanks for the answers, Best Regards, Albert =============== Buzilla 630573 entry ===================== When I generate the generate the documentation for the following code: !> \file !> Subroutine ftn_test_fie !> @param [in] x input param SUBROUTINE ftn_test_fie(x) integer x END SUBROUTINE and I have the option WARN_NO_PARAMDOC set to YES (Doxyfile attached)I get the warning message: D:/bug_undoc/bb.f90:5: warning: return type of member ftn_test_fie is not documented For a Fortan subroutine there is no return type. I have a solution for it, but I'm not happy with it, around line 539 in docparser.cpp: else if ( // see if return needs to documented g_memberDef->hasDocumentedReturnType() || returnType.isEmpty() || // empty return type returnType.find("void")!=-1 || // void return type g_memberDef->isConstructor() || // a constructor g_memberDef->isDestructor() // or destructor ) replace by: else if ( // see if return needs to documented g_memberDef->hasDocumentedReturnType() || returnType.isEmpty() || // empty return type returnType.find("void")!=-1 || // void return type returnType.find("subroutine")!=-1 || // Fortran Subroutine g_memberDef->isConstructor() || // a constructor g_memberDef->isDestructor() // or destructor ) -- View this message in context: http://old.nabble.com/Fortran%3A-Subroutine-seen-as-function-tp29806242p29806242.html Sent from the Doxygen - Development mailing list archive at Nabble.com. |
From: anirudh s. s. <she...@gm...> - 2010-09-13 10:56:22
|
Hi, I'm interested in adding sql language support in doxygen. would like to get a head start and information in doing so, mainly because its been stated as difficulty level 10 in the to-do list of doxygen. why is it so difficult. secondly, I tried to use hyper-sql, a documentation generator for sql on windows, but it didn't work, i mean it generated the html pages etc but nothing related to the documentation of the code. regards Acedip -- My web home http://acedip.in Linux Users Group Jaipur http://lugj.in -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/FA/L/MU/P/S !d s:- a-- C UL P++ L+++ E- W++ N++ o K-- w--- O- M- V PS PE Y PGP t 5 X R tv b DI D G e h+ r- y++ ------END GEEK CODE BLOCK------ |
From: Arnold.Steve <arn...@en...> - 2010-09-09 14:47:46
|
I only maintain the Gentoo package, but if I can grab the patch off a bug (or somewhere) then I can test it out there... Steve ________________________________________ From: Jake Colman [co...@pp...] Sent: Tuesday, September 07, 2010 6:26 PM To: dox...@li... Subject: Re: [Doxygen-develop] where? Patch for generating correct call/caller graphs and function references if conditional compilation is used Martin, Did you create a bug report and attach your patch to the report? Did you email Dimitri and discuss the patch with him? I've submitted patches to Doxygen and had them accepted into the code base but first I discussed it with the "boss". ...Jake >>>>> "MG" == Martin Gerlach <mge...@gm...> writes: MG> Hello, MG> I removed the patch because no one seemed to be interested. If MG> you are interested, I can update it so it applies to the latest MG> version and send it to the mailing list. MG> Regards, MG> Martin. MG> Am 04.09.2010 12:36, schrieb PY: >> Hello Martin. >> >> I came across to the same issue you described in your post: >> https://sourceforge.net/mailarchive/message.php?msg_name=4B520F66.9010202%40gmx.net >> >> I would like to try your patch but your link doesnt seem to work. >> >> when this patch can be added to the next doxygen version? >> >> thanks! >> >> Py >> MG> ------------------------------------------------------------------------------ MG> This SF.net Dev2Dev email is sponsored by: MG> Show off your parallel programming skills. MG> Enter the Intel(R) Threading Challenge 2010. MG> http://p.sf.net/sfu/intel-thread-sfd -- Jake Colman | Director, Software Development Principia Partners LLC 101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770 t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929 e: co...@pp... | w: www.principiapartners.com Credit technology innovation awards winner 2008 and 2009 The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited. The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws. |
From: Jake C. <co...@pp...> - 2010-09-08 01:27:20
|
Martin, Did you create a bug report and attach your patch to the report? Did you email Dimitri and discuss the patch with him? I've submitted patches to Doxygen and had them accepted into the code base but first I discussed it with the "boss". ...Jake >>>>> "MG" == Martin Gerlach <mge...@gm...> writes: MG> Hello, MG> I removed the patch because no one seemed to be interested. If MG> you are interested, I can update it so it applies to the latest MG> version and send it to the mailing list. MG> Regards, MG> Martin. MG> Am 04.09.2010 12:36, schrieb PY: >> Hello Martin. >> >> I came across to the same issue you described in your post: >> https://sourceforge.net/mailarchive/message.php?msg_name=4B520F66.9010202%40gmx.net >> >> I would like to try your patch but your link doesnt seem to work. >> >> when this patch can be added to the next doxygen version? >> >> thanks! >> >> Py >> MG> ------------------------------------------------------------------------------ MG> This SF.net Dev2Dev email is sponsored by: MG> Show off your parallel programming skills. MG> Enter the Intel(R) Threading Challenge 2010. MG> http://p.sf.net/sfu/intel-thread-sfd -- Jake Colman | Director, Software Development Principia Partners LLC 101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770 t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929 e: co...@pp... | w: www.principiapartners.com Credit technology innovation awards winner 2008 and 2009 |
From: Martin G. <mge...@gm...> - 2010-09-08 00:43:30
|
Hello, I removed the patch because no one seemed to be interested. If you are interested, I can update it so it applies to the latest version and send it to the mailing list. Regards, Martin. Am 04.09.2010 12:36, schrieb PY: > Hello Martin. > > I came across to the same issue you described in your post: > https://sourceforge.net/mailarchive/message.php?msg_name=4B520F66.9010202%40gmx.net > > I would like to try your patch but your link doesnt seem to work. > > when this patch can be added to the next doxygen version? > > thanks! > > Py > |
From: PY <ek...@gm...> - 2010-09-04 10:36:16
|
Hello Martin. I came across to the same issue you described in your post: https://sourceforge.net/mailarchive/message.php?msg_name=4B520F66.9010202%40gmx.net I would like to try your patch but your link doesnt seem to work. when this patch can be added to the next doxygen version? thanks! Py |
From: Jason R. <ja...@dr...> - 2010-09-02 18:02:25
|
I have reached a point in my API documentation where the ability to organize examples would be extremely useful. For example my current example list is: http://libnds.devkitPro.org/examples.html The ability to specify a link name, group the examples by category, and specify a short "about" would greatly improve presentation and navigability of our example code...any thoughts? Thanks for your time and an invaluable product. Jason Sent from my iPhone |
From: Anders W. K. <awk...@gm...> - 2010-08-29 11:51:38
|
Hi, are there any plans to include MathJax support in doxygen's html output? MathJax would seem to be a perfect match for doxygen (see http://www.mathjax.org), as it has a number of advantages compared to the current solution for embedding fomulas in html: 1) User does not need LaTeX installation 2) Generating PNGs with LaTeX is fairly time consuming 3) PNG's have fixed resolution (I often zoom in the browser, which makes PNGs blurry) On the other hand with MathJax: 1) Formulas are generated with a client-side script directly in the browser 2) Resolution independence for better scaling 3) Other advantages (e.g. try right clicking a MathJax formula on their site) Kind regards Anders |
From: Davide C. <dc...@ar...> - 2010-08-17 11:31:02
|
Dear doxygen developers, I have a simple suggestion for improvement in fortranscanner.l: === cut here === --- ./src/fortranscanner.l~ 2010-03-14 16:26:58.000000000 +0100 +++ ./src/fortranscanner.l 2010-08-17 12:17:27.000000000 +0200 @@ -1089,6 +1089,8 @@ dest->bodyLine = src->bodyLine; dest->args = src->args; dest->argList = new ArgumentList(*src->argList); + dest->doc = src->doc; + dest->brief = src->brief; } /** fill empty interface module procedures with info from === cut here === this ensures that, in case of MODULE PROCEDUREs belonging to an INTERFACE, the procedure documentation which is reached navigating from the interface link is as complete as the stand-alone documentation of the procedure itself, while now the first one does not contain the brief and long documentation text; I do not know whether it is so by design or because it was overlooked, I will give a longer explanation of why this modification is desirable IMHO. If you think this is reasonable and error-free, it would be nice to have it updated in svn. Longer and boring Fortran explanation: if a programmer defines a generic interface to one or mode module procedures, it means that they would like people to use the generic interfaced name, not the specific name, so the biggest emphasis should be given to the documentation that appears through the interface, not to the documentation that is reached by directly clicking on the stand-alone function/subroutine link. Even more, I think that, at least under the control of a configuration switch, the documented module procedures which are member of an interface should be removed from the function list, this would remove duplications and make the documentation clearer and lighter. I Cc the doxygen-users list too -sorry for double posting- since someone there may comment for or against this proposal. Best regards, Davide -- ============================= Davide Cesari ============================ Servizio IdroMeteorologico ARPA Emilia Romagna Area Modellistica Numerica e Radarmeteorologia E-mail: dc...@ar... Home page: http://www.webalice.it/o.drofa/davide/ ======================================================================== This message has been scanned for malware by Websense. www.websense.com |