<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Mariano & al, Okay I incompletely read and understood your suggestion. It looks like this is a good way to go and I like the idea too :) To sum up, the ideas (correct when wrong): <ul> <li>Add a 'prefrerenceType' or just 'type' instance variable to the Preference class. It can be a symbol or reference to a class (String, Boolean) or instance ({'foo'. 'bar'.'baz'}, (Interval from: 0 to: 100))</li> <li>Purge the Preferences class side methods </li> <li>Use a dictionary like protocol to access the preference instances and its value </li> <li>Make Preferences instance side defined, so we can have load/save features</li> </ul> That's for the basic that should go in Cuis. Complete with the missing point. Hilaire <div class="moz-cite-prefix">Le 28/04/2022 à 15:24, Mariano Montone via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:150660fa-c9cc-349d-c6ac-fde38080644c@gmail.com">What I'm proposing is no hierarchy at all. Neither for Preference or PreferenceType. I'm proposing adding a 'preferenceType' instance variable to Preference, and bind that to Smalltalk classes, like Boolean, String, Integer, Color. Or instances of Array for list of options. Or something else that can be handled by some tool. Then it is up to the tools then to use that information for building widgets the way they like. </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre> </body> </html>