doxygen-develop — List for discussing new features, submitting patches, etc.

Re: [Doxygen-develop] Subdirectory = module

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

On Wed, Sep 24, 2003 at 12:35:00PM -0700, Robin Rowe wrote:
> Hi. I asked this question on doxygen-users a few days ago, but got no
> response. Maybe it is a developer question?

Not really, but anyway...

> I am setting up doxygen to document my build of GTK 1.4. This is my
> first time setting up a large project with doxygen. Doxygen works, but the
> results are messy.
> 
> 1. The 'modules' sections output makes no sense. It gives 'printf' as one of
> my modules! In GTK, like most projects, the modules are contained in
> subdirectories. How do I get doxygen to recognize this? I want doxygen to
> copy my directory layout, mimic that under doxygen/html with an index.html
> in each subdirectory.

GTK 1.4 was probably not documented using doxygen commands. So no wonder that
the results may be unexpected. Doxygen does not yet have an option to 
turn directories automatically into modules, but this is on the todo list.

> 2. Doxygen didn't output much on the first pass so I turned on EXTRACT_ALL.
> Now I have too much -- 81MB! Is there a middle ground?

Splitting the project into smaller chunks might be a solution.

Regards,
  Dimitri

[Doxygen-develop] Subdirectory = module

[Robin R. <ro...@Mo...>]

Hi. I asked this question on doxygen-users a few days ago, but got no
response. Maybe it is a developer question?

I am setting up doxygen to document my build of GTK 1.4. This is my
first time setting up a large project with doxygen. Doxygen works, but the
results are messy.

1. The 'modules' sections output makes no sense. It gives 'printf' as one of
my modules! In GTK, like most projects, the modules are contained in
subdirectories. How do I get doxygen to recognize this? I want doxygen to
copy my directory layout, mimic that under doxygen/html with an index.html
in each subdirectory.

2. Doxygen didn't output much on the first pass so I turned on EXTRACT_ALL.
Now I have too much -- 81MB! Is there a middle ground?

Thanks!

Robin
---------------------------------------------------------------------------
Rob...@Mo...   Hollywood, California
www.CinePaint.org   Free motion picture and still image editing software

[Doxygen-develop] Russian translation update

[<ca...@cr...>]

	One auxiliary function move from public to private.
      Thanks for Petr Prikryl.
=09

> -----Original Message-----
> From: Petr Prikryl [mailto:Pr...@sk...]
> Sent: Wednesday, September 24, 2003 10:40 AM
> To: Doxygen developers
> Cc: Doxygen users
> Subject: [Doxygen-users] Info on the status of the language=20
> translators
> (September 24, 2003).
>=20
>=20
> Info on the status of the language translators (September 24, 2003).
>=20
> Related to the doxygen 1.3.4. Posted to doxygen-develop,
> copied to doxygen-users. The previous report was dated
> September 16, 2003.
>=20
> ATTENTION: Full translator_report.txt together with this
> text is NOT sent to the mailing list. It is now available at
> http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
> as tr2003MMDD.zip where MMDD is replaced by the month and day.
>=20
>=20
> Summary:=20
>  - Doxygen 1.3.4 was released.
>  - The Swedish language has the new maintainer.
>  - Total 29, 9 up-to-date, 6 almost up-to-date, 10 slightly=20
>    obsolete, 2 obsolete, 1 not maintained, 1 different.=20
>  - Searching for the Finnish maintainer.
>=20
> ------------------------------------------------------------
>=20
> Hi,
>=20
> Firstly, thanks to all active language maintainers. Now...
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> New maintainer for the Swedish language
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> There is the new maintainer for the Swedish language.
> Mikael Hallin, welcome on the board!
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Current status
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> The total is 29 languages now. The new one is not really
> new. It is the JapaneseEn which slightly modifies the
> English one. Because it is derived from TranslatorEnglish,
> it is reported as really obsolete, which is not true. The
> newer translator.py script will be modified not to report
> such translators this way.
>=20
> Nine of the languages are up-to-date: Brazilian, Croatian,
> Czech, Dutch, English, French, German, Italian, and Russian.
> Congratulations! (... also to myself ;)
>=20
> Six of the languages are very close to the up-to-date
> status. They reflect at least some changes since Doxygen 1.3
> release: Chinese Traditional, Japanese, Portuguese, Serbian,
> Spanish, and Swedish (ordered by alphabet and by status).
> Good job!
>=20
> Ten of the languages are slightly obsolete, but they still
> require impementing not more than 18 methods: Danish,
> Korean, Polish, Slovak, Catalan, Romanian, Slovene, Chinese,
> Greek, and Ukrainian. (ordered by alphabet and by status).
>=20
> Two of the languages -- Hungarian and Norwegian -- must
> implement about 45 methods to become up-to-date. Please, try
> harder. Or should we search for not-so-tired, new
> maintainers? Keep in mind that the translator adapters, used
> for your translator classes, make Doxygen slightly bigger
> and more complex. After updating your languages, the
> adapters can be removed.
>=20
>   -----------------------------------------------
>   We still have not found new Finnish maintainer. =20
>   The translator became extremely obsolete, and=20
>   it seems that the original maintainer is not
>   in touch with doxygen anymore.
>   -----------------------------------------------
>=20
> Reminder: look at the attached translator report. If you
> think that your language should be listed as up-to-date, but
> it is not, you probably forgot to change the base class of
> your translator class to "Translator". Then, you can run the
> doc/translator.pl script to generate the translator report
> and check the status of your translator report and see what
> has to be done to make it up-to-date.
>=20
> Note: The translator.pl is the original script that will be
> replaced by translator.py one day. You can also give it a
> try. In fact, it is almost one-to-one rewrite of the perl
> version, so do not be disappointed if you like Python. It is
> planned to be rewritten using the OO approach.
>  =20
> With regards,
>   Petr
>=20
> =20
> --=20
> Petr Prikryl, (prikrylp at skil dot cz)
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

