<br><br><div class="gmail_quote">On Fri, Sep 3, 2010 at 2:51 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 03.09.2010, at 10:28, Hannes Hirzel wrote:<br>
<br>
> On of the things I have been wondering recently is where the package actually "lives" in the image.<br>
<br>
</div>A package is a (sub-) instance of PackageInfo. Packages are held by PackageOrganizer.<br>
<br>
One idea would be to include a PackageInfo subclass in each package, and its class comment or methods would describe the package. That would hook into HelpSystem so one could browse comments, instructions, examples etc. per package.<br>
<br>
There are a few conventions for that already, e.g. the class name should end in "Info" and it should be in a category named "PackageName-Info".<br></blockquote><div><br></div><div>This is nice. It's also a place to put package initialization/unloading scripts, etc. Is there example code for the above conventions anywhere?</div>
<div><br></div><div>cheers</div><div>Eliot</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
- Bert -<br>
<br>
<br>
<br>
</font></blockquote></div><br>