1 the kludge which greps for inputbox("field") in template to find valid form
2 fields doesn't work when there are multiple inputbox'es on a line. perhaps
3 it is time to come up with something that's not a kludge - but what? have
4 user specify all the field names explicitly, elsewhere?
6 here's a one-liner to find duplicate inputbox'es:
8 grep inputbox staffing.html | perl -pe '/inputbox\(\"(.*)\"\)/ or die; $_="$1\n";' | sort | uniq -d
10 (though the program should probably error out)
12 and here's another useful one:
14 perl -ne 'if ( /^((.*)\s+)(\S+\@\S+)$/ ) { print "$1<$3>\n"; } else { print "$_\n"; }' P*
16 Delivered-To: ivan-fnf-planners@420.am
17 To: phred@well.com, larryc@cloudfactory.org, fnf-planners@topica.com
18 From: Rob Jellinghaus <robj@unrealities.com>
19 Subject: Re: [FnF-Planners] Staffing feedback
20 Date: Tue, 07 Mar 2000 14:25:16 -0800
22 At 02:00 PM 3/7/2000 -0800, Fred Heutte wrote:
23 >Handing out the staff assignment slips was a big plus. Next time
24 >the channel allocations for the radio links should be there also --
25 >keeping track of what should be happening on four different channels is
26 >just too much instruction to give just verbally.
28 Great idea. In fact, some more infrastructure overall would have been good:
30 - Along with the printed-out staff sheet, a list of the shift descriptions
31 and the radio allocations and channel assignments.
33 - On the printed slips:
36 - start time, end time
38 - get there early reminder
40 (everything was there this time but the radio info)
42 Mike, Ivan, it would be ultra cool if the staff sheet script could be
43 extended to generate conveniently-printed lists of all this for each staff
44 member. Obviously the staff sheet template would need to be extended with
45 start time / end time / general notes for each shift, in some format that
46 the staff sheet could then turn into a printed list. (The general notes
47 for each shift could be just plain text, including the staff description,
48 reminder, radio info, etc.). As it was, I had to rush home at 8 pm the
49 night of the party and spend a solid hour typing/cutting/pasting as fast as
50 I could (literally) until 9 pm... just barely made it to orientation. If
51 the script had been able to do it for me, it would have been astoundingly
52 easier. Nothing like feature creep, eh? :-)
57 On Tue, Dec 19, 2000 at 07:53:19PM -0800, goolie wrote:
61 > Tell me... how hard would it be to get this staffsheet thing to print out
62 > names and the times their supposed to work? Pretty hard, huh? I'm just
65 to do it "right", as in, have the staffsheet know about *time*. that
66 wouldn't be trivial. that's my long-term project, where you layout the
67 staff sheet with an html interface, and it knows what time each signup box
70 however, if you could, say, add a field to each { inputbox } which is just
71 what you wanted to print out on the slip... that i could do without a lot
74 so right now, inputbox'es look like:
76 { inputbox("shift_name"); }
78 and instead, they would look like:
80 { inputbox("shift_name", "shift time etc. to print on slip" ); }
82 and i could print slips with people's names/emails, the extra stuff above
83 and something standard that goes on each slip...
85 how's that work for you?
87 > And then, how hard would "search" functionality be, so i could search for
90 the quick kludge answer: you could grep the data directory? the filenames
91 correspond to the inputbox tags you define, so...