[Doxygen-develop] Info on the status of the language translators (September 24, 2003).

[Petr P. <Pr...@sk...>]

Info on the status of the language translators (September 24, 2003).

Related to the doxygen 1.3.4. Posted to doxygen-develop,
copied to doxygen-users. The previous report was dated
September 16, 2003.

ATTENTION: Full translator_report.txt together with this
text is NOT sent to the mailing list. It is now available at
http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
as tr2003MMDD.zip where MMDD is replaced by the month and day.


Summary:=20
 - Doxygen 1.3.4 was released.
 - The Swedish language has the new maintainer.
 - Total 29, 9 up-to-date, 6 almost up-to-date, 10 slightly=20
   obsolete, 2 obsolete, 1 not maintained, 1 different.=20
 - Searching for the Finnish maintainer.

------------------------------------------------------------

Hi,

Firstly, thanks to all active language maintainers. Now...

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
New maintainer for the Swedish language
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

There is the new maintainer for the Swedish language.
Mikael Hallin, welcome on the board!

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Current status
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The total is 29 languages now. The new one is not really
new. It is the JapaneseEn which slightly modifies the
English one. Because it is derived from TranslatorEnglish,
it is reported as really obsolete, which is not true. The
newer translator.py script will be modified not to report
such translators this way.

Nine of the languages are up-to-date: Brazilian, Croatian,
Czech, Dutch, English, French, German, Italian, and Russian.
Congratulations! (... also to myself ;)

Six of the languages are very close to the up-to-date
status. They reflect at least some changes since Doxygen 1.3
release: Chinese Traditional, Japanese, Portuguese, Serbian,
Spanish, and Swedish (ordered by alphabet and by status).
Good job!

Ten of the languages are slightly obsolete, but they still
require impementing not more than 18 methods: Danish,
Korean, Polish, Slovak, Catalan, Romanian, Slovene, Chinese,
Greek, and Ukrainian. (ordered by alphabet and by status).

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

  -----------------------------------------------
  We still have not found new Finnish maintainer. =20
  The translator became extremely obsolete, and=20
  it seems that the original maintainer is not
  in touch with doxygen anymore.
  -----------------------------------------------

Reminder: look at the attached translator report. If you
think that your language should be listed as up-to-date, but
it is not, you probably forgot to change the base class of
your translator class to "Translator". Then, you can run the
doc/translator.pl script to generate the translator report
and check the status of your translator report and see what
has to be done to make it up-to-date.

Note: The translator.pl is the original script that will be
replaced by translator.py one day. You can also give it a
try. In fact, it is almost one-to-one rewrite of the perl
version, so do not be disappointed if you like Python. It is
planned to be rewritten using the OO approach.
 =20
With regards,
  Petr

=20
--=20
Petr Prikryl, (prikrylp at skil dot cz)

[Doxygen-develop] Suggested patch to optionally suppress XML program listing.

[<Pau...@Sy...>]

Currently Doxygen emits a program listing in XML. This can add hugely to 
the XML file size and slows both the Doxygen XML generation and any 
subsequent XML processing. My suggestion is to make the XML program 
listing an optional config item "XML_PROGRAMLISTING". The change affects 
two files; config.cpp and xmlgen.cpp. Here are the diffs for Doxygen 
version 1.3.4

First config.cpp:

$ diff -u original/config.cpp patched/config.cpp
--- original/config.cpp 2003-09-21 20:42:50.000000000 +0100
+++ patched/config.cpp  2003-09-23 17:23:38.000000000 +0100
@@ -4012,6 +4012,13 @@
                    "syntax of the XML files. \n"
                  );
   cs->addDependency("GENERATE_XML");
+  cb = addBool(
+                    "XML_PROGRAMLISTING",
+                    "If the XML_PROGRAMLISTING tag is set to YES Doxygen 
will \n"
+                    "generate a <programlisting>...</programlisting in 
the XML output. \n",
+                   FALSE
+                 );
+  cb->addDependency("GENERATE_XML");
 
