Re: [nimh-dev] TODO

[Tom Plagge <tplagge@xxxxxxxxxxxxxxxxx>]

Okay, I'm back.  Ended up having more fun than I planned last night, hence
no hacking.  Sounds like you guys kicked some ass.

I'll contact python-dev as soon as we have a reasonable body of stuff to 
commit.

> 3. Decide what to do about mh-format: keep? toss?
>   If toss:
>     Maybe we want to define, e.g., a 'scanformatproc' key, which just
>     feeds the raw data to some program, which then hands its output back to
>     scan. That way, I could write my scan format in python or sed or perl or
>     cat it from /dev/random, and I could make it as (un)readable as I choose.
>   Maybe mhlib should understand mh-formats too?

I don't like mh-format, but if we can get it supported, we could keep it 
around as a legacy option.  I kind of like the idea of supporting all the
old-school mh config files so that nimh can be used as a drop-in replacement,
but also adding in new and more reasonable tools where appropriate.  

I had planned on implementing something like a scanformatproc already,
since scan's overall gimpiness is probably my number one annoyance with mh. 
scanformatproc seems like a good way to proceed, in which case we should have
a ``/usr/local/share/nimh/scanformat'' that is used by default.
-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