Re: [Ftnpl-develop] pkt2txt: working dir changes

[Russ J. <ru...@di...>]

OK, and my main area of concern will be the output filename, and adding 
HTML output. This will involve adding at least one new subroutine. We have 
&printtext for the text output. I'll be using &printhtml for the new 
subroutine. We'll need a command line parameter to specify what output.

Another concern is what if someone wants multiple forms of output? I'm 
thinking the newmsg (I'll be changing this too :) ) routine could call each 
version of output.

We also should have the option (command line parameter) of NOT deleting the 
input files. This will be useful for testing, but someone may also want to 
do this in a production environment.

I'm probably missing something here, but that's what I'm thinking right now.

At 04:36 PM 8/26/2001 -0400, you wrote:
>Russ,
>
>    I've added some files, as follows:
>
>README    -  A readme file giving a brief description of what the script
>does, & lists what the files
>                      in the directory are for.
>
>file_id.diz     -   standard file_id.diz file (I hope...<g>) describeing
>this script
>
>pk2txt.sh     -   an example shell script for running pkt2txt.pl.    Not
>real important  now, but it will be
>                       when there are more parameters...
>
>
>    I also updated the TODO list.   What I'm going to be working on is adding
>some parameters & cleaning up the logging subroutine (likely including a
>name change for the subroutine).   I'll be doing this, btw, by using doing a
>branch to work on the changes & then merge the changes back in once they're
>working;   the kind of changes I'm going to do perhaps does not neccessitate
>an actual branch, but OTOH I need practice on how to do branching &
>merging...<g>
>
>    I'm going to add three command line parameters;   one for defineing the
>logfile, one for defineing the "$INDIR" parameter, & one for defineing the
>"$OUTDIR" variable.   Once I have the logfile defined by a command line
>parameter or by default, I'll clean up the logging subroutine as neccessary.
>And I'll be changeing the example shell script as neccessary as I go
>along...
>
>    Once that's all done, I'll see about merging it back in to the main
>branch...   I'll mostly be working only on the commandline subroutine & what
>is currently called the logmsg subroutine, so it should merge back in with
>no real problems;  assuming I do it right, at least...<g>
>
>
>
>Jame
>
>
>
>
>
>_______________________________________________
>Ftnpl-develop mailing list
>Ftn...@li...
>http://lists.sourceforge.net/lists/listinfo/ftnpl-develop

Russ Johnson
Stargate Online

http://www.dimstar.net
telnet://telnet.dimstar.net
ICQ: 3739685