Re: [Doxygen-develop] Feature request: color coded comments in source browser

[Dimitri v. H. <do...@gm...>]

Hi Michael,

On Mar 29, 2013, at 4:13 , Michael Stangeland <mi...@st...> wrote:
> Eclipse and Notepad++ interpret the comment sections nicely with colorized
> keywords, and a different color for normal comments verses Doxygen markup
> comments.  But when looking at the source the Doxygen markup is now harder
> to read.  (I use STRIP_CODE_COMMENTS=NO because I write minimal comments and
> what little I do write,  I still want to see it)
> 
> When generating the source code view, would it be possible to add a few more
> styles for the elements inside the comment sections?  I figure the parser
> already identifies the them.  Moreover, this would help understand how the
> parser is using the markup.
> 
> In the CSS file I found how to change the style, but obviously only one
> style for all comments.
> 
> span.comment {
> 	color: #800000
> }
> 
> I propose:
> "comment" for normal comments.
> "docomment" for general Doxygen
> "dockeyword" or "docommand" for interpreted Doxygen commands (assuming the
> same engine used to interpret the markup, ALIASes would also be identified
> automatically).
> 
> The extra nice to have would be to also identify and colorize the parsed
> components of the commands such as <name>.  Also Bold, italic and other
> formatting could be reflected.
> 
> Maybe going too far... but the source markup that produces links could also
> be clickable.

Then why not go one step further and let doxygen render the special comments
as it does for the documentation?

Then you could have a documentation view with inline code (when INLINE_SOURCES=YES)
and the inverse; a source view with inline documentation 
(when SOURCE_BROWSER=YES and STRIP_CODE_COMMENTS=NO)

Or do you really want to see the markup commands in the source view, like you
would in Eclipse or Notepad++?

Regards,
  Dimitri