> example:http://www.myethiopia.org/KililisandWoredasandZones/Kilil/Kilil.html (shouldn't take more than 14 sec :))
Took three minutes and a "script running slow" prompt in IE ; in Firefox about the same time and eight prompts. Not all PCs or browsers are alike. The javascript file here is "only" 2Mb ... you've got to simplify. Just taking out whitespace would help. Do you really need both google and yahoo maps? Can you simplify the projections in use? Would another data format work quicker than WKT? Do your points really need to be specified to better than 1mm precision? Seperating the data from the script is good practice, and should allow you to at least show some kind of map while all the crunching is going on, instead of the nothingness that currently greets visitors to your page. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/openlayers-and-css-error-tp5271709p5278670.html Sent from the OpenLayers Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
