On Sep 12, 9:51 pm, Ben Bleything <b...@bleything.net> wrote:
> On Thu, Sep 13, 2007, barjunk wrote:
> > On Sep 12, 11:28 am, Ben Bleything <bbleyth...@laika.com> wrote:
> > > * Linen -- A framework for building command-line interfaces
>
> > This looks interesting. If someone wasn't using this, what would they
> > use?
>
> That's an interesting question. At the time we started on Linen, we
> didn't know about HighLine[1]. Had we, Linen would look different
> today. That said, HighLine is, at its core, a wrapper for Readline that
> gives you a bunch of really nice ways to ask the user for input.
>
> Linen was designed to be the underlying framework of an application that
> adds host to our directory server. We call it "a framework for building
> command-line interfaces", but what Linen is really about is defining
> how to get input from the user and what to do with it once you have
> it. This latter bit is what HighLine doesn't do for you. It's just a
> different philosophy; we needed to build a system where the user could
> define the action in a similar way to how they define the input.
>
...snip..

Thanks Ben.

How does OptParse fit into all of this?

The upcoming release of the animation looks intersting as well.

Thanks for releasing this to the community.

Mike B.

On Fri, Sep 14, 2007, barjunk wrote:
> How does OptParse fit into all of this?

OptParse is just a library to parse command line flags. It's about half
of what main does... main adds the ability to define the action that's
performed on the options that are fetched from the command line.

> The upcoming release of the animation looks intersting as well.

I think we're all very excited about it

> Thanks for releasing this to the community.

You're welcome. I'm really glad we were able to do so.

Ben