<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="4">Ok let's go for it. In the end we will have done a
perfect circle, with two classes to handle the preferences, but
with a slightly better implementation. This is for the better.<br>
</font></p>
<p><font size="4">I will have to contribute changeset to revert the
use of the PreferenceNG and but back the use of the global
variable Preferences</font></p>
<p><font size="4">But after that, application will have their own
space for preferences, as for example the possible global
variable DrGeoPreferences you mentioned. Not sure I will turn it
as a global though.<br>
</font></p>
<p><font size="4"></font>Hilaire<br>
</p>
<div class="moz-cite-prefix">Le 22/06/2022 à 20:54, Luciano
Notarfrancesco a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAL5GDyq=0HaNum5kEM3GxXsdpeu7dme1b1kpuhTFck3s0R8xCA@mail.gmail.com">
<div dir="auto">PreferenceSet sounds good to me, I thought about
that name too. For the global I would use Preferences because
it’s the same name we were using before and seems to make most
sense, but instead of being a class it would now be an instance
of PreferenceSet. For DrGeo I guess you could use a global like
DrGeoPreferences, right?</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>