richard said:
On Thu, 4 Jun 2009 12:35:12 -0600, "Mel Smith"
You might want to consider doing this in PHP. A server side script
could handle this problem easier.
Instead of listing all 600 plus items, list them in smaller groups.
Assuming you have somewhat of "streets" in your park, you could list
the names according to the street.
Richard:
Some explanatory notes and corrections:
- My phonebook is two columns (in the general sense) wide, with the
Names (plus phone numbers, addresses, lot numbers, etc, etc). in
alphabetical order left-to-right, and top-to-bottom.
- In the viewport in full-screen, nearly six phone/name entries are
displayed (with a slider on the right side of the viewport for a resident to
view all the other residents), and also a button (in his *own* entry) to
allow him to edit his own demographic information (some of which does not
display in the online phone book)
- Since we have a set amount of 613 homesites and homes, I then have
307 'blocks' of resident information arranged in two columns.
- Since I am a long-time commercial business application developer in
Windows, and have expertise in database systems (CDX Databases mostly), I
create / modify / send all my pages from a C-based language (see
www.xharbour.com). I run my own apache server right beside me in my home
office. I have a very limited knowledge of web page design going back only
five months
- Since I'm networked with my apache server beside me, it is normal
for me to send updates to the server many times each day for testing and
trials.
My Problem:
- The residential data is badly out-of-date (e.g.,home summer
caretakers have been dead for years, emergency phone numbers are badly
out-of-date, etc). The Park Office puts out a hard copy of the Phone Book
yearly, but it has wrong information in many places. Only the homeowner
himself *really* knows the correct information.
- I wish the homeowner (or one of his computer knowledgeable friends)
to access the online directory, move to his entry in the table, 'click' on
this EDIT button, get my input page, and modify his demographic data, submit
it to me, where I'll verify it (with my C-based CGI program), and place it
in my datasbase, and quickly re-build the basic resident directory page
(about 3/4 of a second).
- THEN, I want to send the corrected phonebook page back to him *and*
position the long table so that *his* entry is in the viewport, and he can
see that he made the proper changes.
(btw, this morning I tried to use the following:
<body onload="window.document.getElementById('lot318').focus();">
(and deep in the body I had <input type="submit", id="lot318",
value="EDIT> , etc, etc)
but when I viewed the page with explorer it didn't move down the
viewport to this entry. Sigh ...
Sorry for this long harangue.
Thanks for your suggestion.
-Mel Smith