One thing I'd like to see is a write up of things that dojo does poorly and could be improved by switching to jQuery.
I'm not advocating that Esri switch to jQuery, but here are some reasons I prefer to use jQuery over Dojo.When I create controls for developers who have no GIS experience, I currently create them using jQuery UI Widget Factory using a minimal amount of Dojo as required for the ArcGIS JS API.
- jQuery has better documentation than Dojo. Not just jQuery and Dojo's own websites, but it's easier to find outside tutorials for accomplishing a task with jQuery than with Dojo using a search engine.
- Most things are more complicated in Dojo than jQuery. For example, try going through the both the jQuery Mobile and Dojo Mobile tutorials. I found that it is much easier for me to create my own widgets in jQuery (using the jQuery UI Widget Factory) than it is to create "dijits".
- The Dojo UI controls are weird. When you create a Dojo UI Button, it changes the HTML button element into a span element. When you create a jQuery UI Button, it remains an HTML button.
If you're after the jQuery style of selector syntax, check out dojox.jq.
Hello Steve G,
I just saw in your sample PermitView.
It's so smooth and good app with jquery that i saw in a while. I was looking for such examples.
One thing i noticed that in your print map, there were buffer circles in the final map. I was wondering, how were you able to get buffer graphics exported to map? Did you use buffer_analysis inside of your python script or did you export graphics from javascript and sent it to export_map?
Thanks and Regards,
Shay~