ParameterMgrPlatformConnectorThis class is the main client interface.
See http://01org.github.io/parameter-framework/doc/classCParameterMgrPlatformConnector.html for the complete documentation of each API.
createSelectionCriterionType and createSelectionCriterionImplement the Selection Criterion creation requirements. See section 5.4 of the requirements documentation.
getSelectionCriterionThere is no requirement to retreive a criterion by it's name.
setLoggerImplement [req-post-mortem-debug].
Implements a way for the user to provide a log backend. This is not a requirentment currently. Maybe it is a miss?
start and isStarted???
There is no “two-step-creation” requirement. This is an implementation detail.
applyConfigurationsDeffered application requirement; see [req-multiple-criterion-change-atomicity] See also the Selection Criterion APIs below.
createParameterHandleIntrospection and direct parameter read/write access; see [req-introspection] especialy the point about parameter properties. See also the Parameter Handle APIs below.
setForceNoRemoteInterface and getForceNoRemoteInterfaceTuning capability activation control; see section [req-disabling] in [req-tuning].
setFailureOnMissingSubsystem and getFailureOnMissingSubsystem???
Currently only used for XML generation. There is no requirement associated.
setFailureOnFailedSettingsLoad and getFailureOnFailedSettingsLoad???
Currently only used for XML generaton. There is no requirement associated.
setSchemaUri and getSchemaUri; setValidateSchemasOnStart and getValidateSchemasOnStart???
Currently only used for XML generation. There is no requirement associated.
ParameterMgrFullConnectorThis is another client interface that covers the same purposes and APIs than ParameterMgrPlatformConnector and extands them. See this class' description. Added APIs are described in this chapter.
setTuningMode and isTuningModeOnTuning capability activation control; see section [req-parameter-overwriting]. It adds another level of flexibility over setForceNoRemoteInterface. The semantic of these two APIs overlap but neither one fully contains the other.
TODO: fix the semantics.
setValueSpace and isValueSpaceRaw; setOutputRawFormat and isOutputRawFormatHexSerialization control (FIXME: what about deserialization ?). Seems UNUSED. There is no requirement associated.
setAutoSync, isAutoSyncOn and syncSynchronization on client request; see section [req-explicit-sync].
accessParameterValueParameter value direct access. This overlaps with ParameterHandle. Implements the same requirement: [req-parameter-overwriting]
getParameterMappingPart of the Introspection requirements. See [req-introspection] especialy implement intropsepction of the mapped syncer.
All of the following APIs implement the Tuning requirement; see section [req-tuning]
accessConfigurationValue
createDomain
deleteDomain
renameDomain
deleteAllDomains
setSequenceAwareness
getSequenceAwareness
setElementSequence
createConfiguration
deleteConfiguration
renameConfiguration
restoreConfiguration
saveConfiguration
addConfigurableElementToDomain
removeConfigurableElementFromDomain
split
setApplicationRule
getApplicationRule
clearApplicationRule
exportDomainsXmlExports the “Domains” (aka “Settings”) which is the inference engine's data. See section [req-serializable].
importDomainsXmlImports previously-exported data into the inference engine. See [req-deserializable].
exportSingleDomainXmlExports a given part of the inference engine data. See [Serialization of individual data].
importSingleDomainXmlImports a partial inference engine data as previously exported. See section [req-deserialization-of-individual-data].
ISelectionCriterionTypeInterfaceImplementation detail of the criterion requirement [req-selection-criterion].
addValuePairImplementation of [req-criterion-changes].
getNumericalValueImplementation of [req-criterion-changes].
getLiteralValueImplementation of [req-criterion-changes].
isTypeInclusiveGet how the criterion possible states were specified, see [req-state-domain-specification]
getFormattedStatePretty print criterion state [req-pretty-print]
ISelectionCriterionInterfacesetCriterionState and getCriterionStateAllow Introspection of a criterion; see [req-introspection].
getCriterionNameAllow Introspection of a criterion; see [req-introspection].
getCriterionTypeAllow Introspection of a criterion; see [req-introspection].
CParameterHandleThis class implements the requirements related to direct read/write access to parameters.
isRogueRelative to setting rogue parameters; see section [req-introspection].
isArrayAllow Introspection of a parameter metadata; see [req-introspection].
getArrayLengthAllow Introspection of a parameter metadata; see [req-introspection].
getPath and getKindAllow Introspection of a parameter identifier; see [req-introspection].
The following APIs allow reading/writing parameters. Implements [req-introspection] and [req-parameter-overwriting]
setAsBooleangetAsBooleansetAsBooleanArraygetAsBooleanArraysetAsIntegergetAsIntegersetAsIntegerArraygetAsIntegerArraysetAsSignedIntegergetAsSignedIntegersetAsSignedIntegerArraygetAsSignedIntegerArraysetAsDoublegetAsDoublesetAsDoubleArraygetAsDoubleArraysetAsStringgetAsStringsetAsStringArraygetAsStringArray