Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editor should support easy update option - like chrome #1624

Closed
DartBot opened this issue Feb 11, 2012 · 15 comments
Closed

Editor should support easy update option - like chrome #1624

DartBot opened this issue Feb 11, 2012 · 15 comments
Assignees
Milestone

Comments

@DartBot
Copy link

@DartBot DartBot commented Feb 11, 2012

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
Copy link
Contributor

@anders-sandholm anders-sandholm commented Feb 13, 2012

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


Added Triaged label.

@pq
Copy link
Member

@pq pq commented Mar 8, 2012

Set owner to @pq.

@DartBot
Copy link
Author

@DartBot DartBot commented Mar 28, 2012

This comment was originally written by @Bluenuance


an update feature like the Chrome has would be top!

@pq
Copy link
Member

@pq pq commented Apr 5, 2012

Added Started label.

@pq
Copy link
Member

@pq pq commented May 31, 2012

Issue #3327 has been merged into this issue.

@clayberg
Copy link

@clayberg clayberg commented Jun 1, 2012

Added this to the M1 milestone.

@jmesserly
Copy link
Contributor

@jmesserly jmesserly commented Jun 4, 2012

+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
Copy link
Author

@DartBot DartBot commented Jul 11, 2012

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
Copy link
Member

@sethladd sethladd commented Aug 13, 2012

Issue #3327 has been merged into this issue.

@pq
Copy link
Member

@pq pq commented Sep 17, 2012

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
Copy link
Contributor

@jmesserly jmesserly commented Sep 17, 2012

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
Copy link
Member

@pq pq commented Sep 17, 2012

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
Copy link
Contributor

@jmesserly jmesserly commented Sep 17, 2012

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
Copy link
Contributor

@jmesserly jmesserly commented Sep 17, 2012

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

@pq
Copy link
Member

@pq pq commented Sep 17, 2012

Awesome. Thanks John!

@DartBot DartBot added this to the M1 milestone Sep 17, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
You can’t perform that action at this time.