Tom Plagge on Sun, 5 Dec 2004 03:40:16 -0600 (CST)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[nimh-dev] Summary of existing code


All right, here's the situation so far.  I've written (barely) functional
scan and show programs that I've called nimh_scan.py and nimh_show.py.  All
they do is take an optional folder or sequence (using Joel's sequence code) 
on the command line, check .mh_profile for a scanproc or showproc, and using
either those or the defaults, list or display the chosen messages.  

To get there, Joel and I have put together the basics of some classes in a 
module.  They include folder, message, and sequence classes, as well as classes
to handle .mh_profile, context, and .mh_sequence files.  The latter 3 classes
ought to be abstracted to a config file class that will later be the parent
class for replcomps, .mh_mimeconfig, and so on.  

None of the code to send or modify messages, or to modify folders, or to
change config files (such as change the Current-Folder) have been written
yet.  Some amount of error checking is in place, but it's insufficient.  

Anyway, it's coming along nicely.  In order to have a system that we can start
using, we need to, in no particular order,

1. Clean up the current code, abstracting classes and adding functionality as
   needed or convenient.
2. Implement ``inc''.
3. Implement ``comp''.
   a. Put together something similar to ``whatnow'' (but better).
4. Do some quickies like ``anno'', ``pick'', ``folder'', ``refile''.
5. Add MIME functionality to show (not too hard).
6. Implement ``repl'' and ``forw'' after figuring out the appropriate format.
7. Aliases.
8. Loose ends; programs that I don't use but that others might. 

Anyway, I'm off to bed.  Talk to you all tomorrow
-t

________________________________________________________________________
Tom Plagge                              UC Berkeley Physics Dept.
351 LeConte Hall                        Voice: (510) 643-1650
Berkeley, CA  94720                     Email: tplagge@xxxxxxxxxxxxxxxxx
_______________________________________________
nimh-dev mailing list
nimh-dev@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/nimh-dev