okay, will get some light mechanism in place


On Tue, Aug 6, 2013 at 10:44 AM, Jai Ram Rideout
<notifications@github.com>wrote:

> In pyqi/interfaces/optparse/config/make_optparse.py:
>
> > +from pyqi.commands.make_optparse import CommandConstructor
> > +
> > +# Examples of how the command can be used from the command line
> > +usage_examples = [
> > +    OptparseUsageExample(ShortDesc="Fill in an Optparse config template",
> > +                         LongDesc="Construct the beginning of an Optparse configuration file based on the Parameters required by the Command",
> > +                         Ex="%prog -c pyqi.commands.make_optparse.MakeOptparse -m pyqi.commands.make_optparse -o pyqi/interfaces/optparse/config/make_optparse.py")
> > +    ]
> > +
> > +# Inputs map command line arguments and values onto Parameters. It is possible to
> > +# define options here that do not exist as parameters, e.g., an output file
> > +inputs = [
> > +    # An example option that has a direct relationship with a Parameter
> > +    #OptparseOption(InputType=str, # can be non-primitive, handled by InputHandler
> > +### do we want to define a helper method, get_param = lambda x: CommandConstructor.Parameters[x]
> > +### and drop it in each config file via the template?
>
> That'd be pretty convenient
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bipy/pyqi/pull/110/files#r5609120>
> .
>