axxl et al what do you think the best new things are with the new Dojo? Will you do anything new now that leverages the new Dojo? Just curious, thanks.
I can't believe there's no search box for the API Reference anymore, 'cause, like who would ever want to search it right. So awesome now to search google for "arcgis javascript <term>" and get a page that says "The page you're looking for does not exist or has been moved", but does nothing to get you to that specific page in the new reference. Real bang up job.
Thanks Kelly for the quick response. The problem is when click second level navigation items in left side, the content in right side does not refresh. And the error is "Object doesn't support this action".
I ran a quick test of this sample in IE7 and it worked for me. Can you provide more details about what you mean by 'cannot run well'. Are you getting an error? Does the sample load?
And many stuff CANNOT run well under IE7, such as Samples/map, http://help.arcgis.com/en/webapi/javascript/arcgis/jssamples/#sample/map_infowindow
In the latest sample "Create a map", the syntax still is dojo.require("esri.map"); should be require(["esri/map"]);?
my understand is at dojo 1.8 both are supported but the latter (newer format) is preferred, and at dojo 2.0 the latter format will be required.So we can begin transitioning without breaking everything.
The Samples no longer take you first to the source code, but rather straight to the live application. While I can still get to the Source, of course, this is a bit annoying. It even still says on the bottom of the Sample Page:"These samples demonstrate how to use various features in the ArcGIS API for JavaScript. Each sample page contains a description of what happens in the sample, the source code and links to view the sample live or download as a .zip file. Watch a video that shows how you can copy the code from the samples to run them on your machine."Despite this currently not being true.
dojo/parser::parse() error TypeError arguments: Array[2] get message: function () { [native code] } get stack: function () { [native code] } set message: function () { [native code] } set stack: function () { [native code] } type: "non_object_property_call" __proto__: Error
Using lang="en" can break apps that use when using layout dijits and data-dojo-config(or dojoConfig) locale or extraLocale is not set. The recommended fix is to set locale or extraLocale on data-dojo-config or remove the lang="en" attribute. The specific error seen when this is an issue is "dojo/parser::parse() error TypeError" in Chrome and "TypeError: _72f(...) is undefined" in Firefox. More information is available in the Dojo bug tracker:http://trac.dojotoolkit.org/ticket/15630#comment:7 http://trac.dojotoolkit.org/ticket/15768#comment:6
dawenx you're right, I don't see a Search anywhere either. This should be added back. FYI I loaded that page fine in FF 17.
dojo.io.script errorError: Unauthorized access
the website will take some getting used to, but I like the look and feel of it so far. Looking forward to seeing the full list of enhancements and bug fixes.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.