Naming TransformAble2

[John Norman]

I have dropped out of the conversation on the basis that this is not a  
user-facing issue. As I understand matters this is a web-developer  
facing issue. The transformable component will be used in some page  
and the page can be named anything the web developer likes. It may  
well contain other preference settings for the application, but  
doesn't have to. So the main thing is to name it in such a way that a  
web-developer would have a reasonable understanding of what the  
component would do for her/him.

John

On 7 Oct 2008, at 01:10, Gary Thompson wrote:

> The name for "TransformAble2" as a Fluid component.
>
> Gary
>
> Michael S Elledge wrote:
>> I'm a little confused. Are we talking about the name for  
>> Transformable as a
>> widget, or the link that would appear on a web page?
>>
>> Mike
>>
>> Daphne Ogle writes:
>>
>>
>>> +1 for "User Interface Options" or  "User Interface Preferences"
>>>
>>> I was going to respond with only the latter but Anastasia's comment
>>> convinced me that brevity and ease of rolling off the tongue are
>>> pretty important too.  I like preferences because it is more  
>>> personal
>>> and we want to transform the interface to the user's personal needs.
>>>
>>> -Daphne
>>>
>>> On Oct 3, 2008, at 1:25 PM, Anastasia Cheetham wrote:
>>>
>>>
>>>>> Interface Options
>>>>> Interface Preferences
>>>>> User Interface Options
>>>>> User Interface Preferences
>>>>> Personal Interface Options
>>>>> Personal Interface Preferences
>>>>>
>>>>>
>>>> +1 for "User Interface Options"
>>>>
>>>> Interface alone, without anything in front of it, sounds more
>>>> technical than user interface, which is a very commonly used  
>>>> phrase.
>>>> User interface rolls off the tongue more easily than 'personal
>>>> interface', and 'options' rolls more easily than 'preferences'
>>>>
>>>> My second choice would be Interface Options, for simplicity and
>>>> brevity.
>>>>
>>>> -- 
>>>> Anastasia Cheetham                   a.cheetham at utoronto.ca
>>>> Software Designer, Fluid Project    http://fluidproject.org
>>>> Adaptive Technology Resource Centre / University of Toronto
>>>>
>>>> _______________________________________________
>>>> fluid-work mailing list
>>>> fluid-work at fluidproject.org
>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>
>>> Daphne Ogle
>>> Senior Interaction Designer
>>> University of California, Berkeley
>>> Educational Technology Services
>>> daphne at media.berkeley.edu
>>> cell (510)847-0308
>>>
>>>
>>>
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>>
>>
>>
>>
>> Mike Elledge
>> Assistant Director
>> Usability & Accessibility Center
>> Michigan State University
>> 517-353-8977
>>
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work