RE: [Doxygen-users] Customizing look in Doxygen

[Wagner, V. <VW...@se...>]

You must be talking about the summary info, not the detailed info, right??

-----Original Message-----
From: Joh...@ub... [mailto:Joh...@ub...]
Sent: Monday, 2001 July 16 09:18
To: dox...@li...
Subject: [Doxygen-users] Customizing look in Doxygen


Dimitri / Joe

Are the CR's (carriage returns) that was given in the example 
meaningful ?
If so then this is not the format that doxygen produces in version 
1.2.8.1 .

Joe's Example
> return_type
> function_name(
>     argument_type1                    argument_name1,
>     argument_type2                    argument_name2)
> 

I'm using doxygen 1.2.8.1  and the sort of HTML format for class 
members I'm getting is ...

<tr>
    <td >RETURN_TYPE</td>
    <td>METHOD_NAME (ARGUMENT_1, ARGUMENT_2)</td>
</tr>

If the CR's in the example Joe gave were meaningful then perhaps Joe is 
suggesting something where the args are in separate cells on different 
rows in the HTML table ie a format more like ....

<tr>
    <td>RETURN_TYPE</td>
    <td>&nbsp;</td>
  </tr>
  <tr>
    <td>METHOD_NAME</td>
    <td>(ARGUMENT_1</td>
  </tr>
  <tr>
    <td>&nbsp;</td>
    <td>ARGUMENT_2)</td>
  </tr> 


I have the same problem as Joe (ie "rather long function names and 
argument types") and the 1.2.1.8 format of HTML documentation as shown 
above is pretty unreadable. 

Joe's suggestion might help us with our common specific problem however 
this mail chain make me wonder if it would be preferable to have a more 
general solution - one that would allow personalisation of the 
formatting algorithm by for example an optional runtime plugin (ie on 
unix a .so file or NT would use a .dll file  - dunno what other 
platforms offer for this sort of thing). This approach might help avoid 
a proliferation of compiler and runtime switches for other formats that 
users might wish to define. 

JL



This transmission may contain information that is privileged, confidential
and exempt from disclosure under applicable law.
If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED.
If you received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic or
hard copy format.
Thank you