Jeff Hostetler wrote:
> i send my last response before i received your second
> messge last night (chicago time), so when i wrote my
> data structure discussion i hadn't seen your getopt_long
> table stuff.
>
> parse command line should be done first and build a list
> of filenames to open and maybe update the option variable
> settings. then show the splash. this needs to occur
> quickly -- you want the splash to occupy the user's eye
> while they wait for the document windows to open.
>
> then (while the splash is up) go thru and start creating
> document windows and opening document files -- this can
> take a while -- depending upon the speed of the machine
> and the bandwidth of the X connection and the size of the
> document on disk. this is why i was suggesting a ut_vector
> of filenames -- accumulate them in the parse and then
> wait and open them one by one later on by walking thru the
> vector.
>
> as for the getopt table of values, i've not had a chance
> to read the man page on it, so i'll have to let you and
> Shaw discuss this. (i'm leaving for vacation tomorrow)
>
> as for the list of options what we need, the list that i
> noted in pseudo-BNF in the comment block is a good start.
> i would add --help as is the style and the usage dump as
> is typical.
>
> jeff
Ok! But I have an end-of-term examination! -_-
Here are a sample of new ParseCommandLine
using getopt_long. Of couse, it will call _showSplash
before opening documents. :)
New-ParseCommandLine-Sample.patch.gz
