Fill dropdown on demand from script

[Jochen Daum]

Hi !

I have a page with a large amount of dropdowns, which are quite big
sometimes. All these are generated with PHP. Some timing tests tell me
that the problem is not the database, but the sheer data.

So, I would like to do something to fill the dropdown-box on demand. I
thought of maybe opening a Pop-Up window (maybe even an IE dialog box)
and copying the information from there into the select box.

How would you guys do that? Use a popup window, IE dialog or a hidden
frame?

Would you store the information in that popup? In a javascript array
or HTML form or something else?

Thanks for any idea.

Jochen
--
Jochen Daum - CANS Ltd.
PHP DB Edit Toolkit -- PHP scripts for building
database editing interfaces.
http://sourceforge.net/projects/phpdbedittk/

[Peter Hurford]

If I were guaranteed an MS browser, I'd look at using javascript to
"CreateActiveXObject", and look at Microsoft's XMLHTTP object (part of
MSXML 3 or 4).

Post an xml doc to the server and receive server's response as an xml
doc. Server code can be php I guess, if that's what you like. Can do all
this asynchronously on the client if you wish.

HTH
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Richard Cornford]

"Peter Hurford" <pe***********@microcrest.com> wrote in message
news:3f***********************@news.frii.net...

If I were guaranteed an MS browser, I'd look at using javascript
to "CreateActiveXObject", and look at Microsoft's XMLHTTP object
(part of MSXML 3 or 4).

<snip>

And if you were interested in authoring for non-Microsoft Windows
browsers (in their default configuration) you would know that
Mozilla/Gecko browsers offer a parallel mechanism for doing exactly the
same:-

<URL: http://jibbering.com/faq/#FAQ4_38 >

Though the only cross-browser method would involve re-loading the pages
and having the server scripts fill in the required information. Given
that the stated problem is the size of the resulting HTML the best
solution might be to split the page up over several pages (a wizard
style interface instead of a single form).

Richard.

[Jochen Daum]

Hi Richard, Peter!

On Mon, 1 Sep 2003 16:26:49 +0100, "Richard Cornford"
<Ri*****@litotes.demon.co.uk> wrote:

"Peter Hurford" <pe***********@microcrest.com> wrote in message
news:3f***********************@news.frii.net...

If I were guaranteed an MS browser, I'd look at using javascript
to "CreateActiveXObject", and look at Microsoft's XMLHTTP object
(part of MSXML 3 or 4).

<snip>

And if you were interested in authoring for non-Microsoft Windows
browsers (in their default configuration) you would know that
Mozilla/Gecko browsers offer a parallel mechanism for doing exactly the
same:-

<URL: http://jibbering.com/faq/#FAQ4_38 >

Though the only cross-browser method would involve re-loading the pages
and having the server scripts fill in the required information. Given
that the stated problem is the size of the resulting HTML the best
solution might be to split the page up over several pages (a wizard
style interface instead of a single form).

This sound actually much more complicated than opening a new page and
copying the content of an array into a select tag. I think I keep
sticking to that.

Jochen
--
Jochen Daum - CANS Ltd.
PHP DB Edit Toolkit -- PHP scripts for building
database editing interfaces.
http://sourceforge.net/projects/phpdbedittk/

[Peter Hurford]

You're right, it is more complicated our way. But what you get is the
ability to load things dynamically - potentially only as and when
they're needed - rather than having to load everything at the start.

If your users can handle the delay when the page first shows, stick with
your original. Your right it'll be less complex code-wise.

P

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Jochen Daum]

Hi Peter!

On 02 Sep 2003 08:22:34 GMT, Peter Hurford
<pe***********@microcrest.com> wrote:

You're right, it is more complicated our way. But what you get is the
ability to load things dynamically - potentially only as and when
they're needed - rather than having to load everything at the start.
That exactly what I want as well, but I don't quite see, why I need
XML for that.
If your users can handle the delay when the page first shows, stick with
your original. Your right it'll be less complex code-wise.

Ok, so does IE load this asynchronously, without the javascript event?
Jochen
--
Jochen Daum - CANS Ltd.
PHP DB Edit Toolkit -- PHP scripts for building
database editing interfaces.
http://sourceforge.net/projects/phpdbedittk/

[Sean Jorden]

Jochen Daum <jo*********@cans.co.nz> wrote in
news:g2********************************@4ax.com:

Hi Peter!

On 02 Sep 2003 08:22:34 GMT, Peter Hurford
<pe***********@microcrest.com> wrote:

You're right, it is more complicated our way. But what you get is the
ability to load things dynamically - potentially only as and when
they're needed - rather than having to load everything at the start.

That exactly what I want as well, but I don't quite see, why I need
XML for that.

If your users can handle the delay when the page first shows, stick with
your original. Your right it'll be less complex code-wise.

Ok, so does IE load this asynchronously, without the javascript event?
Jochen

you might also want to look at remote scripting with an IFRAME which is
more cross browser that the process described previously.

http://www.oreillynet.com/pub/a/java...08/iframe.html
http://developer.apple.com/internet/...pt/iframe.html

basically you use an invisible IFRAME (pre-created or created dynamically)
and use it to load pages that will output javascript statements to perform
whatever action you wish, such as filling a drop down with values.

--
Sean Jorden
Norada Corp.