//--------------------------------------------------------------------------
   addInfo(  "DEF","configuration options for the AutoGen Definitions 
output");
 
//--------------------------------------------------------------------------

And the diff for xmlgen.cpp:

$ diff -u original/xmlgen.cpp patched/xmlgen.cpp
--- original/xmlgen.cpp 2003-09-20 14:09:24.000000000 +0100
+++ patched/xmlgen.cpp  2003-09-23 17:25:52.000000000 +0100
@@ -1249,9 +1249,11 @@
   t << "    <detaileddescription>" << endl;
 writeXMLDocBlock(t,fd->docFile(),fd->docLine(),fd,0,fd->documentation());
   t << "    </detaileddescription>" << endl;
-  t << "    <programlisting>" << endl;
-  writeXMLCodeBlock(t,fd);
-  t << "    </programlisting>" << endl;
+  if (Config_getBool("XML_PROGRAMLISTING")) {
+    t << "    <programlisting>" << endl;
+       writeXMLCodeBlock(t,fd);
+    t << "    </programlisting>" << endl;
+  }
   t << "    <location file=\"" << fd->getDefFileName() << "\"/>" << endl;
   t << "  </compounddef>" << endl;
   t << "</doxygen>" << endl;

Best regards,

Paul Ross


**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************

[Doxygen-develop] Patch: Giving nested classes, structs unions an access attribute.

[<Pau...@Sy...>]

NOTE: This was previously reported on bugzilla as bug 120464.

Given this pseudo code:
class AB
{
public:
    class ABE{};
protected:
    class ABD{};
private:
    class ABC {};
};

Doxygen XML does not assign a prot="..." attribute for the member classes 
(it also does not emit the access attribute in HTML as well).
The patch for XML for version 1.3.4 is in xmlgen.cpp, function 
generateXMLForClass().

The diff for xmlgen.cpp, version 1.3.4 is:

$ diff -u original/xmlgen.cpp patched/xmlgen.cpp
--- original/xmlgen.cpp 2003-09-20 14:09:24.000000000 +0100
+++ patched/xmlgen.cpp  2003-09-23 16:51:56.000000000 +0100
@@ -876,7 +876,17 @@
   writeXMLHeader(t);
   t << "  <compounddef id=\""
     << cd->getOutputFileBase() << "\" kind=\""
-    << cd->compoundTypeString() << "\">" << endl;
+    << cd->compoundTypeString() << "\"";
+  Protection prot = cd->protection();
+  t << " prot=\"";
+  switch (prot)
+  {
+    case Public:    t << "public";    break;
+    case Protected: t << "protected"; break;
+    case Private:   t << "private";   break;
+    case Package:   t << "package";   break;
+  }
+  t << "\">" << endl;
   t << "    <compoundname>";
   writeXMLString(t,cd->name());
   t << "</compoundname>" << endl;

Paul Ross


**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************

[Doxygen-develop] space after doxylogo in html-footer

[Stefan K. <ko...@im...>]

hi hi,

the html-fragment in the current (version 1.3.3) footer look like this:
	<a href="http://www.doxygen.org/index.html">
	<img src="doxygen.png" alt="doxygen" align="middle" border="0">
	</a>
but should better be a oneliner like this:
	<a href="http://www.doxygen.org/index.html"><img src="doxygen.png"
alt="doxygen" align="middle" border="0"></a>

This would avoid that the blue underscores right after the image.

Stefan
-- 
      \|/            Stefan Kost
     <@ @>           private            business
+-oOO-(_)-OOo------------------------------------------------------ - - -  -   -
|       __  Address  Simildenstr. 5     HTWK Leipzig, Fb IMN, Postfach 301166
|      ///           04277 Leipzig      04277 Leipzig
| __  ///            Germany            Germany
| \\\///    Phone    +49341 2253538     +49341 30766101
|  \__/     EMail    st_kost_at_gmx.net kost_at_imn.htwk-leipzig.de
|           WWW      www.sonicpulse.de  www.imn.htwk-leipzig.de/~kost/about.html
===-=-=--=---=---------------------------------- - - -  -    -

[Doxygen-develop] RV: Tell Me about this propourse for improving Doxygen

[Raul L. B. <rl...@ag...>]

> -----Mensaje original-----
> De: Raul Lorenzo Boullosa [mailto:rl...@ag...]=20
> Enviado el: lunes, 08 de septiembre de 2003 14:50
> Para: Doxygen Develop (dox...@li...)
> Asunto: Tell Me about this propourse for improving Doxygen
>=20
>=20
> Hi,
> 	In Wish list of doxygen appear this improvement for it;
>=20
> 	Add call graphs, or sequence graphs for each member to=20
> visualize the internal structure and external dependencies
>=20
> I propose this improvement;
>=20
> 	Add call graphs, or sequence graphs for each entire=20
> project=B4s class to visualize the internal structure and=20
> external dependencies with other classes in the project
>=20
> What do you think?
>=20
> Bye,
>=20

[Doxygen-develop] Russian translation update

[<ca...@cr...>]

	Russian translation update.

[Doxygen-develop] Windows binaries available for Doxygen-1.3.3-20030915

[Petr P. <Pr...@sk...>]

Hi,
=20
If interested, you can download the doxygen binaries
compiled for MS Windows from
=20
  http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
=20
This is the place where you should find also the next
releases.  The name of the archive is constructed=20
from the date of CVS release.
=20
The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)
=20
Regards,
  Petr
=20
--=20
Petr Prikryl (prikrylp at skil dot cz)

[Doxygen-develop] Info on the status of the language translators (September 16, 2003)

[Petr P. <Pr...@sk...>]

