Naming TransformAble2

[Michelle D'Souza]

John's correct, however it's also a Fluid community issue. The problem  
that we came across with our other naming issues was one of  
communication. If the developers call something 'module layout' and  
the designers call it 'layout customizer' and the integrators call it  
'layout reorderer' we eventually realize that we are all talking about  
the same thing but it's better if we can speak the same language. This  
also means that API docs, tutorials and design docs will use the same  
language thereby tying all the bits of a component together.

I actually care little about what we name things as long as it's clear  
and consistent. My preference is always for short names since I'm  
afflicted with the common programmer trait of typing laziness. :)

Michelle


On 7-Oct-08, at 5:21 AM, John Norman wrote:

> 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
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto