Re: Groovy Documentation Formatting

On 06/03/2021 04:06, Paul King wrote: On Sat, Mar 6, 2021 at 6:55 AM MG > wrote: @we'd want the full info somewhere: Agree. But since the annotation section headers already have the fully qualified name and the user gets taken there when he clicks the a

Re: Groovy Documentation Formatting

On Sat, Mar 6, 2021 at 6:55 AM MG wrote: > @we'd want the full info somewhere: Agree. > But since the annotation section headers already have the fully qualified > name and the user gets taken there when he clicks the annotation (short) > name on the sidebar, so I feel we are good here :- > Pote

Re: Groovy Documentation Formatting

@we'd want the full info somewhere: Agree. But since the annotation section headers already have the fully qualified name and the user gets taken there when he clicks the annotation (short) name on the sidebar, so I feel we are good here :-) Cheers, mg On 05/03/2021 20:45, Paul King wrote: I

Re: Groovy Documentation Formatting

I agree some improvement in presentation would be great. The main thing for me is to remember that most of the HTML doco is generated (asciidoc or templating). So as long as we modify things from the sources, that should re-generate better. Also, we now also do a PDF version of the documentation. I

Re: Groovy Documentation Formatting

Hi Leo, thanks for your input. My take on this is: I am not against the current tables, but they need some improvement (padding and maybe some lines (if it is a table, why not present it as such ?)). If that improvement is not coming, I would be for taking up your offer to rework them in a gl

Re: Groovy Documentation Formatting

MG, thanks for bringing this up! I hope you don't mind my potentially hijacking your thread to briefly agree with one of your points and then expand on one of the others you brought up... # Left-nav too narrow I think your idea of not using the fully qualified names makes a lot of sense. If someo