Info on the status of the language translators (September 16, 2003).

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
                  MORE ATTENTION!=20

This is the last chance for updating the language
translators before the 1.3.4 is released.

This is more "repost of the last Info" than anything else.
The purpose is to wake up some language maintainers from
hibernation ;) -- no offence.

The French and the Italian languages became up-to-date since
the last time. Only, the Italian source was changed to
derive from Translator directly.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D


Related to the doxygen 1.3.3-20030915 in CVS. Full
translator_report.txt included in the attached zip file.
Posted to doxygen-develop, copied to doxygen-users. The
previous report was dated September 10, 2003.

Summary:=20
 - Attention: 1.3.4 is going to be released.
 - The Swedish language has the new maintainer.
 - Total 29, 7 up-to-date, 9 almost up-to-date, 11 slightly=20
   obsolete, 2 obsolete, 1 not maintained, 1 different.=20
 - Searching for the Finnish maintainer.

------------------------------------------------------------

Hi,

Firstly, thanks to all active language maintainers. Now...

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
ATTENTION!=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

If you are the language maintainer, this is a good time to
update your translator now because the 1.3.4 is going to be
released soon. Please, think about users who do not use
sources from CVS, but only the precompiled binaries. The
1.3.4 will be the next public release. I guess that some
people do wait for language updates for your language.

Thanks

Reminder: look at the attached translator report. If you
think that your language should be listed as up-to-date, but
it is not, you probably forgot to change the base class of
your translator class to "Translator". Then, you can run the
doc/translator.pl script to generate the translator report
and check the status of your translator report and see what
has to be done to make it up-to-date.

Note: The translator.pl is the original script that will be
replaced by translator.py one day. You can also give it a
try. In fact, it is almost one-to-one rewrite of the perl
version, so do not be disappointed if you like Python. It is
planned to be rewritten using the OO approach.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
New maintainer for the Swedish language
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

There is the new maintainer for the Swedish language.
Mikael Hallin, welcome on the board!

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Current status
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The total is 29 languages now. The new one is not really
new. It is the JapaneseEn which slightly modifies the
English one. Because it is derived from TranslatorEnglish,
it is reported as really obsolete, which is not true. The
newer translator.py script will be modified not to report
such translators this way.

Five of the languages are up-to-date: Brazilian, Croatian,
Czech, Dutch, English, French, and Italian. Congratulations!
(... also to myself ;)

Seven of the languages are very close to the up-to-date
status. They reflect at least some changes since Doxygen 1.3
release: Chinese Traditional, Japanese,
Portuguese, Spanish, Swedish, Serbian, and German (ordered
by alphabet and by status). Good job!

Eleven of the languages are slightly obsolete, but they
still require impementing not more than 18 methods: Danish,
Korean, Polish, Russian, Slovak, Catalan, Romanian, Slovene,
Chinese, Greek, and Ukrainian (ordered by alphabet and by
status).=20

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

  -----------------------------------------------
  We still have not found new Finnish maintainer. =20
  The translator became extremely obsolete, and=20
  it seems that the original maintainer is not
  in touch with doxygen anymore.
  -----------------------------------------------

With regards,
  Petr

--=20
Petr Prikryl, (prikrylp at skil dot cz)

[Doxygen-develop] Info on the status of the language translators (September 10, 2003)

[Petr P. <Pr...@sk...>]

Info on the status of the language translators (September 10, 2003).

Related to the doxygen 1.3.3-20030909 in CVS. Full
translator_report.txt included in the attached zip file.
Posted to doxygen-develop, copied to doxygen-users. The
previous report was dated June 9, 2003.

Summary:=20
 - Attention: 1.3.4 is going to be released.
 - The Swedish language has the new maintainer.
 - Total 29, 5 up-to-date, 9 almost up-to-date, 11 slightly=20
   obsolete, 2 obsolete, 1 not maintained, 1 different.=20
 - Searching for the Finnish maintainer.

------------------------------------------------------------

Hi,

Firstly, thanks to all active language maintainers. Now...

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
ATTENTION!=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

If you are the language maintainer, this is a good time to
update your translator now because the 1.3.4 is going to be
released soon. Please, think about users who do not use
sources from CVS, but only the precompiled binaries. The
1.3.4 will be the next public release. I guess that some
people do wait for language updates for your language.

Thanks

Reminder: look at the attached translator report. If you
think that your language should be listed as up-to-date, but
it is not, you probably forgot to change the base class of
your translator class to "Translator". Then, you can run the
doc/translator.pl script to generate the translator report
and check the status of your translator report and see what
has to be done to make it up-to-date.

Note: The translator.pl is the original script that will be
replaced by translator.py one day. You can also give it a
try. In fact, it is almost one-to-one rewrite of the perl
version, so do not be disappointed if you like Python. It is
planned to be rewritten using the OO approach.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
New maintainer for the Swedish language
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

There is the new maintainer for the Swedish language.
Mikael Hallin, welcome on the board!

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Current status
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The total is 29 languages now. The new one is not really
new. It is the JapaneseEn which slightly modifies the
English one. Because it is derived from TranslatorEnglish,
it is reported as really obsolete, which is not true. The
newer translator.py script will be modified not to report
such translators this way.

