2014.09.13 Programmer's Notes

In order to implement the Picker population properly, I'm going to have to add a new
attribute to the Relation specifications of a BAM.  I'll add an optional PickerPopRelation
attribute to them, which references a Relation (one of Components, Children, or Details.)

When you specify a PickerPopRelation, the code will search through the object
runtime hierarchy for an instance of PickerPopRelation.FromTable.  When it finds
such an instance, it will cast it accordingly, and invoke the member attribute
accessor for the relationship.

If no PickerPopRelation is specified and the target of the relationship
has no container defined, then the global set of target objects will be used
for the population.  Otherwise, if the container of the target objects is a
Tenant or Cluster, the appropriate security object will be used to filter
the population set.

Note that for now I'm not planning to support Add methods in the picker windows.
There are a lot of complications to doing so, and I wouldn't *always* want you
to be able to add an object without going to it's container.  I may someday
implement yet another flag, say PickerAllowsAdd to enable such functionality
on a per-relationship basis, if I ever work out the kinks to doing so.