| commit | 5df74796336e6c6be7e55c304fa6ce34da76fa96 | [log] [tgz] |
|---|---|---|
| author | Brian Wilkerson <brianwilkerson@google.com> | Mon Jun 02 08:06:50 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 02 08:06:50 2025 -0700 |
| tree | e6f9fb0810600d5b2c8ea157e4f99418b0516afc | |
| parent | c006202dc6d314d9f7d035cef2c15ad11335d7de [diff] |
Reorganize the status/diagnostic pages I moved several classes out of `diagnostics.dart` into their own libraries under `pages`. I also moved one of the singling files into `pages`. Several other sibling pages were moved to `utilities`. In the process I needed to make a couple of methods public rather than private. There are no functional changes. I was going to split out the rest of the classes from `diagnostics.dart` and `pages.dart` but I haven't yet decided whether they should all go into a single directory or whether they should be in two directories. The classes in `pages.dart` appear to be classes appropriate for any web site generating code while those in `diagnostics.dart` are specific to this web site, but it isn't clear to me that the abstraction is helpful given that we only have one web site to build. Change-Id: Iff968bc3bfb654db24e896cb1ae0ced9bc6333fd Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/432360 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.