<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="4">Hi Gerald,</font><br>
</p>
<div class="moz-cite-prefix">Le 28/04/2022 à 09:18, Gerald Klix a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:75b54634-5573-9115-473d-ddc76733d7f8@klix.ch">
<pre class="moz-quote-pre" wrap="">1. Move the class-side code in Preferences to the instance-side by using
a preferences singleton. This way we can easily change a whole set of
preferences, maybe loading from disk.</pre>
</blockquote>
<p>That is something needed for application use.
</p>
<blockquote type="cite"
cite="mid:75b54634-5573-9115-473d-ddc76733d7f8@klix.ch">
<pre class="moz-quote-pre" wrap="">2. If you add some meta/type-information, do this in a general manner.
There are obvious other uses for such a system.
Not so important:
3. Make the type/meta information optional eg. a package.
There is little use of having the meta information in the image,
once you have a set of working personal preferences.
If you use Cuis to implement daemons, you probably set some preferences
with a script and don't need a type system.</pre>
</blockquote>
<p>In that case, with only one Preference class defined, one type
attribute as Mariano mentioned from Squeak. IT could be a symbol
or am optional PreferenceType instance.<br>
</p>
<p>Hilaire<br>
</p>
<p>
</p>
<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>