<link rel="stylesheet" type="text/css" href="http://serverapi.arcgisonline.com/jsapi/arcgis/3.0/js/dojo/dijit/themes/claro/claro.css"> <script type="text/javascript" src="http://serverapi.arcgisonline.com/jsapi/arcgis/?v=3.0"></script>
Solved! Go to Solution.
I'm having a similar problem. Also I am running this from my local file system [ATTACH=CONFIG]15793[/ATTACH]
I'm having a similar problem. Also I am running this from my local file system [ATTACH=CONFIG]15793[/ATTACH]
Please use a local web server. It's not realistic to run web apps from your local file system. There are plenty of free options and most OSes come with a web server built-in.
Hi Derek,
Thanks for the clarification. However, I agree with Jeff that this represents a new hurdle for developers (especially those just starting out with the JS API).
While it's not realistic to run web apps from a local file system, it IS common to fire up a quick sample to check how one specific thing works, which is surely the point of the samples? This is how we test out new functionality before compiling it into a robust web app for deployment (not just in the ArcGIS Server JS API but in other web mapping APIs, or indeed other JavaScript/HTML libraries).
I haven't looked into v3.0 yet so I don't fully understand the change, and why it was necessary. As a developer, all I can see is that the copy/paste/test approach used to work, and now doesn't. Perhaps there could be a blog post/tutorial explaining the changes, and giving some simple instructions for the new requirements of a web server - this could be linked on each sample page.
Cheers,
Steve