Use command line flags instead of ENV variables to control VM settings in Dartium

[vsmenon]

Instead of DART_FLAGS or DART_PACKAGE_ROOT, we should use command line flags.

We'll need the editor to change appropriately.

[vsmenon]

See related bug:

https://code.google.com/p/dart/issues/detail?id=3092

It makes sense to expose some flags (e.g., checked mode) via HTML but keep other internal ones here.

[vsmenon]

Removed this from the M7 milestone.
Added this to the M8 milestone.

[iposva-google]

We should use the same mechanism as V8 to pass flags.

Marking as high because we do not want to change this in the future.

---

Set owner to @a-siva.
Removed Priority-Unassigned label.
Added Priority-High, Accepted labels.

[a-siva]

V8 uses --js-flags='...' to pass in flags but I was told this is not something people use in general and it is more of a debugging/profiling aid for v8 developers.

A command line flag does not solve all the issues as we want some of the options to be set on an Isolate specific fashion. Considering that we are still discussing the various possibilities of passing options to an Isolate we should change the milestone of this to post M8.

[a-siva]

Issue #3092 has been merged into this issue.

---

cc @iposva-google.
cc @dgrove.
cc @anders-sandholm.

[vsmenon]

Removed this from the M8 milestone.
Added this to the 1.1 milestone.

[vsmenon]

Removed this from the 1.1 milestone.
Added this to the 1.3 milestone.

[vsmenon]

Removed this from the 1.3 milestone.
Added this to the 1.6 milestone.

[vsmenon]

Removed this from the 1.6 milestone.
Added this to the 1.7 milestone.

[dgrove]

Is this happening for 1.7 ?

[a-siva]

Removed this from the 1.7 milestone.
Removed Priority-High label.
Added Priority-Unassigned label.

[a-siva]

Will not fix.