<div dir="ltr">You can doIt HelpBrowser openOn: SystemReference<div><br><div>That will open a HelpBrowser on all class comments.</div><div><br></div><div>Karl</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Jun 13, 2014 at 6:50 PM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 13-06-2014, at 9:37 AM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
<br>
><br>
> So do I. Personally I like class comments. I don't want to look for methods that contain help text.<br>
<br>
Me too.<br>
<br>
There’s nothing to prevent an extension of the HelpBrowser to have it use the contents of class comments and/or other sources of text, which would make it really easy for people to add content.<br>
<br>
We probably don’t want to clutter the image with large strings (there’s already too many) and class comments get stored in the changes which is a sensible place to have them. It shouldn’t be difficult to make any other local documentation live in the same place(s) - we only need a convention on the method name(s) to allow specified method comments to be sucked in. When online it shouldn’t be beyond us to suck in swiki page content.<br>
<br>
But the mechanism isn’t anywhere near as important as the content. Lots of us are capable of the programming for the mechanism but fewer have the writing talent to produce good documentation - let alone the time.<br>
<div class=""><br>
<br>
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
</div>The Static Typing Philosophy: Make it fast. Make it right. Make it run.<br>
<br>
<br>
</blockquote></div><br></div>