<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">El 28/4/22 a las 14:31, Hilaire Fernandes via Cuis-dev escribió: </div> <blockquote type="cite" cite="mid:713e0453-e32e-f13e-7398-4a7373735a22@drgeo.eu"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 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. </blockquote> Hi Hilaire, yes, I agree with that list :D One thought: what if instead of purging the Preferences class side methods, we keep them, but make them access the new Preferences singleton object, and we can have backwards compatibility. Mariano </body> </html>