til_settings: label til_settings_t instances

This adds a mandatory label string to til_setttings_new() and
updates call sites accordingly.

For now the root-level settings created by main.c are simply
named "module" and "video" respectively.  Any nested settings
creations on behalf of modules will be labeled using the module's
name the settings are being created for use with.

This might evolve with time, for now it's just a minimum churn
kind of decision.  I can see it changing such that the top-level
settings also become labeled by the module/video driver name
rather than the obtuse "module" "video" strings.

How these will be leveraged is unclear presently.  At the least
it'll be nice to have a label for debugging til_settings_t
heirarchies once recursive settings support lands.  In a sense
this is a preparatory commit for that work.  But I could see the
labels ending up in serialization contents as markup/syntactic
sugar just to self-document things as well.

There might also be a need to address til_settings_t instances in
the settings heirarchy, which may be something like a
"label/label/label/label" path style thing - though there'd be a
need to deal with name collisions in that approach.

I'm just thinking a bit about how knobs will become addressed
when those become a real thing.  The settings label heirarchy
might be the convenient place to name everything in a tree, which
knobs could then inherit their parent paths from under which
their respective knob labels will reside.  For the whole name
collision issue there could just be some builtin settings keys
for overriding the automatic module name labeling, something
like:

--module=compose,layers=checkers\,label=first\,fill_module=shapes:checkers\,label=second\,fill_module=shapes

would result in:
/module/first/shapes
/module/second/shapes

or in a world where the root settings weren't just named "module"
and "video":
/compose/first/shapes
/compose/second/shapes

then if there were knobs under checkers and shapes, say checkers
had a "foo" knob and checkers had a "bar" knob, they'd be under
.knobs in each directory:

/compose/first/.knobs/foo
/compose/first/shapes/.knobs/bar
/compose/second/.knobs/foo
/compose/second/shapes/.knobs/bar

something along those lines, and of course if compose had knobs
they'd be under /compose/.knobs

This is just a brain dump and will surely all change before
implemented.

0 files changed, 0 insertions, 0 deletions