[Cuis-dev] The Preference model

Luciano Notarfrancesco luchiano at gmail.com
Sat Apr 30 06:39:06 PDT 2022


Hi Hilario,
Great! Maybe I would rename #of: to something more self evident like
#valueAt: for example, but not sure, we should think carefully because
that’s the message that will be called the most fro the rest of the system.
Other than that on a first glance looks perfect to me!

On Sat, 30 Apr 2022 at 8:28 PM Hilaire Fernandes via Cuis-dev <
cuis-dev at lists.cuis.st> wrote:

> A first implementation following the ideas exchanged there.
>
> It is a one class approach (hi Ken), with an additional type attribute (hi
> Mariano), without defaultValue attribute, it is not used in the base system
>
> It is possible to reset to Cuis base preferences, or to import the
> existing Preferences from the old system, but the type is not good, so only
> for testing.
>
> A preference is created and auto-kept when instantiating it.
>
> Access to Preference instance as dictionary: PreferenceNG at: #
> biggerCursors. Access to preference value PreferenceNG at: #biggerCursors
> or message send PreferenceNG biggerCursors
>
> Things to do, conform the value change to the type when type is not a
> class. Third party editor level right?
>
> Each occurrence in system of Preferences biggerCursors should be replaced
> by PreferenceNG biggerCursors (to become just Preference or even
> Preference*s*). Message send goes by a DNU so may be system use should be PreferenceNG
> of: #biggerCursors
>
> Hilaire
>
> --
> GNU Dr. Geohttp://drgeo.euhttp://blog.drgeo.eu
>
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20220430/19ac6029/attachment-0001.htm>


More information about the Cuis-dev mailing list