Hey, Antranig,
I'm just going over the fluid.initRendererComponent() and its options, and I
wanted to double-check whether or not any of the options would fall into the
"unsupported" class.
Below, I've listed the options I've found so far. Would any of these be
considered "unsupported" i.e. we don't really want users to know about them?
There seem to be "repeated" options - top level options that re-appear inside
options blocks that get passed down (e.g. model) - are these things that the
user should be instructed to provide at the top level, but NOT at the lower
levels (i.e. the framework will take care of propagating it down)?
model
resources
resolverGetConfig
resolverSetConfig
rendererOptions
model <would this be the same as above?>
applier
autoBind
document
debugMode
idMap
messageLocator
messageSource
renderRaw
cutpoints
rendererFnOptions
cutpointGenerator
expanderOptions
ELStyle
IDescape
model <same as above?>
resolverGetConfig <same as above?>
resolverSetConfig <same as above?>
noexpand
rendererOptions
<would these be the same as above?>
templateSource
rendererTargetSelector
selectors
repeatingSelectors
selectorsToIgnore
strings
messageResolverFunction
parentBundle
protoTree
produceTree
--
Anastasia Cheetham Inclusive Design Research Centre
[email protected] Inclusive Design Institute
OCAD University
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