Five of the languages are up-to-date: Brazilian, Croatian,
Czech, Dutch, and English. Congratulations! (... also to
myself ;)

Nine of the languages are very close to the up-to-date
status. They reflect at least some changes since Doxygen 1.3
release: Chinese Traditional, French, Italian, Japanese,
Portuguese, Spanish, Swedish, Serbian, and German (ordered
by alphabet and by status). Good job!

Eleven of the languages are slightly obsolete, but they
still require impementing not more than 18 methods: Danish,
Korean, Polish, Russian, Slovak, Catalan, Romanian, Slovene,
Chinese, Greek, and Ukrainian (ordered by alphabet and by
status).=20

Two of the languages -- Hungarian and Norwegian -- must
implement about 45 methods to become up-to-date. Please, try
harder. Or should we search for not-so-tired, new
maintainers? Keep in mind that the translator adapters, used
for your translator classes, make Doxygen slightly bigger
and more complex. After updating your languages, the
adapters can be removed.

  -----------------------------------------------
  We still have not found new Finnish maintainer. =20
  The translator became extremely obsolete, and=20
  it seems that the original maintainer is not
  in touch with doxygen anymore.
  -----------------------------------------------

With regards,
  Petr

--=20
Petr Prikryl, (prikrylp at skil dot cz)

[Doxygen-develop] Windows binaries available for Doxygen-1.3.2-20030909

[Petr P. <Pr...@sk...>]

Hi,
=20
If interested, you can download the doxygen binaries
compiled for MS Windows from
=20
  http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
=20
This is the place where you should find also the next
releases.  The name of the archive is constructed=20
from the date of CVS release.
=20
The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)
=20
Regards,
  Petr
=20
--=20
Petr Prikryl (prikrylp at skil dot cz)

[Doxygen-develop] doxywizard 1.3.3 preview posted for MacOS X

[George V. <gy...@ma...>]

 Hi,

I have posted the first reincarnation of the OS X native doxywizard to:

http://homepage.mac.com/gyvarga/.cv/gyvarga/Public/doxygen/doxywizard.app.sit-link.sit

if this link does not work try connecting to http://homepage.mac.com/gyvarga/ and go to doxygen and download the doxywizard.app.sit file.

Known problems:
icon is wrong. I have used the Qt assistant icon as a place holder until the final one will be created.

No command line tools. use the ones you already have.

When saving a new file use the save as command. You have to do this on every platfrom.

Copyrigh might be wrong in get info.

ReadMe and disk image is missing.
The application does not fit on a 1024 pixel wide screen. On 10.1 the last 20-30 pixels are cut off. Every controll is still reachable.
On 10.2 the search tab (the last one) is not seen and the left most controls are off the screen.

How does it work and what it contains:

The application is a compilation of the original 1.3.3 doxywizard. It has been modified to use the doxygen included in its bundle. It does NOT uses any other version you have. To install unstuff the sit file and move the application anywhere you want. It claim the DOXY file type and the doxygen file extension. If you name your Doxyfiles anding in .doxygen double clicking on them should start up doxywizard.
When you let it run you will get the spinning rainbow until doxygen does its work. You can open Console to see where what it is doing (if you did not checked the quite flag).

The application has been run on 10.1.x (latest 10.1) and  10.2.6.


Modifications to sources:
I have modified the RunDoxygen function to run the doxygen from the application bundle.
I also modified the Makefile.Doxywizard to automatically build/copy the needed parts. One should change the doxygen.pro or doxygen.pro.in files to genereate the correct make files automatically.

The Qt 3.2.1 is used and there were some problems there too.

ToDo:
Icons
Read Me
Disk image

moving makefile changes to .pro files
creating developer documentation

Best regards
George Varga

[Doxygen-develop] New Brazilian translator

[FJTC (F. J. T. Chino) <ch...@ic...>]

Hi there!

Here goes the new version of Brazilian translator.

See you.
FJTC

----------------------------------------------------------------------
           FJTC (Fabio Jun Takada Chino) - ch...@ic...
      Computer Science - ICMC - University of Sao Paulo - Brazil
              GBDI - Grupo de Base de Dados e Imagens
----------------------------------------------------------------------
Homepage
  http://www.icmc.usp.br/~chino (main)
  http://gbdi.icmc.usp.br/ (GBDI)
  http://www.fjtc.hpg.com.br/ (Anime - Portuguese Only)
  http://www.bbits.hpg.com.br/ (Game Programming - English Only)
======================================================================

[Doxygen-develop] Re: MacOS X doxywizard status

[George V. <gy...@ma...>]

>>
>>creating installation package (disk image file).
>
>I could probably contribute to this - I've got some shell scripts that 
>whip together the disk image on another project...

Thank you. Naturally making it by hand is my first goal then we should 
automate it.



>>Testing on other systems. I will do this on the week-end on 10.2.
>
>If you can send me the disk image or let us know where to get it, I could 
>also do some testing on it...

My mac is currently off the internet. On the week-end I will put an 
"installer" onto my .Mac homepage.

