new, more readable table.html from JD

1 files changed, 47 insertions, 0 deletions

diff --git a/TODO b/TODO
index 771ae48..bba92ca 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,8 @@
+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
@@ -49,3 +54,45 @@ 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
+
+