* The DARApplier and associated names
How about ChangeGuard and that.changeGuard or ModelGuard and
that.modelGuard?
Well.... guarding is just one of its several functions. So far the
full civilization of listeners it supports are
i) guards which can react "early" to incoming changes to the model,
validate or reject them
ii) (not yet implemented) "transactional" reactors which can look at
a fully assembled "new state" to the model, and still have the ability
to back out the transaction as a whole (only at greater cost than
rejecting it at stage i)
iii) model changed listeners, which notify interested parties about
which pieces of data are now "dirty" due to change etc. so they may
update their own state (whether in other models, or in a UI, etc.)
To me, it automates the complete lifecycle process of "applying"
a change to the model...
ModelManager?
* DataBinding.js: fluid.assembleSuperModel()
This automates the work both of assembling many smaller models into
a combined model, but at the same time assembling their sub-appliers
into a super-applier, which will route incoming change requests to
the "leaf appliers".
Maybe fluid.assembleCombinedModel() ?
fluid.assembleCombinedManagedModel() ? :-)
* 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...
* 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.
--
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
