Editor should support easy update option - like chrome

[DartBot]

This issue was originally filed by jimhug@google.com

---

It should be a simple one-click process to update the editor to the latest sdk, dartium and editor itself. This is a high-priority issue now due to the immature nature of all three pieces. It would make working with the tools in this early stage much more pleasant. FWIW - The lack of this feature has often caused me to go back to using textmate and the command-line tools for a day or two when I need a feature from head and don't feel like going through the current manual update process.

[anders-sandholm]

In general, I think we need to rethink our release cycle for trunk and editor.

---

Added Triaged label.

[pq]

Set owner to @pq.

[DartBot]

This comment was originally written by @Bluenuance

---

an update feature like the Chrome has would be top!

[pq]

Added Started label.

[pq]

Issue #3327 has been merged into this issue.

[clayberg]

Added this to the M1 milestone.

[jmesserly]

+1, this would be so nice. Since I generally use the Dartium that's bundled with the editor, this would also solve the "Dartium expired" problem. Two birds with one stone!

[DartBot]

This comment was originally written by @butlermatt

---

(Comments copied over from issue #2 and expanded upon)

I think it would be great to have a working auto-update process, However as was previously mentioned on the mailing:
https://groups.google.com/a/dartlang.org/d/topic/misc/2Uc6cNDWNz0/discussion (see comment from: Peter von der Ahé on May 22nd)

A mechanism should exist to disable auto-update/expiration of tools for situations like educational institutions which rely on a static version for teaching without having to be concerned about the updates changing functionality while students are still going through the learning process.

This is something though that should be discouraged 99% of the time, as such I would rather see it a manual flag to be added in something like DartEditor.ini as opposed to an option that is available through the preferences.

[sethladd]

Issue #3327 has been merged into this issue.

[pq]

As of our latest integration build (12440), the bit is flipped and this is on.

Do note that auto-update is disabled by default. If we want to go further, as in Peter's use case above, and disappear it altogether, we can definitely do that too. If so, let's track that as a new feature request.

---

Added Fixed label.

[jmesserly]

Awesome! Do you plan to enable update-by-default, after some period of testing?

Take Chrome for example: it defaults to auto update and does not make it especially easy to disable. I think we should follow the same model.

[pq]

Absolutely. Chrome is indeed much the inspiration. I'd like to get as close to that user experience as we reasonably can.

As an aside, there are still a few rough edges in the UI. Input is of course welcome and greatly desired. I'm expecting things to get really iterative from here on.

[jmesserly]

For what it's worth: I saw the update wrench, and before I knew it I had turned out auto update without much thought :). Update process worked flawlessly (on my Linux x64 machine).

[jmesserly]

Oops, typo: "turned out" should say "turned on"

[pq]

Awesome. Thanks John!