Jeremie Cornet ... awesome! I can confirm, measurement with all methods now works, Geometry Engine is now accurate for me as well for length and area.
So awesome that measurements now update!
by the way, what does "NB" mean, or stand for? In the dialogue when modifying a measurement label. Also, move has a typo an extra 'o'. Unless we are talking about cow geometry here. 
NB : you can modify/moove geometry on map.
Thanks! This is an incredible widget. Really looking forward to adding Point measurement in the future as well as segments. Point is probably a little more important to us at the moment since Tom Sellsted 's Measure does Segments perfectly. (Longterm, it would seem logical to merge these two perhaps)
NB is nota bene 
Nota bene - Wikipedia, the free encyclopedia
For "moove", i thought i have remoooved it 
Hi Jeremie, testing the latest version you are testing (with Alaska Albers, WKID 3338, WAB 1.2, Firefox)
1) I thought the previous version was showing measurements as we clicked, but might be getting that mixed up with the measure widget. I'm not sure what it would take to add that to this, but that is a nice feature in the measure. Both widgets have very nice features, but for now it looks like I will need both in my apps.
2) The drawing list seems to duplicate the entry after I "do something else". That is, if I draw a 1 square mile box and name it, then close the widget and open i (maybe just move to a differe draw tab)t, there are now two entries. Is this as-designed? And if so, what is the purpose of the second one? I named mine "oneSqMi" and the other just showed up.
Personal comment on the import/export icons (just my opinion....take it or leave it). Seems to me the up-arrow should be import, down-arrow should be download/save. This would make more sense to me on the graphic above. Also, maybe since you have the download here, you could also have the import and remove a tab? Just a thought (and 1) have no idea how much work it would be, and 2) that seems to work so....)
Thanks for you work on this widget!
Jeremie Cornet On this same line of thinking as Finbar, I'm thinking about using this widget as a way for staff to create basically as red-line document that they could then send us for updating our SDE master files. They don't usually have the time to make sure all the detail is to the standards we have to maintain.
I was looking at the json output and wondering what is the best way to use this type of operation (i.e. python snippet anyone?). I was going to post this to a new thread, and will if needed, but since Finbar mentioned a shapefile output, I decided to do a +1 for that. Let me know if I should go ahead and fork my question.
-------
EDIT: I did find a Tool and/or python solution for converting the json to a FC or shapefile. For our internal use, that would probably work. The help doc for 10.2 ArcGIS Help (10.2, 10.2.1, and 10.2.2)
python snippets for FC and shapefile
arcpy.JSONToFeatures_conversion(in_json_file="C:/myDrawing.json", out_features="C:/data/jsonTest.gdb/jsonfc") arcpy.JSONToFeatures_conversion(in_json_file="C:/myDrawing.json", out_features="C:/data/jsonShape.shp")
by default eDraw save the json to folder/file: C:\Users\<username>\AppData\Local\Temp\<filename>.json
Although a direct save would be nice, this is a pretty easy fix (and much easier than my knowledge of widget development)