Page History

• flesh out to give more explanation

• update code samples to latest form

• remove anything without 'autoInit'  

  Jira
  server Fluid Project Issue Tracker key FLUID-5152

• remove mention of lifecycle functions

  Jira
  server Fluid Project Issue Tracker key FLUID-5140

• remove mention of initDependents

  Jira
  server Fluid Project Issue Tracker key FLUID-5141

Remove mention of demands 

We've decided that demands blocks will no longer be used or recommended, so we will remove references to them altogether. They should be replaced with either the use of distributeOptions, or with a grade that overrides things.

• Demands Specifications
• Demand Resolution

The two pages have been removed. The rest of the docs still need to be reviewed.

Invokers        

Justin,

Antranig to review

Component Grade page Component Grades    

- and then cover dynamic grades, both supplied via direct options as well as those resolved
via an IoC reference in the "gradeNames" list - explain the limitations on this latter process
and how it must be used carefully.

dynamic grades and grade merging
   ability to write an ioc expression where a grade name is expected

See

 Model Transformation   

Some docs exist in the GPII wiki:
http://wiki.gpii.net/index.php/Architecture_-_Available_transformation_functions

• Subcomponent Declaration and dynamic components

• Jira
  server Fluid Project Issue Tracker key FLUID-5238

• Contexts   

  Jira
  server Fluid Project Issue Tracker key FLUID-5149

  • diagram from demand resolution page, plus some explanation

• Pseudoarguments
  • "a demands block which uses named arguments such as "options", "container", etc. rather than an argument list"

Message loading: We need an overview page describing how to work with message files/string bundles, for localization, including

• in renderer components
• using the message resolver (fluid.messageResolver) in non-renderer-component scenarios

• Update the scenarios, use to identify "paths through the docs"

Overview of preference editor framework
    what it's for
    what it is
    how it's structured/architected
    what is a preferences editor

How is prefs config different from IoC config
    how does it build upon it
    spine of lookup onto names

GPII preferences server as a crucial element of the system
    for schema users
    a central place where 'all' prefs are defined/stored
    stress the fact that the gpii prefs server is not required (even though right now it is required)

Justin,

Antranig to review

Please paste a link here to where the docs have been started!

see FLUID-4258 for info

Declarative Syntax for Binding ChangeApplier Events