* The DARApplier and associated names
The DARApplier is the newest part of our framework. As model layer
infrastrcture, the DARApplier allows components to make requests to
the framework for changes in the model. It provides a scheme for
validation routines to be plugged into this change request pipeline,
and for change events to be fired as a result of successful updates
to the model.
* 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.
* DataBinding.js: fluid.assembleSuperModel()
This one is a bit confusing. I'm not sure how and when I'd use it,
and some in the community has said it reminds them of nerds in their
basement. Enough said.
* 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?
* Uploader.js: fileQueueView.repairFromUpload()
This is part of the Uploader's file queue view, and is called after
the upload completes. I've never quite understood what it does from
the name.
Other things we might rename:
* DataBinding.js: fluid.bindFossils()
I'm not sure most people understand the use of the word "fossil" in
this context. The use and usefulness of the function might be better
served by a different name for fossils.
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
