On Tue, May 11, 2010 at 3:44 PM, Alain Plantec <[email protected]>wrote:

> Le 11/05/2010 15:22, Alain Plantec a écrit :
>
>> Le 11/05/2010 14:13, Mariano Martinez Peck a écrit :
>>
>>>
>>>
>>>
>>>
>>> But maybe the default value in the "PharoCore" is not the same as
>>> PharoDev?  I mean, suppose these are the default prefrences we used in the
>>> pharo dev image
>>>
>> ok, there is only one default.
>> For this need, you should have to create a setting style for pharodev and
>> load it.
>>
> I've re-thougth about this and maybe building a style class and let it in
> the dev image  is a bad solution
> because then, the style class depends on all other packages. This is
> exactly what we wanted to avoid by
> introducing the settings.
> So, maybe the default state for the preferences in the dev should be the
> one of the core
> plus the state decided by maintainers for additional packages.


Ok...but how can I do the following: there is a setting that in Core has XXX
value and I want to change it for the Dev image. Creating whole Style
doesn't make sense as I only want to change one setting. In addition,
happens what you told me in this mail, and finally it is difficult to manage
I think: imagine today I create a Style and tomorrow you create ore
settings...do I need to update my style to contemplate such setting ?

Actually, I want to change two things: FastDragging (to true) and "Show
update option in World menu" (to false).

So, how can I do that ?

Thanks

Mariano



>
>
> Alain
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to