Windows binaries available for Doxygen-1.5.3-20071008 in CVS

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Windows binaries available for Doxygen-1.5.3-20071008 in CVS

Petr Prikryl
Hi,

If interested, you can download the doxygen binaries
compiled for MS Windows from

  http://doxygen.sourceforge.net/dl/doxygen-1.5-cvs/

This is the place where you should find also the next
releases.  Name of the archive file is

    doxygenw20071008_1_5_3.zip.

The related translator report can be found inside
the archive tr20071008_1_5_3.zip.

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... ;)

Regards,
    Petr

P.S. This is probably the last version where sources
were got from CVS server. The next version souces will
be available via SVN.

--
Petr Prikryl (prikrylp at skil dot cz)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Doxygen-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Reply | Threaded
Open this post in threaded view
|

Best way to list features of versions

Frank Peelo
The \version Special Command allows one to write a paragraph about a
specific version of your program.

Putting - at the start of a line allows one to write a bulleted list.

Are these two features supposed to work together?

I get slightly different formatting of the first version, compared with
other versions.

My questions are:
1. Am I using \version the right way, or should versions be documented
    slightly differently?
2. Is the difference in formatting a bug in Firefox or a bug in Doxygen?


Here is how I document versions -- the source of a program which shows
the problem:
--------------------------cut here--------------------------
/*!
    \mainpage Test program

    \section intro_sec Introduction

    This is a dummy .c program to show version numbers in Doxygen

    \section  ver_sec  Release history

    \version  1.0.0.1  --  2007-07-20
    - First version

    \version  1.0.0.2  --  2007-08-02
    - Fixes this
    - Fixes that
    - Fixes the other

    \version  1.0.0.3  --  2007-10-09
    - More bug fixes
    - New features
    - And so on...
*/
#define VERSION "1.0.0.3"

void main(void)
{
   /* blablabla */
}
--------------------------cut here--------------------------

This is a minimal program with 3 documented versions.
The HTML for the version features, formatted for legibility, looks like
this:

--------------------------cut here--------------------------
<dl class="version" compact>
   <dt><b>Version:</b></dt>
   <dd>
     1.0.0.1 -- 2007-07-20
     <ul>
       <li>First version</li>
     </ul>

     <p>
     1.0.0.2 -- 2007-08-02
     <ul>
       <li>Fixes this</li>
       <li>Fixes that</li>
       <li>Fixes the other</li>
     </ul>

     <p>
     1.0.0.3 -- 2007-10-09
     <ul>
       <li>More bug fixes</li>
       <li>New features</li>
       <li>And so on... </li>
     </ul>
   </dd>
</dl>
--------------------------cut here--------------------------

I note that each version has a <p> before it except the first. Editing
the html file, putting <p> before the "1.0.0.1" line and telling Firefox
to refresh, fixes the formatting.

So, what is the best way to document my version changes?

Thanks

Frank





-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Doxygen-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Reply | Threaded
Open this post in threaded view
|

Re: Best way to list features of versions

Dimitri van Heesch-2


On 10/10/07, Frank Peelo <[hidden email]> wrote:
The \version Special Command allows one to write a paragraph about a
specific version of your program.

Putting - at the start of a line allows one to write a bulleted list.

Are these two features supposed to work together?

I get slightly different formatting of the first version, compared with
other versions.

My questions are:
1. Am I using \version the right way, or should versions be documented
    slightly differently?
2. Is the difference in formatting a bug in Firefox or a bug in Doxygen?


Here is how I document versions -- the source of a program which shows
the problem:
--------------------------cut here--------------------------
/*!
    \mainpage Test program

    \section intro_sec Introduction

    This is a dummy .c program to show version numbers in Doxygen

    \section  ver_sec  Release history

    \version   1.0.0.1  --  2007-07-20
    - First version

    \version  1.0.0.2  --  2007-08-02
    - Fixes this
    - Fixes that
    - Fixes the other

    \version  1.0.0.3  --  2007-10-09
    - More bug fixes
    - New features
    - And so on...
*/
#define VERSION "1.0.0.3"

void main(void)
{
   /* blablabla */
}
--------------------------cut here--------------------------

I note that each version has a <p> before it except the first. Editing
the html file, putting <p> before the " 1.0.0.1" line and telling Firefox
to refresh, fixes the formatting.

So, what is the best way to document my version changes?


The version command was not intended for creating a changelog, but
merely to mark a function or class with a certain version number, for instance
the API version in which it first appeared.

You can however redefine the command by putting the following in the config file:

ALIASES = version="\par version"

Which is probably closer to what you had in mind.

Regards,
  Dimitri


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Doxygen-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Reply | Threaded
Open this post in threaded view
|

Re: Best way to list features of versions

Frank Peelo
Dimitri van Heesch wrote:

>
>
> On 10/10/07, *Frank Peelo* <[hidden email] <mailto:[hidden email]>> wrote:
>
>     The \version Special Command allows one to write a paragraph about a
>     specific version of your program.
>
>     Putting - at the start of a line allows one to write a bulleted list.
>
>     Are these two features supposed to work together?
...
>
> The version command was not intended for creating a changelog, but
> merely to mark a function or class with a certain version number, for
> instance
> the API version in which it first appeared.

Ahhh, right. When I read the documentation, I did not understand that. I
thought it was to document versions of the class/program/whatever, in
case there was some special processing that Doxygen could do with
version logs -- not that I know of any, but I'm sure there are features
of Doxygen that I haven't seen yet.

So, that means I just ignore the version command, and write the version
log like any other bulleted list. That has solved my problem.

Thanks

Frank




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Doxygen-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/doxygen-users