No doubt. That would be perfect, so long as beginners and folks new to the update know how to find that. <div>So, it seems to make sense for the SM app to have a link to the wiki page for those who want more info. so that everyone can be on the same page (literally and figuratively).</div>
<div> </div><div>And, it seems logical for the SM app to have an indicator to say that the Safe to Install filter is on, and provide a way to turn it off in case a programmer needs to find old code to test. <br><br>There's nothing to indicate what 'SqueakMap Package Loader (7 shown out of 773 packages)' means.<br>
<br>- Darius<br><br><div class="gmail_quote">On Wed, Dec 28, 2011 at 12:10 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 28 December 2011 17:38, Darius Clarke <<a href="mailto:socinian@gmail.com">socinian@gmail.com</a>> wrote:<br>
><br>
> On Wed, Dec 28, 2011 at 9:16 AM, Darius Clarke <<a href="mailto:socinian@gmail.com">socinian@gmail.com</a>> wrote:<br>
><br>
>><br>
>> But a current SqueakMap refresh in 4.3 has almost none of the prior<br>
>> applications in it any more. It's been neglected too by the community.<br>
><br>
><br>
> Correction: With the "Safe To Install" filter turned on by default.<br>
<br>
</div></div>Given that 4.3 is 3 days old, isn't that to be expected? Quoting from<br>
Swiki (<a href="http://wiki.squeak.org/squeak/2726" target="_blank">http://wiki.squeak.org/squeak/2726</a>),<br>
<br>
"With Squeak 4.2, the SqueakMap Catalog opens without the rot showing.<br>
Whenever a new version of Squeak is released, all of the packages that<br>
were visible in the list in the prior version no longer appear in the<br>
new version. This is because the SqueakMap process requires authors to<br>
re-designate their applications as working in the new Squeak release."<br>
<br>
Now one could have some kind of server sitting somewhere taking a<br>
fresh image and running install scripts with some kind of script<br>
verifying that the package loaded correctly (say, by running the<br>
package's tests), and on a green light marking the SM package as "Safe<br>
To Install". But at any rate, right now it's up to the package owner<br>
to perform this task.<br>
<br>
frank<br>
<br>
> Darius<br>
><br>
><br>
><br>
<br>
</blockquote></div><br></div>