"Stupid" is a rather strong word, but yes, it is an ill-advised approach. Let's assume you sort out the particulars of issuing requests to a server for more data without moving off of the current page. (This can be done, with hidden frames and Javascript.) The killer will be performance.
Dynamically requesting new data as the mouse wanders over an images is a viable approach for a fat UI that has a short and fast pipe to underlying data, but for a web-based application, performance is going to SUCK. The lag between determining that you need to fetch data for more cities and that data being available in the browser will driver your users up the wall. (It did to our users when we tried something similar.)
I think your best bet is to generate a fatter page initially, with city data in Javascript data structures that you can query in the browser.
In reply to Re: Calling a perl function from within a javascript function
by dws
in thread Calling a perl function from within a javascript function
by Baz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |