I'm having a horrible time deciding the best way to accomplish this goal.
Let me see if I can explain this well enough that I can get some
suggestions.
For a small business intranet, I want the user to fill out the form, save it
onto the web server, and be able to retreive it later. A text file will be
fine, there won't be any need for reporting etc and a database would be
overkill. I would like to have a directory structure on the web server that
matches with three of the fields on the form, a directory for each engineer,
then a subdirectory for each band (created as needed), and then a text file
for each song name that that contains the state of the form. Each form will
be the tracking sheet for a particular song.
I have the saving part worked out. After the form is filled out it is saved
as a text file in the appropriate location. But I am stuck on how to let the
user pull the form back up. I'm imagining that the user will select from the
engineer names in a drop list, then possible band names for that engineer in
a drop list, and then the possible song names for that band will be shown in
the next drop list. After selecting the desired song name the form will then
be loaded using that saved form information.
I looked into using javascript to display the list boxes dynamically
depending on user input, but of course javascript can't go back and get a
directory listing off of the server to see what the next choices should be.
I also don't really want to have to expand my horizons into javascript if I
don't have to, since I'm still learning perl :) Someone suggested that I
build a hash using File::Find to begin with of all directories and
subdirectories when the page loads. I don't expect this to be hit more than
a few times a day, but would like to build this the best way, so that I can
copy this concept for similar uses.
I would like to have the directory structure instead of all the saved files
in one directory, simply because I can leverage that directory structure for
other things. But I am very open to suggestions. I looked at the web page
http://www.wiley.com/legacy/compbooks/stein/ and that is how I worked out
the saving part. But his example of how to restore is not practical, as it
has the user type in the path to the file. The other reference I have used
is the O'Reilly CGI Programming with Perl book.
Sorry this was so long, and if you read this far thanks!
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
