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