Marcin Komorowski | 17 Apr 15:08 2014
Picon

Doxygen development/debug IDE under OSX

Hi All,

Does anyone on this list do any development/debugging of Doxygen under OSX?

Do you have any suggestion for best IDE to use under OSX for this work?

If you have one, would you be willing to share your IDE project setup file for Doxygen?

Thank You,
Marcin Komorowski

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
Markus Geimer | 12 Apr 18:49 2014
Picon

Double dash within <tt> or <code> is again (or still?) broken

Hi,

This issue has already been reported ten years ago in bugreport
https://bugzilla.gnome.org/show_bug.cgi?id=133418 and was marked
as resolved, however, I see this issue again/still with current
sources from git (just sync'ed my local copy).

Simply try something like
	<tt>--prefix</tt>
or
	<code>--prefix</code>
and you will get '&ndash;' in the HTML output and '--' in LaTeX
(should be '-\/-' to prevent getting the en-dash). Same applies
to the em-dash, though I assume that this is used less often in
<tt>/<code> environments.

On the other hand, the LaTeX output contains an unnecessary italic
correction for dashes between words. For example, 'so-called' is
typeset as 'so-\/called'.

Unfortunately, I couldn't yet figure out where things go wrong.
The output of '-d commentscan' already reports '--' or '&ndash;'
depending on the MARKDOWN_SUPPORT setting, however, the final
output is identical in both cases. Some hint where to start would
be very welcome.

Thanks,
Markus

------------------------------------------------------------------------------
(Continue reading)

Markus Geimer | 9 Apr 19:34 2014
Picon

[PATCH] Fix broken links to subpages in LaTeX output

Hi,

The attached patch fixes a bug in generating references to subpages (and
potentially also other items) in the LaTeX output when PDF_HYPERLINKS is
set to NO. I also included a minimal example.

Cheers,
Markus
Attachment (example.tgz): application/x-gtar-compressed, 166 bytes
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Phil Mason | 9 Apr 16:07 2014

Some meta tags are not properly closed.

Hi,

 

When I run doxygen built from git head on some of my source the resulting html has meta tags that are not properly closed (and fail to pass the w3c validator as a result). The following is a sample of the html output (from html/search/all_0.html):

 

<html><head><title></title>

<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>

<meta name="generator" content="Doxygen 1.8.6">

 

Note that the second meta tag is not properly closed (and as the doctype of this file is XHTML it needs to be).

 

This trivial patch resolves this issue:

 

diff --git a/src/searchindex.cpp b/src/searchindex.cpp

index 7aa8216..a550eb1 100644

--- a/src/searchindex.cpp

+++ b/src/searchindex.cpp

<at> <at> -1027,7 +1027,7 <at> <at> void writeJavascriptSearchIndex()

             " \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">" << endl;

           t << "<html><head><title></title>" << endl;

           t << "<meta http-equiv=\"Content-Type\" content=\"text/xhtml;charset=UTF-8\"/>" << endl;

-          t << "<meta name=\"generator\" content=\"Doxygen " << versionString << "\">" << endl;

+          t << "<meta name=\"generator\" content=\"Doxygen " << versionString << "\"/>" << endl;

           t << "<link rel=\"stylesheet\" type=\"text/css\" href=\"search.css\"/>" << endl;

           t << "<script type=\"text/javascript\" src=\"" << baseName << ".js\"></script>" << endl;

           t << "<script type=\"text/javascript\" src=\"search.js\"></script>" << endl;

 

Hope this is useful

 

Regards

 

Phil

 

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Ross Rogers | 19 Dec 20:38 2013
Picon

Re 3321410 - was ditaa ever integrated?

Hello,

Regarding the ancient thread http://sourceforge.net/mailarchive/message.php?msg_id=3321410 , was ditaa ever integrated into doxygen or is there a generalized mechanism for doing external text->image processing?

 - Ross
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
mkk | 18 Dec 20:50 2013
Picon
Picon

Re: Doxygen VHDL

 see http://plantuml.sourceforge.net/doxygen.html

--
View this message in context: http://doxygen.10944.n7.nabble.com/Doxygen-VHDL-tp6240p6409.html
Sent from the Doxygen - Development mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
David Binderman | 17 Dec 20:20 2013
Picon

doxygen-1.8.5:doxygen.cpp:3572: possible bad if test ?

Hello there,

I just ran the static analyser "cppcheck" over the source
code of doxygen-1.8.5. It said many things, including

[doxygen.cpp:3572]: (warning) Logical conjunction always evaluates to false: EXPR != -1 && EXPR == -1.

Source code is

if (md->getStartBodyLine()!=-1 && md->getStartBodyLine()==-1)

Suggest code rework.

The analyser also said

[fortranscanner.cpp:1307]: (style) Array index 'i' is used before limits check.
[markdown.cpp:541]: (style) Array index 'i' is used before limits check.
[markdown.cpp:1317]: (style) Array index 'i' is used before limits check.
[markdown.cpp:1323]: (style) Array index 'i' is used before limits check.

which may also be worth fixing.

Regards

David Binderman 		 	   		  
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
Szabolcs Palmer | 11 Dec 02:44 2013

Broken link in Doxy documentation

Hello Everyone,

Just wanted to give a heads up that on page http://www.stack.nl/~dimitri/doxygen/helpers.html at the end of section JavaScript, the link to Xie Wenjie's approach is broken.

Cheers,
Szasza
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Tom Ghyselinck | 4 Nov 11:33 2013

Re: Patch for linking to TCL class members with 'dot' in their name

Hi all,

I filed this as BUG 711387 ( https://bugzilla.gnome.org/show_bug.cgi?id=711387 )

With best regards,
Tom.

On ma, 2013-11-04 at 10:15 +0100, Tom Ghyselinck wrote:
Hi all,

There is a bug in doxygen-1.8.5 with TCL classes with a dot in their name.

When we want to use \link to these members, the resolution of the name
fails.

This is due to the fact that the any dot in a name is subsituted by '::' as
if it was a scope separator.
This is very suitable and convenient for C++ / Java / etc., where a dot
in function names and class members is not allowed,
but TCL does allow a dot in function names.

I wrote a (quick and (maybe not so) dirty) patch for doxygen-1.8.5.

The function resolveRef in util.h/util.c now has an additional
argument dotIsScopeSeparator. When this is set to FALSE,
a 'dot' in the reference name won't be translated to '::'.

For compatibility, it defaults to TRUE.
The Q&D part now exists in the fact that, the rest of the code
still uses the compatible call. The function itself tries to resolve
with dotIsScopeSeparator = FALSE when resolving with
dotIsScopeSeparator = TRUE fails.

I added a simple test project with several links as suggested by
http://www.stack.nl/~dimitri/doxygen/manual/autolink.html

With best regards,
Tom.



--

| tom.ghyselinck <at> excentis.com
|
| Tom Ghyselinck
| Senior Engineer
| Excentis N.V.
| Gildestraat 8 B-9000 Ghent, Belgium
| Tel: +32 9 269 22 91 - Fax: +32 9 329 31 74
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Tom Ghyselinck | 4 Nov 09:03 2013

Patch for disabling source link in classes and class members

Hi all,

We have a special use case of doxygen:

1. We have TCL classes which are implemented in C++.
To generate the documentation, we create a "dummy" (TCL) source file (api.tcl)
which just defines the class and the methods (with their arguments)
without implementation.

During documentation generation, the source code in the file is filtered out
Doxyfile:
FILTER_SOURCE_FILES = YES FILTER_SOURCE_PATTERNS = *api.tcl="api_source_filter.sh"
with api_source_filter.sh being an empty file.

This source code is not desired in our doxygen files listing output,
nor do we want any link to the "filtered-out" source code.


This would work great if we have SOURCE_BROWSER = NO in our Doxyfile, but:

2. We also provide documentation for wrapper scripts for our TCL API.
This part includes (open-source) scripts and tools to ease the use of our API (described in 1.).
This documentation is listed in the Files section of doxygen. So we explicitly need
SOURCE_BROWSER = YES in order to make this work.


Another option is to split up the documentation it 2 parts, but:

3. There are some restrictions to do this:
* The API and TCL wrapper scripts refer to each other
* We also have example pages which refer to the API and wrapper and vice versa.
So the documentation MUST be in one Doxygen project.


To remove the linking to the source file in classes and class members,
we created a patch for doxygen 1.8.5 release (see attachment).
It can be controlled by the SOURCE_DEFINITION configuration item.
Linking to the source is still enabled by default.

Note that our patch does not remove the links to source code
for documentation in the Files section!

Any comments or other suggestions for our change are very welcome!

If there are any other suggestions for our flexible documentation,
please let us know!

With best regards,
Tom.

--

| tom.ghyselinck <at> excentis.com
|
| Tom Ghyselinck
| Senior Engineer
| Excentis N.V.
| Gildestraat 8 B-9000 Ghent, Belgium
| Tel: +32 9 269 22 91 - Fax: +32 9 329 31 74
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Markus Geimer | 2 Oct 12:50 2013
Picon

[PATCH] Improved ALIASES definitions

Hi,

please find two patches attached regarding the definition of ALIASES.
The first one simply fixes a typo in an error message. The second
patch implements escaping of commands using the \-syntax in the value
part of ALIASES.

Rationale:
So far, there was no way to disambiguate a forced newline (via '\n')
from a command using the \-syntax starting with 'n'. While special
handling was implemented for some internal commands, self-defined
commands or LaTeX commands inside a \latexonly environment were not
recognized. For example, it was impossible to properly define a
command inserting a newline followed by a page break only for the
LaTeX output, as the '\newpage' in

	newpage="\latexonly\n\newpage\endlatexonly"

was recognized as '\n' followed by the text 'ewpage'.

Proposed solution:
The attached patch implements C-style escaping for the value part of
ALIASES. That is, '\n' inserts a newline, '\"' a quote character,
'\\' a backslash, and '\<num>' expands the corresponding argment.
The aforementioned command can therefore now be defined as either

	newpage="\\latexonly\n\\newpage\\endlatexonly"
or
	newpage" <at> latexonly\n\\newpage <at> endlatexonly"

While this solution is admittedly not backwards-compatible, it is
IMO preferable over only escaping '\n's as it provides a consistent
escaping scheme that is easy to remember.

Cheers,
Markus
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop