<div dir="ltr">Ok<div><br></div><div>Karl</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 16, 2015 at 6:39 PM, Chris Muller <span dir="ltr"><<a href="mailto:ma.chris.m@gmail.com" target="_blank">ma.chris.m@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Maybe it would be nice if the filters where off when opening the SqueakMap<br>
> browser. With filters on it seems to be empty and not functioning.<br>
<br>
</span>No. Just a gentle reminder, the best way to talk about SqueakMap and<br>
figure out how to improve it is to orient ourselves with the<br>
requirements:<br>
<br>
<a href="http://wiki.squeak.org/squeak/6183" rel="noreferrer" target="_blank">http://wiki.squeak.org/squeak/6183</a><br>
<br>
Presenting everything in the list would violate requirement #4.<br>
Publishers who simply follow these publishing guidelines [1] are able<br>
to meet these requirements, and so what users see in the list is what<br>
WORKS. If we show "everything" then we're hiding what works, and SM<br>
becomes useless again.<br>
<br>
Why do you say its an empty list? I just checked Squeak 5.0 and there<br>
are at least 20 packages showing up in there..?<br>
<br>
IF nothing were to show up in the list when "Safely-available" filter<br>
(and nothing else) is checked, then that's on us as a community. It<br>
simply means that we didn't care enough to take the 5 minutes<br>
necessary to recertify our packages for the latest Squeak. It is what<br>
it is, but let's not fake out the "truth".<br>
<br>
Thankfully, we DON'T have a blank list in 5.0. Thanks to those in the<br>
community who have gotten on board with the publishing guidelines we<br>
have packages on SM that actually WORK (if they were done right) and<br>
have single one of those requirements met. Users are able to consume<br>
those packages with one click instead of being forced to come begging<br>
to the list for "how to load it"..<br>
<br>
We will get there!<br>
<br>
[1] -- SqueakMap Publishing Guidelines<br>
<a href="http://wiki.squeak.org/squeak/6182" rel="noreferrer" target="_blank">http://wiki.squeak.org/squeak/6182</a><br>
<br>
[2] -- How to designate existing SqueakMap packages for a new version of Squeak<br>
<a href="http://wiki.squeak.org/squeak/6180" rel="noreferrer" target="_blank">http://wiki.squeak.org/squeak/6180</a><br>
<div class="HOEnZb"><div class="h5"><br>
> There is always warnings about package not being compatible when you try to<br>
> load them anyway.<br>
><br>
> Karl<br>
><br>
> On Tue, Sep 15, 2015 at 10:04 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
>><br>
>> After review and some thought, it has become clear to me that Dave's<br>
>> change is incorrect. Please take a look at the SqueakMap filters and<br>
>> consider them from the context of the use-cases -- what users need to<br>
>> do with SqueakMap, and NOT from the context of a database that needs<br>
>> to produce generalized "query results" <---- because it doesn't.<br>
>><br>
>> "Published" are the ones which have software to install, while<br>
>> "Auto-installable" shows only packages that are installable from the<br>
>> "Install" menu selection within the image. These two filters are<br>
>> useful together in a restricting fashion, not an inflating one, so<br>
>> that newbies can see what's ready to go.<br>
>><br>
>> It was then that I also realized that Hannes' combination was not a<br>
>> use-case either. The use-cases we have are: 1) user wants to install<br>
>> software or, 2) user wants to see what they have already installed.<br>
>> Seeing a cumulative list of both installed and uninstalled satisfies<br>
>> neither use-case.<br>
>><br>
>> Nevertheless you may once again "Clear all filters" (which was broken<br>
>> by Dave's commit) if you want to see everything.<br>
>><br>
>> I still say SqueakMap catalog can and needs improvement, but we need<br>
>> to really consider our changes because its clear that Göran put a lot<br>
>> of thought into the usage of SqueakMap and its role in the community;<br>
>> so I think we can afford to be a bit more skeptical before thinking<br>
>> something like that was a bug in the first place and for nine years<br>
>> running..<br>
>><br>
>><br>
>> On Tue, Sep 15, 2015 at 2:58 PM, <<a href="mailto:commits@source.squeak.org">commits@source.squeak.org</a>> wrote:<br>
>> > Chris Muller uploaded a new version of SMLoader to project The Trunk:<br>
>> > <a href="http://source.squeak.org/trunk/SMLoader-cmm.85.mcz" rel="noreferrer" target="_blank">http://source.squeak.org/trunk/SMLoader-cmm.85.mcz</a><br>
>> ><br>
>> > ==================== Summary ====================<br>
>> ><br>
>> > Name: SMLoader-cmm.85<br>
>> > Author: cmm<br>
>> > Time: 15 September 2015, 2:58:07.033 pm<br>
>> > UUID: 21a75b8d-4a1b-49c8-8f82-fbbd74fae96b<br>
>> > Ancestors: SMLoader-dtl.84<br>
>> ><br>
>> > Revert dtl.84, because it broke the Catalog filters.<br>
>> ><br>
>> > =============== Diff against SMLoader-dtl.84 ===============<br>
>> ><br>
>> > Item was changed:<br>
>> > ----- Method: SMLoaderPlus>>packageListCalculated (in category<br>
>> > 'lists') -----<br>
>> > packageListCalculated<br>
>> > "Return a list of the SMPackages that should be visible<br>
>> > by applying all the filters. Also filter based on the currently<br>
>> > selected category - if any."<br>
>> > ^ self packages select: [:p |<br>
>> > + filters allSatisfy: [:currFilter |<br>
>> > - filters anySatisfy: [:currFilter |<br>
>> > currFilter isSymbol<br>
>> > ifTrue: [(self perform: currFilter)<br>
>> > value: p]<br>
>> > ifFalse: [self package: p<br>
>> > filteredByCategory: (map object: currFilter)]]]!<br>
>> ><br>
>> ><br>
>><br>
><br>
</div></div></blockquote></div><br></div>