Re: Revised Optik docs

On Tue, 2004-05-25 at 10:47, Greg Ward wrote:
> Hi all -- after sitting down to document the Optik features that I've
> recently been working on, I ended up spending the afternoon getting the
> docs into the shape they should have been in before I released Optik
> 1.4.1 just over a year ago.  Sigh.  (Thank goodness for rainy afternoons
> on the third day of a long weekend, otherwise I'd never get anything
> done.)

This is probably a good time to raise the refactoring and extension I've
been hacking on. It's all in my arch archive - I've resent the previous
emails to the list, which sourceforge had blackholed the first time
around.

The latest code is considerably more advanced, but I'm still tweaking
the api as I develop the first user-of-the-code classes. I guess the
first place to start is:
are you interested in taking optik in the same direction I/we have? 

The direction is for optik to be a framework supporting:
* option parsing
* argument parsing
* autogenerated help strings for the first two 
* command line completion feedback from the grammars for the option and
argument parsers. (i.e. for use by the cmd module).
* Easily extensible by composition, not inheritance - to allow libraries
to provide Option and Argument plugins, that client classes can use.
I.e. module CVS might provide a CVSRepositoryArgument that knows how to
parse and validate cvs repository location strings.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAsqRbI5+kQ8LJcoIRAsTYAKCt5qFMNrGDIhj6DwL18WBLLaDB+ACcCobR
fgvsVejNjixlywUuBKmUHVM=
=A6yq
-----END PGP SIGNATURE-----