<html><body><div style="color:#000; background-color:#fff, font-family:arial, helvetica, sans-serif;font-size:12pt">Agree 100%. Leave the module as-is and let's improve the doc generator. I don't think we should design the functionality of code around documentation issues.<br><br>-Steve<br class="yui-cursor"><span></span><div style="font-family: inherit; font-size: 12pt;"><br><div style="font-family: inherit; font-size: 12pt;"><font face="Arial" size="2"><div style="border: 1px solid rgb(204, 204, 204); line-height: 0pt; font-size: 0pt; margin: 5px 0px; padding: 0pt;" readonly="true" class="hr" contenteditable="false"></div><b><span style="font-weight: bold;">From:</span></b> Michel Fortin <michel.fortin@michelf.com><br><b><span style="font-weight: bold;">To:</span></b> Discuss the phobos library for D <phobos@puremagic.com><br><b><span style="font-weight: bold;">Cc:</span></b> <br><b><span style="font-weight:
bold;">Sent:</span></b> Thursday, February 10, 2011 8:03 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [phobos] Split std.datetime in two?<br></font><br>
Le 2011-02-10 à 0:54, Jonathan M Davis a écrit :<br><br>> I do have one concern however. As there's a fair bit of functionality in there, <br>> there's a lot of documentation, and I'm afraid that the documentation may be a <br>> bit overwhelming to someone trying to figure out how to use std.datetime. On the <br>> whole, everything in there is quite easy to use, but there's a lot of it.<br><br>I agree that the documentation isn't very well structured; std.datetime is hardly the only module with this problem.<br><br>I disagree about restructuring the code if the goal is only to make the documentation better. The right solution is to improve the documentation generation, not to contort the code to fit a particular documentation structure. Let's ask ourself how we want the documentation to be, then lets look at how we can achieve that.<br><br>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). Perhaps it'd also be nice if things could be split on multiple pages, but I'm not sure on what criterion.<br><br><br>-- <br>Michel Fortin<br><a ymailto="mailto:michel.fortin@michelf.com" href="mailto:michel.fortin@michelf.com">michel.fortin@michelf.com</a><br>http://michelf.com/<br><br><br><br>_______________________________________________<br>phobos mailing list<br><a ymailto="mailto:phobos@puremagic.com" href="mailto:phobos@puremagic.com">phobos@puremagic.com</a><br>http://lists.puremagic.com/mailman/listinfo/phobos<br><br><br></div></div></div><br>
</body></html>