I understand, Torten, but we wil get there, one day.
> On 9 Mar 2017, at 23:04, Torsten Bergmann <[email protected]> wrote:
>
> Uko wrote:
>> If there is a rule not to duplicate preferences, why is catalog not
>> following it?
>
> Because at the time when I implemented it for catalog there was no other
> setting.
>
> The enabling/disabling for all GT extension was introduced later. Also the
> confusing
> default was introduced later (with the more hidden spotter extension disabled
> and
> leaving the Catalog setting enabled) leading to this whole mess.
>
> To be honest I dont care or respond anymore on the whole issue because as we
> now know from
> the long discussion the only outcome is that:
>
> <sarcasm>
> - most of us should be knowledgable enough to know that two settings exist
> - most of us should become experts in fixing deficencies with startup scripts
> - most of us should accept that we have to hide features as deep as possible
> in the settings tree
> - most of us should accept that we have to make it as complicated as
> possible to load catalog projects
> - most of us should accept that we can display and access anything in
> spotter except catalog projects
> - most of us should accept that Pharo videos get broken and never match
> reality
> - most of us should continue to "rest in their comfort zone"
> - most of us should continue to be "an egoist instead of being an adult"
> - most of us should be allowed to speak up only when they presented Pharo at
> a university
> - most of us should start working with slow networks
> </sarcasm>
>
> Fixing it by removing Spotter and Catalog completely from Pharo would
> possibly be the
> best solution. Anyone up for a slice?
>
> Bye
> T.
>
