Hi, I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy. If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post. Technically speaking once someone exports preferences, he/she should always use the same kind of image. Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5. Cheers, Juraj
On 16 Mar 2015, at 17:11, Juraj Kubelka <juraj.kubelka@gmail.com> wrote:
Hi,
I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy.
Yes, that is why I never use this export feature, it is broken by design, for me. An image is a persistent world which can hold its own settings. I can imagine some people want some automatic loading in each new image, but that should be opt-in.
If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post.
Technically speaking once someone exports preferences, he/she should always use the same kind of image.
Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5.
Cheers, Juraj
Hi, The problem is that the export exports all values, not the delta between what was chosen and what comes by default. In our case, if I want to choose to always send the anonymous usage information for Spotter, I also have to commit to using a dedicated set of icons. This constraint does not match well the use case. I think we should be able to save selected settings, or just the settings that we modified explicitly. Cheers, Doru On Mon, Mar 16, 2015 at 5:23 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 16 Mar 2015, at 17:11, Juraj Kubelka <juraj.kubelka@gmail.com> wrote:
Hi,
I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy.
Yes, that is why I never use this export feature, it is broken by design, for me.
An image is a persistent world which can hold its own settings.
I can imagine some people want some automatic loading in each new image, but that should be opt-in.
If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post.
Technically speaking once someone exports preferences, he/she should always use the same kind of image.
Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5.
Cheers, Juraj
-- www.tudorgirba.com "Every thing has its own flow"
16. 3. 2015 v 13:23, Sven Van Caekenberghe <sven@stfx.eu>:
On 16 Mar 2015, at 17:11, Juraj Kubelka <juraj.kubelka@gmail.com> wrote:
Hi,
I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy.
Yes, that is why I never use this export feature, it is broken by design, for me.
Well, Spotter is potentially the first use case where people likely want to persist the setting about âsend usage dataâ. Otherwise it will ask in every new image.
An image is a persistent world which can hold its own settings.
I can imagine some people want some automatic loading in each new image, but that should be opt-in.
Automatic loading is on by default. Cheers, Juraj
If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post.
Technically speaking once someone exports preferences, he/she should always use the same kind of image.
Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5.
Cheers, Juraj
participants (3)
-
Juraj Kubelka -
Sven Van Caekenberghe -
Tudor Girba