Hi Esteban,

I think we should invoke coherence when it makes sense :).

I agree that when people are searching for settings they should expect to find them in the Settings browser. This makes sense.

But, why is it a good choice to have settings removed from the tool they are about? I think it's not necessarily so clear cut. I think it would make perfect sense to have settings scoped to a certain context (which you can already do with the Settings Browser), but I would not want these contextual settings to be in a window of their own. That is why we invested in having this floating window that disappears when you click away.

Also, in the current case there is an extra reason. As also pointed out by Andrei, we are talking about the data of people. This is sensitive and the status of the uploading should be as apparent as possible to keep people informed.

The other thing to notice is that Spotter is different than anything else in Pharo. I think that should not be held against it :). That does not mean that everything about it is perfect either. I simply say that if we want the future to conform with what we have now, it's not necessarily a good policy.

Cheers,

Doru

On Tue, Mar 10, 2015 at 2:05 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:

Until this conversation started I had no idea that you can actually persist the settings in the Setting browser��
using the 'Export settings' button so that they will be loaded by default in your other images. And I've been
using Pharo for some time :)

disagree :)
here the reason: everybody can think their settings deserve better exposition, and then add a way to change the L&F to add a settings option.��

I still view some settings as more special then the others, especially those that send data out of your image.
��
that will break inner coherence of Pharo.��
and we need to think *all tools* in pharo as one unique IDE�� it has to be coherent.��
your little cog ��breaks coherence.��

Very few things in the current spotter UI are coherent with any other tool from Pharo :)
Yes, the fast that we do not store this setting using the normal settings mechanism it's a bug that should be fixed.
��

I admit we need to do a pass on Settings browser to group better, explain better and remove unnecessary stuff�� maybe on Pharo5 we will find the time.��

For Pharo 5 maybe we can move in the opposite direction. Why not move the settings closed to the tools then separate them in the Settings Browser?

Cheers,
Andrei
��

www.tudorgirba.com

"Every thing has its own flow"