<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="4">Hi Luciano,<br>
</font></p>
<p><font size="4">ok got it. I think I was confused with the name
PreferenceDictionary and my recent errant involvment. What about
a name among :<br>
</font></p>
<ul>
<li><font size="4">PreferenceDomain</font></li>
<li><font size="4">PreferenceApp</font></li>
<li><font size="4">PreferenceSet<br>
</font></li>
<li><font size="4">other idea?</font></li>
</ul>
<p>I will work on some design with two classes<br>
</p>
<p>Hilaire<br>
</p>
<div class="moz-cite-prefix">Le 21/06/2022 à 19:32, Luciano
Notarfrancesco via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAL5GDyqjMnMV7dH-Dr2=qAAGaoAdet=oHUtDic_+iwx3N8B9Ww@mail.gmail.com">
<div dir="auto">Hi Hilaire,</div>
<div dir="auto">I’m not sure if we should rename PreferenceNG to
PrefernceDictionary, or if it’s best to keep it. If you get rid
of the PrefernceNG class you’d have to implement
PreferenceDictionary with multiple instance variables with
dictionaries to hold preference types, names, values and
categories, or a single dictionary with arrays {name. type.
category. value}, etc… there are several possibilities for the
implementation if you do this. On the other hand, if you keep
PreferenceNG and create a new class PreferenceDictionary, the
PreferenceDictionary can have a single instance variable (say
‘contents’ for example) with a dictionary name ->
aPreferenceNG, and you would only need to move the class-side
methods from PreferenceNG to the instance side of
PreferenceDictionary.</div>
<div><br>
</div>
</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>