[Cuis-dev] The Preference model

[Luciano Notarfrancesco]

Good idea. Then a package that implements a tool to browse and edit
preferences could implement methods in Boolean class, Integer class,
Interval, etc, and delegate to the preference type the building of the
corresponding GUI components.

On Wed, 27 Apr 2022 at 10:01 PM Mariano Montone via Cuis-dev <
cuis-dev at lists.cuis.st> wrote:

> El 27/4/22 a las 11:50, Hilaire Fernandes via Cuis-dev escribió:
>
> We can have the minimum Preference model matching the use cases in the
> image. Then an external package with Preference extension or Application
> extending themself the Preference model.
>
> Yes. What I think I would do, though, is add a preferenceType instance
> variable to Preference. Then perhaps having a package PreferenceTypes, or
> something, that applications, tools and a PreferenceBrowser can use.
>
>
> Also I'm thinking about this: what if instead of having a PreferenceTypes
> hirarchy, we use as preference type already existing classes and objects in
> Cuis ?
>
> For example:
>
> myPreference preferenceType: String.
>
> myPreference preferenceType: Boolean.
>
>
> Or, for list of options:
>
> myPreference preferenceType: {'foo'. 'bar'.'baz'}.
>
>
> Or, for intervals:
>
> myPreference preferenceType: (Interval from: 0 to: 100).
>
>
> Mariano
> --
> 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/20220427/e660e439/attachment-0001.htm>