<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">El 27/4/22 a las 11:50, Hilaire Fernandes via Cuis-dev escribió: </div> <blockquote type="cite" cite="mid:2c6b96f9-886b-9b76-b2ff-5a23bab6d259@drgeo.eu"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 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. </blockquote> 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 </body> </html>