On 10 feb 2011, at 17:40, spir wrote:

> On 02/10/2011 02:03 PM, Michel Fortin wrote:
>> Creating a table of content sorted by task (like Andrei did for std.algorithm) looks like a good start. Another idea to address the nesting problem could be to collapse the nested declarations with a show/hide javascript button to avoid having nested declarations you don't know they belong to what (if you've explicitly disclosed some content, you should know what it is).
> 
> Very similar to what I dream of: that the doc page is folded just like code in an editor or a directory tree, letting only headers visible. Then one can quickly browse it, see the dependancies (showed by indentation like now), and open sections at will to read the actual doc contents.
> 
> class Range +		<-- open doc for 'Range'
>    bool empty() +	<-- open doc for 'empty'

This is called CandyDoc (see one of my other posts). But CandyDoc has this in a separate menu/tree.

> [Actually, it's more or less reproducing python's doc structure in source (where the doc sections belong to what they describe, instead of beeing weirdly & unpractically placed before).]
> 
>> Perhaps it'd also be nice if things could be split on multiple pages, but I'm
> not sure on what criterion.
> 
> Rather not, I guess, would increase the complexity.
> 
> Denis
> -- 
> _________________
> vita es estrany
> spir.wikidot.com
> 
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

-- 
/Jacob Carlborg