Need customization so that specific Settings can apply only to *self sets.

 

 

Gerry's proposal:

 

Need a trait pattern, so that <foo>+<tagname> is a pattern that can be applied to any card, possibly limited by another setting to some subset of all cards.

 

In pattern lookups, this is a special pattern key, or rather it is patterns without a key, so there will be a global list of traits that a module can add their trait-name to.  The trait name is either a special Setting card or a similar type, most likely they will all need codenames for necessary code supports.  In module lookups, each trait may include methods and overrides, so the registered order will matter or we will need another config to give them a priority.

 

to clarify:

*account is a...trait setting?

Gerry+*account is a... trait rule?

 

and if we just say "trait", we mean....?  Perhaps a "trait" itself is not a card, but just, well a trait.  Gerry has the trait of having an account.

 

if there are methods and overrides, how do they fit in to the set hierarchy?  What does that api look like?