>>Because macOS X does not support scrolling the tabs as windows does the 
>>window is very wide. It might not fit on smaller screens. (I am running 
>>1600x1200). I will measure this. The contents of the tab panels have 
>>sometimes shrunk to not fill the available space. It usually jumped 
>>between filled state and shrunken state. It caused controls on the right 
>>side being hidden. I think this is might be a Qt bug.
>
>The OS X way would probably be to have a scrollable row of icons on top of 
>the window, but I doubt that would be easy to squeeze in without having to 
>conditionalize a lot of code :(
>
>>
>>The look of the application is just not mac like. It has the aqua widgets 
>>but it looks a bit weird. This is an inherent problem of Qt applications.
>
>I think it's either live with it or design e.g. a Cocoa app as the 
>frontend. Maybe there's some common code that could be used to get the 
>available options, etc? AFAIK, doxygen itself uses a subset of the Qt 
>libraries for some generic classes (strings, localization, whatnot). I 
>haven't had a look at the doxywizard code yet, but maybe there's some code 
>that could be shared among a Qt implementation and a custom UI frontend? 
>OTOH, it may not be worth the time if the Qt frontend is functional, but 
>just not quite as aesthetic as a native Aqua frontend... :(

I think we have to live with these limitations. Doxywizard uses lots of 
code from doxygen and Qt.

George 

[Doxygen-develop] Windows binaries available for Doxygen-1.3.2-20030904

[Petr P. <Pr...@sk...>]

Hi,
=20
If interested, you can download the doxygen binaries
compiled for MS Windows from
=20
  http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/
=20
This is the place where you should find also the next
releases.  The name of the archive is constructed=20
from the date of CVS release.
=20
The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)
=20
Regards,
  Petr
=20
--=20
Petr Prikryl (prikrylp at skil dot cz)
=20

=20

Re: [Doxygen-develop] MacOS X doxywizard status

[Jens M. <ju...@ma...>]

Am Freitag, 05.09.03 um 08:16 Uhr schrieb George Varga:

> Dear All,
>
> I have made great progress on creating the Doxywizard application for 
> MacOS X. I should say that at some stages I just said I will stop 
> here, but after a calm down I went back and continued.
>
> I have built QT 3.2.1 for Mac and compiled doxywizard. I have also 
> created the bundle and now doxywizard can start up and edit the 
> Doxyfiles. It can also run the doxygen from itself.
>
> The compilation has been done on MacOS X 10.1.5 so the resulting 
> executable is able to run 10.1, 10.2 and up.

Thanks, that sounds great!

> To Do:
> creating icons for doxywizard. For this I would need a rather large 
> image (100x100 pixel) that will be used as the recurring element for 
> the application and for doxyfile icons. Unfortunately the Doxygen logo 
> (with the string in it) is not useful because when it is scaled back 
> to 32x32 it would be just an orange rectangle. I would prefer use the 
> gear used in doxywizard to run doxygen. I do not know however if this 
> gear is a generic one or created for doxygen.
>
> modifying the make files (doxywizard.pro or doxywizard.pro.in or 
> doxywizard.t) and adding new files for the application bundle. To 
> create the wizard I had to change the makefile.doxywizard link 
> settings. I had to remove the X11 libs and had to add some MacOS 
> specific libs. I hand created the application bundle and moved its 
> contents by hand into it. This could be also automated via the 
> makefile. As I am not really good at the tmake automation I might need 
> your help to adjust the root files (*.pro or *.t) depending on the 
> supplied makefiles.
>
> creating installation package (disk image file).

I could probably contribute to this - I've got some shell scripts that 
whip together the disk image on another project...

>
> Testing on other systems. I will do this on the week-end on 10.2.

If you can send me the disk image or let us know where to get it, I 
could also do some testing on it...

>
> Updating Building Doxygen pages. On my progress I want to add help for 
> the next ones.
>
> Known problems:
> Because macOS X does not support scrolling the tabs as windows does 
> the window is very wide. It might not fit on smaller screens. (I am 
> running 1600x1200). I will measure this. The contents of the tab 
> panels have sometimes shrunk to not fill the available space. It 
> usually jumped between filled state and shrunken state. It caused 
> controls on the right side being hidden. I think this is might be a Qt 
> bug.

The OS X way would probably be to have a scrollable row of icons on top 
of the window, but I doubt that would be easy to squeeze in without 
having to conditionalize a lot of code :(

>
> The look of the application is just not mac like. It has the aqua 
> widgets but it looks a bit weird. This is an inherent problem of Qt 
> applications.

I think it's either live with it or design e.g. a Cocoa app as the 
frontend. Maybe there's some common code that could be used to get the 
available options, etc? AFAIK, doxygen itself uses a subset of the Qt 
libraries for some generic classes (strings, localization, whatnot). I 
haven't had a look at the doxywizard code yet, but maybe there's some 
code that could be shared among a Qt implementation and a custom UI 
frontend? OTOH, it may not be worth the time if the Qt frontend is 
functional, but just not quite as aesthetic as a native Aqua 
frontend... :(

</jum>

[Doxygen-develop] MacOS X doxywizard status

[George V. <gy...@ma...>]

Dear All,

I have made great progress on creating the Doxywizard application for MacOS 
X. I should say that at some stages I just said I will stop here, but after 
a calm down I went back and continued.

I have built QT 3.2.1 for Mac and compiled doxywizard. I have also created 
the bundle and now doxywizard can start up and edit the Doxyfiles. It can 
also run the doxygen from itself.

The compilation has been done on MacOS X 10.1.5 so the resulting executable 
is able to run 10.1, 10.2 and up.

To Do:
creating icons for doxywizard. For this I would need a rather large image 
(100x100 pixel) that will be used as the recurring element for the 
application and for doxyfile icons. Unfortunately the Doxygen logo (with 
the string in it) is not useful because when it is scaled back to 32x32 it 
would be just an orange rectangle. I would prefer use the gear used in 
doxywizard to run doxygen. I do not know however if this gear is a generic 
one or created for doxygen.

modifying the make files (doxywizard.pro or doxywizard.pro.in or 
doxywizard.t) and adding new files for the application bundle. To create 
the wizard I had to change the makefile.doxywizard link settings. I had to 
remove the X11 libs and had to add some MacOS specific libs. I hand created 
the application bundle and moved its contents by hand into it. This could 
be also automated via the makefile. As I am not really good at the tmake 
automation I might need your help to adjust the root files (*.pro or *.t) 
depending on the supplied makefiles.

creating installation package (disk image file).

Testing on other systems. I will do this on the week-end on 10.2.

Updating Building Doxygen pages. On my progress I want to add help for the 
next ones.

Known problems:
Because macOS X does not support scrolling the tabs as windows does the 
window is very wide. It might not fit on smaller screens. (I am running 
1600x1200). I will measure this. The contents of the tab panels have 
sometimes shrunk to not fill the available space. It usually jumped between 
filled state and shrunken state. It caused controls on the right side being 
hidden. I think this is might be a Qt bug.

The look of the application is just not mac like. It has the aqua widgets 
but it looks a bit weird. This is an inherent problem of Qt applications.

Saving a new (not yet saved) document does not pops up the Save As dialog. 
Neither on Windows.


George Varga

[Doxygen-develop] Italian translation update

[Alessandro F. <ale...@da...>]

Hi all,
Here is the updated italian Doxygen translation containing elements added
since v1.3.3.

--
Alessandro Falappa

[Doxygen-develop] New Doxygen modder - How to build? (VS2002)

[Daniel S. <dig...@ho...>]

Hi everyone.

I have been using Doxygen for about a year (at first as an imposed 
programming class requirement) and now have started getting 
interested/involved in a few OSS projects.

In my latest one, I wanted to integrate the News Archive as a Doxygen imput 
file - I do not really want to start messing with HTML myself - and I ran 
into two simple limitations that I would like to fix:
1- Be able to have links within page/section/etc titles - should be almost 
as simple as parsing titles like normal text.
2- Prevent the extra pages from showing up in the Related Pages page - 
possibly by adding a "@norelatedpage" special command to add a flag telling 
the Related Pages generator to ignore that page.

For what I am trying to do, these two simple little features would go a long 
way.

Those two changes/features are most likely nearly trivial to implement and I 
would be happy to implement them myself... if I could manage to build the 
stock Doxygen with VS2002. When I try to build it, there is a dozen 
(exactly) missing files. Some of those are nowhere to be found (like 
Doxygen's version.cpp that should contain versionString="1.3.3")  but most 
have CPP-ish looking '.l' files I do not quite know what I am supposed to do 
with. I am guessing that there are a few preliminary steps and probably 
extra tools required.

I have looked around the directories and Doxygen's site but could not find 
anything that looked like an "How to build" file. So, besides making an 
implicit feature request (that I may very likely end up implementing), could 
anyone give me some how-to-build Doxygen with VS2002 tips&pointers?

[... I could build on my LinBox... but all my current projects are Win32 so 
having to switch between two computers all the time would be inconvenient 
and much slower since LinBox is a P233MMX so I'd rather use that as a last 
resort if getting Doxygen to compile with VS2002 looks like too much 
hassle... do my mod on LinBox, submit the changes for inclusion in the next 
CVS and then wait for the next Win32 build... I could also live with that.]

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8.  
http://join.msn.com/?page=features/junkmail

[Doxygen-develop] resend with attachment: missing documentation lines when using defgroup and addtogroup

[George V. <gy...@ma...>]

Sorry the attachment was not added to the previous post. here it is.

Dear Dmitri,

I have found a problem with doxygen 1.3.2 on Windows 2000 SP4. If one uses 
a defgroup to define a group and in an other file it adds some more info to 
this group via addtogroup the first paragraph of the documentation in the 
addtogroup  comment is not shown in the resulting HTML output.

The attached sample contains a small case that reproduces the problem.
The two cpp files contain the source. Use the doxyfile to create a new 
documentation. in the HTML folder you find the html file showing the 
problem. As I remember I was also able recreate the problem with 1.3.3 but 
I do not have it currently installed.

Happy Hunting
George Varga

[Doxygen-develop] missing documentation lines when using defgroup and addtogroup

[George V. <gy...@ma...>]

Dear Dmitri,

I have found a problem with doxygen 1.3.2 on Windows 2000 SP4. If one uses 
a defgroup to define a group and in an other file it adds some more info to 
this group via addtogroup the first paragraph of the documentation in the 
addtogroup  comment is not shown in the resulting HTML output.

The attached sample contains a small case that reproduces the problem.
The two cpp files contain the source. Use the doxyfile to create a new 
documentation. in the HTML folder you find the html file showing the 
problem. As I remember I was also able recreate the problem with 1.3.3 but 
I do not have it currently installed.

Happy Hunting
George Varga

Re: [Doxygen-develop] MacOS X doxywizard

[Jens M. <ju...@ma...>]

Am Dienstag, 02.09.03 um 09:03 Uhr schrieb George Varga:

> Dear All,
>
> I would like to thank you for the Doxygen Package. I turned to be a 
> big fan of it in a very short time. At my company we are using it to 
> document a rather big project on Windows.
>
> We have found some interesting behavior that I will address in 
> separate mails, but I have to create small cases for them.
>
> This letter is about a missing piece of the package. I am a long 
> standing MacOS developer and as I see there is no doxywizard for MacOS 
> X. If nobody is working on it I would like to write one.
>
> My goal is to deliver a real MacOS X application that could be used 
> the same way as the doxywizard on Windows with maybe some additional 
> functionallity.
>
> I know that on UNIX people are used to make, install, run things from 
> the command line. On MacOS this is not the case. Apple has created a 
> very good cover on the UNIX underpinnings. This allows users, even 
> developers to not touch the terminal window for they whole life.
> I would prefer to make such a cover for doxygen.
> Some technical background:
> Apple has created Bundles which are directories that look like files. 
> In a bundle you can have anything: applications, multi-file documents 
> (like a database, a help for something, a web site). An application 
> bundle contains the application and it can contain additional things 
> that the application needs. In the Doxygen case the Doxywizard.app 
> would contain the wizard, the doxygen executables (doxygen, 
> doxytag,...), the doxygen documentation. The installation would only 
> require uncompressing the bundle.
> A user usually would use the Doxywizard.app to do its stuff. The tools 
> are still available from the command line. Naturally entering 
> .../Doxywizard.app/Contents/bin/doxygen is not so easy therefore the 
> application could add symlinks to a user selected directory.
> I would also prefer to add an extension to the Doxyfile. This way the 
> system could bind the extension to the wizard. This could be also a 
> Good Thing for Windows.
>
> Please let me know if anybody else is already doing this kind of work.

I've once successfully built the 'regular' doxywizard on Mac OS X (as 
an X11 application) and it did work...

doxywizard uses the Qt framework, so it should be possible to built it 
using the Mac OS X implementation of the Qt framework (haven't tried 
yet). IIRC, there's a free Qt license for Mac OS X meanwhile when used 
in OpenSource apps...
This should get you a lot of mileage towards your goal and from what I 
know about the Qt framework, this should be possible without changing a 
line of code. I'd rather take this approach than trying to crop up a 
whole new Cocoa app, since as doxygen changes, the doxywizard needs to 
be adjusted to take into account the latest configuration options. If 
the end result is not satisfying, it might be possible to get a better 
result by minor modifications to the doxywizard code while still using 
the same codebase and Qt.

There's nothing that really prevents you from assigning an extension to 
the Doxyfiles - you can always call doxygen with the explicit filename.

I think the first step would be to try and build the doxywizard against 
the Mac OS X Qt libraries to see what it looks like in native Aqua look 
and whether this is acceptable. Once this is done, the next steps like 
packaging could be tackled...

</jum>

[Doxygen-develop] MacOS X doxywizard

[George V. <gy...@ma...>]

Dear All,

I would like to thank you for the Doxygen Package. I turned to be a big fan 
of it in a very short time. At my company we are using it to document a 
rather big project on Windows.

We have found some interesting behavior that I will address in separate 
mails, but I have to create small cases for them.

This letter is about a missing piece of the package. I am a long standing 
MacOS developer and as I see there is no doxywizard for MacOS X. If nobody 
is working on it I would like to write one.

My goal is to deliver a real MacOS X application that could be used the 
same way as the doxywizard on Windows with maybe some additional 
functionallity.

I know that on UNIX people are used to make, install, run things from the 
command line. On MacOS this is not the case. Apple has created a very good 
cover on the UNIX underpinnings. This allows users, even developers to not 
touch the terminal window for they whole life.
I would prefer to make such a cover for doxygen.
Some technical background:
Apple has created Bundles which are directories that look like files. In a 
bundle you can have anything: applications, multi-file documents (like a 
database, a help for something, a web site). An application bundle contains 
the application and it can contain additional things that the application 
needs. In the Doxygen case the Doxywizard.app would contain the wizard, the 
doxygen executables (doxygen, doxytag,...), the doxygen documentation. The 
installation would only require uncompressing the bundle.
A user usually would use the Doxywizard.app to do its stuff. The tools are 
still available from the command line. Naturally entering 
.../Doxywizard.app/Contents/bin/doxygen is not so easy therefore the 
application could add symlinks to a user selected directory.
I would also prefer to add an extension to the Doxyfile. This way the 
system could bind the extension to the wizard. This could be also a Good 
Thing for Windows.

Please let me know if anybody else is already doing this kind of work.

Thank you
George Varga