RE: [Doxygen-users] RE: Is it possible to customise the page layo ut for class members

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

while agreeing that the documentation needs to be useful, I'll point out
that what Doxygen currently outputs is LEGAL syntax for the compiler, your
proposal isn't.

-----Original Message-----
From: Joh...@ub... [mailto:Joh...@ub...]
Sent: Friday, 2001 June 29 11:27
To: dox...@li...
Subject: [Doxygen-users] RE: Is it possible to customise the page layout
for class members



Before I start there may be somnething about this on the sourceforge 
website but the search facility is broken and I get this message ......

-------------
htsearch detected an error. Please report this to the returned matches
webmaster of this site. The error message is:
unable to read configuration file '/bigassraid/htdig//conf/11668.conf'
-------------



Is it possible to customise the page layout for class members so that 
instead of a table like 

__________________________________
| RETURN VALUE | METHOD(ARGS)     |
|_________________________________|
| RETURN VALUE | METHOD(ARGS)     |
|_________________________________|


we have the alternative format ...

____________________________________
| METHOD  | (ARGS)   | RETURNVALUE |
|__________________________________|
| METHOD  | (ARGS)   | RETURNVALUE |
|__________________________________|

As this is a bit easier on the eye when looking to a particular method.

In my project out type names are pretty long and in the current table 
format the return value column takes up most of the width of the pane, 
leaving the method name and its ares all scrunched up.

I've tried the alternative format shown above in an html editor and it 
is much more readable.

I've attached examples of the orig and alternative formats.





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