I don't think so. You have a file with some bytes in it that can do  
things. The configuration of those things is conceptually separate.

Steve

On 6 Mar 2009, at 10:17, "Gary Chambers" <gazzaguru2 at btinternet.com>  
wrote:

> Of course, from that perspective, all code is UI... :-)
>
> Regards, Gary
> ----- Original Message -----
> From: Steve Wart
> To: The general-purpose Squeak developers list
> Sent: Friday, March 06, 2009 6:09 PM
> Subject: Re: [squeak-dev] Re: [ANN] Preference pragmas
>
> 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.
>
> 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.
>
> On Fri, Mar 6, 2009 at 9:46 AM, Gary Chambers <gazzaguru2 at btinternet.com 
> > wrote:
> ----- Original Message -----
> Hi Alain -
>
> 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.
>
>
> I disagree that preferences "as a      concept" are UI level (in  
> terms of graphical and/or point and click).
> It is quite valid that a preference exists for use with or without a  
> user means of setting/changing.
>
> Regards, Gary.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090306/360de83c/attachment.htm