<p>Absolutely no objections from me. ;)</p>
<p>Thanks for your help Dave. I wasn't sure how to proceed.<br></p>
<p>Alex</p><br><br><div class="gmail_quote">2011/1/19 David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Mon, Jan 17, 2011 at 03:14:20PM +0100, Alexander Lazarevi?? wrote:<br>
> Although in a feature freeze I would like to add the following as the first<br>
> entry of the "How to extend the system" workspace:<br>
><br>
> "Install and open a SystemReporter. You can use this information when<br>
> sending out bug reports"<br>
> (Installer ss project: 'SystemReporter') install: 'SystemReporter'.<br>
> (Smalltalk at: #SystemReporter) open<br>
><br>
> In the light of the upcoming releases and new VMs I think it would be<br>
> valuable to have something to easily identify a system and the environment<br>
> it's running in.<br>
<br>
</div></div>Are there any objections to the following actions:<br>
<br>
- Copy latest SystemReporter from SqueakSource to trunk, and add it to<br>
the configuration map for trunk.<br>
<br>
- Add an "About this System" menu pick in TheWorldMainDockingBar help<br>
menu to invoke a SystemReporter (if and only if class SystemReporter<br>
is present in the image), and remove the loading instructions from<br>
the "Extending the system" workspace.<br>
<br>
- Add package SystemReporter to the list of packages removed by<br>
#unloadAllKnownPackages.<br>
<br>
The result of the above changes would be that SystemReporter will be<br>
a readily accessible menu pick for all users, and will be a fully<br>
unloadable and reloadable package so as not to contribute to image<br>
bloat.<br>
<br>
If no objections, I will commit the changes to trunk in a day or so.<br>
<br>
Thanks to Alex for this enhancement.<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br>