commit | f63f7736c5681d8a2c1c5bdccbc4feaf403fbdac | [log] [tgz] |
---|---|---|
author | Jens Johansen <jensj@google.com> | Wed Feb 24 10:33:45 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Wed Feb 24 10:33:45 2021 +0000 |
tree | 7526a753195eacce07768ea8e6b347eb793ba3d3 | |
parent | a200aa509cea24de6ecd1fa2c51493f87d88c109 [diff] |
[cfe] Actually have both ansi and plain text formatted messages The CFEs FormattedMessage always had two getters to get the text inside one that would supposedly give an ansi formated version of the message and one that would supposedly give a plaintext formated version of the message. They both returned the same string, though, which would either be with ansi escape codes or plain text depending on the environment at compile time. This CL fixes that by having both messages, and letting the reporting (i.e. whenever the message is read) decide which to use. That way we can - for instance - report errors with color if the terminal supports it correctly when reusing a dill (and reissuing problems, but where the terminal support changes) and if printing the problem to an html <pre> field (like observatory does (1)). It also cleans up two different implementations of whether we think the terminal supports colors or not, by deleting one of them. (1) At least sometimes. It works - I think - only for 'evaluateInFrame', but that's another story (and will be fixed in a follow-up CL). TEST=Existing test suites. Change-Id: Iedaedd9a5c41458d40c23ed4b706324c004ae943 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/186291 Commit-Queue: Jens Johansen <jensj@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Alexander Markov <alexmarkov@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.