AppCLI is more general than just being a tool for command-line apps, and it bothers me that the name doesn't reflect that. I think the name should reflect some/all of the following:
Multiple locations are searched for parameter values.
Parameters can be thought of as sophisticated default values.
Repeatedly try until success.
Heterogenous location types.
Some ideas:
~stackable~
Too reminiscent of "stack" in the web development sense.
~findit~
search
query
quest
switch
multiparam
menu
pchoice
the "p" is short for "parameter"
pswitch
attrichoose
get123
getwhere
octoattr
polyattr
oligoattr
pluribus
onion
~parfait~
~cake~
~layercake~
baklava
strata
meso
~default~
plattr: "plural attr"
cfg (surprised this is available...)
anycfg
anysrc
byocfg
byoc
canfig
~default~
~dfault~
cdefault
confault
smartdefault
iqdefault
fancydefault
gofind
~meltingpot~
~lineup~
I don't want to have "param" in the name, because *param*.param is redundant. Maybe I could just change the convention to from *param* import param, Key, ..., though...
I like the term "default", since I'm more and more thinking of the role of the library as being to provide very fancy default values. Unfotunately the obvious variants of this term are taken. cdefault (for config-default) is one of my favorite choices so far...
I like "gofind" too; it does a good job communicating the "multiple locations are searched for parameter values" criterion from above...
AppCLI is more general than just being a tool for command-line apps, and it bothers me that the name doesn't reflect that. I think the name should reflect some/all of the following:
Some ideas:
I don't want to have "param" in the name, because
*param*.param
is redundant. Maybe I could just change the convention tofrom *param* import param, Key, ...
, though...I like the term "default", since I'm more and more thinking of the role of the library as being to provide very fancy default values. Unfotunately the obvious variants of this term are taken.
cdefault
(for config-default) is one of my favorite choices so far...I like "gofind" too; it does a good job communicating the "multiple locations are searched for parameter values" criterion from above...