[OctDev] Repository priorities

[Matthew W. R. <ma...@ne...>]

Well, I guess it's time to start trying to get the repository moving
again. :)


Here's what I've done lately:

1) Cut a lot of the garbage and dated stuff out of the home page.

BTW, I found out that sourceforge has archives up now:

http://lists.sourceforge.net/archives/octave-dev/

It should help those of you (like me) who need to remember where the
development state is.

2) Started working on a perl script to allow "easy" browsing of the
CVS tree.  You can the see output here:

http://octave.sourceforge.net/afunclist.html

The script is in CVS now (cvs-tree).  One problem I had was robustly
extracting the "help" text from the script files.  If anyone has any
suggestions I'd appreciate it.

Also, as you can see, I did some very simple TeXinfo formatting,
just to make the descriptions readable.  I don't think trying to
write a perl Texinfo parser is the way to go.  Anyone have any ideas
how to translate the texinfo help into html text that could be used
in a script?

Lastly, I want to do more than just an alphabetical listing.  I'd
like to do some sort of categorizing.  My initial idea is to put
description files in each of the active directories.  The file
should be named the same thing in each directory.  Then I can walk
the CVS tree and build a nice "manual" with sections.  Thoughts?

Future Plans:

I'd like to upload it into CVS unless someone else wants to take that on.

Also, I'd like to start working on a Makefile.  I don't think I need
to go the autoconf route -- it seems we just need to have something
that will copy script files into the right directories.  Any ideas
how the configuration should work?

Thanks,  

--
Matthew W. Roberts
------------------------------------------------------------------
Structural Engineering  *  Texas A&M University  *  ma...@ta...