Ferreteria/v0.5/feature

the Features system

A "Feature", in this context, is a set of classes which work together to handle a particular type of data, traditionally represented by a table in a database. The class-set for each Feature is primarily organized around a descendent (subclass) of the Feature class.

Each Feature subclass represents a singleton object and has:

• a SpecSlug() for identifying its table specs in the config data
• an ActionKey() for being identified as the object to handle URL data

Related

• The table registry involves both tables and table specs.

Notes

I'm still trying to figure out how this needs to work. There are currently Table Specs and registration of Features. A Feature doesn't know about Tables per se; it only knows about its Storage Row, and the Storage Row may use a Table (thought it doesn't have to; the Dropin-viewer Dropin just uses an in-memory array).

Table specs are used/required by Card objects.