Well it's an interface between a user and the system, even if it's in a config file. In that sense it's a UI component. Not all user interfaces are graphical.<br><br>OTOH, that doesn't mean that a preferences mechanism isn't core in some way. Even the most basic loader will need some way of indicating its preferred data sources, etc.<br>
<br><div class="gmail_quote">On Fri, Mar 6, 2009 at 9:46 AM, Gary Chambers <span dir="ltr"><<a href="mailto:gazzaguru2@btinternet.com">gazzaguru2@btinternet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">----- Original Message ----- <br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Alain -<br>
<br>
To me there is a big difference: From my perspective all preferences code is UI code. Why? Because at the system level we use class variables and messages, not preferences. At the system level if you want to broadcast an event you use announcements or some other event system.<br>
<br>
</blockquote>
<br></div>
I disagree that preferences "as a concept" are UI level (in terms of graphical and/or point and click).<br>
It is quite valid that a preference exists for use with or without a user means of setting/changing.<br>
<br>
Regards, Gary. <br>
<br>
</blockquote></div><br>