Dealing with Preferences in external packages?

> Now that setting is starting to get integrated (great) we will also face
> the problem
> of branching.
> For example, how do we manage that OB uses Preferences.... and that we
> don't.
> Any idea or process is welcome.
>
> Of course we can have a package full of override but this is the ultimate
> solution
> before complete fork.
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 

> Now that setting is starting to get integrated (great) we will also face the problem
> of branching.
>        For example, how do we manage that OB uses Preferences.... and that we don't.
>        Any idea or process is welcome.
>
> Of course we can have a package full of override but this is the ultimate solution
>        before complete fork.
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> That's a serious problem, but given that OmniBrowser is pretty modular
> I guess that the preferences can be factored out into an
> OBPharoPlatform.
>
> Lukas
>
> 2009/12/7 Stéphane Ducasse <[hidden email]>:
>> Now that setting is starting to get integrated (great) we will also face the problem
>> of branching.
>>        For example, how do we manage that OB uses Preferences.... and that we don't.
>>        Any idea or process is welcome.
>>
>> Of course we can have a package full of override but this is the ultimate solution
>>        before complete fork.
>>
>> Stef
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> "Shared" settings will introduce another kind of package dependency...
> Perhaps
> there is some benefit of all settings being local to a package but
> cross-linked in some way such
> that the compatible preferences all change value at the same time in the
> settings browsers?
>
> There will always be some kind of compromise, one way or the other, but it
> might work ;-)
>
> Regards, Gary
>
> ----- Original Message -----
> From: "Stéphane Ducasse" <[hidden email]>
> To: <[hidden email]>
> Sent: Monday, December 07, 2009 1:50 PM
> Subject: [Pharo-project] Dealing with Preferences in external packages?
>
>
>> Now that setting is starting to get integrated (great) we will also face
>> the problem
>> of branching.
>> For example, how do we manage that OB uses Preferences.... and that we
>> don't.
>> Any idea or process is welcome.
>>
>> Of course we can have a package full of override but this is the ultimate
>> solution
>> before complete fork.
>>
>> Stef
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> "Shared" settings will introduce another kind of package dependency...
> Perhaps
> there is some benefit of all settings being local to a package but
> cross-linked in some way such
> that the compatible preferences all change value at the same time in the
> settings browsers?
>
> There will always be some kind of compromise, one way or the other, but it
> might work ;-)
>
> Regards, Gary
>
> ----- Original Message -----
> From: "Stéphane Ducasse" <[hidden email]>
> To: <[hidden email]>
> Sent: Monday, December 07, 2009 1:50 PM
> Subject: [Pharo-project] Dealing with Preferences in external packages?
>
>
>> Now that setting is starting to get integrated (great) we will also face
>> the problem
>> of branching.
>> For example, how do we manage that OB uses Preferences.... and that we
>> don't.
>> Any idea or process is welcome.
>>
>> Of course we can have a package full of override but this is the ultimate
>> solution
>> before complete fork.
>>
>> Stef
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project