Found one but perhaps that makes use of API version 3 which is quite different from version 4.
Please guide. Thanks.
I have to wonder if Esri will need to make more progress with porting functionality from 3.x before we see more literature. There is still a bit of important functionality that needs to be ported, not to mention some bugs and intricacies resolved in 3.x that have cropped-up again in v4.
I like the progress on the one hand, but on the other, we have invested years into creating a mature product based upon the 3.x line, Esri's suggestion to "re-write" rather than port 3.x-based applications really stings! IMHO, API upgrades shouldn't be so obtuse, but I understand the reasoning, and it is certainly not unprecedented. We re-wrote our mapping app from Silverlight (not even Esri-based) before switching to the JSAPI a few years ago.
The future is a 5 mile tall obelisk rave party over London?
This isn't my future, and arguably that's not A LOT of other people's futures as well. What IS my future is migrating my 3.x apps which require selecting features within a featureLayer, a refresh interval on featureLayers, modifying graphics, changing the renderer, a color picker, feature table, measurement widget, editing, and the draw toolbar (all things STILL listed as "coming soon" as of version 4.3).
I was trying to inject some levity into the discussion, apologies if I didn't succeed.
It's worth noting that, while a lot of the functionality you mention is missing a plug-and-play solution, the building blocks to accomplish most (maybe all) of those things are exposed in the API. I've had to tackle most of those issues myself, building on top of the API.
The building blocks are really what's exciting to me: the potential is there to build some really cool things, in 2D and 3D.