> On 10 Mar 2015, at 14:05, Andrei Chis <[email protected]> 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.

you can ask that in a special sentence, like the “go to settings” 
recommendation. That wouldn’t break anything (you can take the opportunity to 
explain why you want the data… otherwise natural tendency  will be to deny it 
anyway :)

>  
> 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 :)

you know that you are not helping your case, isn’t? ;)
Spotter is a particular tool… but its particularities does not allow it to 
break anything… 

> 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?

well… we need to discuss it. 
In particular, I like the vision of one IDE, not separated tools. 
And I would like a good “control center” more than many separated and probably 
incoherent (but certainly harder to maintain) options. 

but again… for Pharo5 I’m open to a discussion… not for Pharo4 :)

Esteban

> 
> 
> Cheers,
> Andrei
>  
> 

Reply via email to