OK the more I explore this, I'm getting seriously interested. One thing I'd add either if I do it or someone else does is to put a Nav widget in (previous extent, forward to next extent) and a buffer tool. Although I guess that could be created with the Geoprocessing widget. I'll read up on widget dev, but so far the documentation looks pretty thorough and more importantly, it seems to actually encourage "widgets" in a standard way. I always disliked how blocks of code on the JS API page were called Widgets. Yes I know the Dojo term and it loosely applies. But to me, a widget is a completely independent block of code that provides a functionality (i.e. Draw) and is EASY to add to your project. No mucking around with scoping, variable names, etc. It just works. Like in Flash. You want a Widget? Download it to the Widgets folder, turn it on in config, and you're done. There is no step 3.
A big question: So, Query Widget. It executes pre-defined Queries. That is good. But, could ESRI consider enhancing this widget, in order to allow end users to construct their OWN queries? Basically, just expose the interface that we see as developers, to construct the queries. That would be exponentially more useful. I can see adding only a handful of preset queries before it gets to be "too much". But almost every user might have a unique query they would want, and perhaps a different kind of query every day even, depending on what they need to know.
Also how do we add our own REST endpoints. We want nothing to do with ArcGIS.com at least for some of our viewers. (We have an org account and like it but it can not be used for certain kinds of data and viewers)
Also I'd recommend at least as an option to display each line segment or each side with its own measured length dimension, in Draw. Like the old Draw in Simple Viewer or the Flash/Flex Draw/Measure widget. So if you draw a rectangle for example, it has the length of each side on it as text labels.
