API name change ideas for Infusion 1.0

[Colin Clark]

Hey,

On 31-Mar-09, at 11:10 AM, Anastasia Cheetham wrote:
>> To me, it automates the complete lifecycle process of "applying"
>> a change to the model...
>
> ModelManager?

I've always been wary of giving code a vague name like "Manager." It  
tends to point to a design where the identity of the object is poorly  
defined, and inevitably accumulates various bits of cross-cutting  
logic. The DARApplier is pretty tightly defined, though it is abstract  
in real-world terms.

The best metaphor we've come up with so far for the DARApplier is as a  
personal assistant. Imagine the model as a busy executive who needs  
help in handling requests from people (the views). The DARApplier  
fields requests for changes to the model, consults others who can help  
make a decision, and if approved, the request is passed on to the  
model itself.

This metaphor is a bit of a stretch, and doesn't help me much with  
naming ideas, but perhaps it will be useful to everyone else.

Having been the author of several poorly named things called  
"Managers," I'm hesitant to add another to our framework. That said,  
these are such abstract things. Riffing off your suggestion, I also  
seem to come up with equally generic names:

ModelHelper
ModelChanger
ModelCenter
ModelHub

I don't really like any of these much.

>> * Fluid.js: fluid.findKeyInObject()
>> This is a framework utility that performs reverse lookups in an  
>> object: pass in a value, and you'll get its associated key. This  
>> name always confuses me about the order and nature of the arguments.
>
> Sounds like it might be better named fluid.findKeyForValue() ? The  
> required parameters include the value and the object to search in...  
> findKeyForValueInObject() is getting a bit annoyingly long...

This awful name was entirely my doing... a late night change on the  
eve of Infusion 0.5. :(

I'm cool with fluid.findKeyForValue(). If people are worried about  
verbosity, how about fluid.keyForValue()?

>>> * UIEnhancer
>
>>> UIEnhancer is the companion to UI Options, and is the component  
>>> responsible for actually transforming the page based on user  
>>> preferences. I like the name, but I wonder if it will be confused  
>>> with the concept of Progressive Enhancement. We'll likely add  
>>> framework-level support for progressively enhancing components in  
>>> a future release. Maybe UITransfomer instead?
>>>
>> Naming this one has been hard! So far it has been called StyleAble,  
>> Skin and UIEnhancer. I'm happy to rename again - we hadn't thought  
>> of the confusion with Progressive Enhancement during the last  
>> naming discussion. I like UITransformer - it was the runner up  
>> during the last conversation which you can see in the channel logs  
>> starting at 16:01:
>> http://wiki.fluidproject.org/display/fluid/fluid-work+IRC+Logs-2009-02-26
>
> Well, cars that turn into robots comes to mind, but other than that,  
> I'd be ok with UITransformer.


Well, this is one we don't necessarily have to rename. Do others think  
that there could be a risk that people will confuse the UIEnhancer  
with support for progressive enhancement?

Or, alternatives to UITransformer? Yes, it's geeky.

Colin

---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org