[thelist] dynamically populating <SELECT> when selected

[Ian Anderson]

Tom Schmidt wrote:

> I agree this is a fairly sub-optimal solution.  My limitation is that
> my solution (should I choose one), must be 100% client side based,
> and in this case, that means standard HTML, javascript, and the
> application specific tags (APIs) that interface with the application
> and the database.

I don't understand how what you're proposing will make any difference, 
if there isn't the facility to use server side scripting to control the 
options that are generated for the dynamically populated popup.

You're saying then that all the data has to be loaded into the page at 
first load, and then some of the options will populate the select menu. 
And you're saying that building the full popup takes too long

But it's the same data you're loading. You either load it into a 
JavAScript array or into an HTML popup menu. I don't see how you can 
save download or server processing time unless you are hitting the 
server again for a reduced data set after the user's first interaction.

My personal feeling is that you should be using two separate pages, 
rather than trying to get all this happening in a single screen. Which 
would again require server side scripting to filter down the options for 
the second screen.

HTH

Cheers

Ian



-- 
_________________________________________________
zStudio - Web development and accessibility
http://zStudio.co.uk

Snippetz.net BETA - Online code library
File, manage and re-use your code snippets online
http://snippetz.net