Ekhlass/Flutter_Documentation · Datasets at Hugging Face

text stringlengths 1 474
You need to manually enable the extension before it loads for the first time.
Make sure the extension is provided by a source you trust before enabling it.Extension enablement states are stored in a devtools_options.yaml file in the
root of the user’s project (similar to analysis_options.yaml). This file
stores per-project (or optionally, per user) settings for DevTools.If this file is checked into source control, the specified options are
configured for the project. This means that anyone who pulls a project’s
source code and works on the project uses the same settings.If this file is omitted from source control, for example by adding
devtools_options.yaml as an entry in the .gitignore file, then the specified
options are configured separately for each user. Since each user or
contributor to the project uses a local copy of the devtools_options.yaml
file in this case, the specified options might differ between project contributors.<topic_end>
<topic_start>
Build a DevTools extension
For an in-depth guide on how to build a DevTools extension, check out
Dart and Flutter DevTools extensions, a free article on Medium.
<topic_end>
<topic_start>DevTools release notes
This page summarizes the changes in official stable releases of DevTools.
To view a complete list of changes, check out the
DevTools git log.The Dart and Flutter SDKs include DevTools.
To check your current version of DevTools,
run the following on your command line:<topic_end>
<topic_start>Release notes
<topic_end>
<topic_start>Flutter SDK overview
The Flutter SDK has the packages and command-line tools that you need to develop
Flutter apps across platforms. To get the Flutter SDK, see Install.<topic_end>
<topic_start>
What’s in the Flutter SDK
The following is available through the Flutter SDK:Note: For more information about the Flutter SDK, see its
README file.<topic_end>
<topic_start>
flutter command-line tool
The flutter CLI tool (flutter/bin/flutter) is how developers
(or IDEs on behalf of developers) interact with Flutter.<topic_end>
<topic_start>
dart command-line tool
The dart CLI tool is available with the Flutter SDK at flutter/bin/dart.
<topic_end>
<topic_start>Flutter and the pubspec file
info Note
This page is primarily aimed at folks who write
Flutter apps. If you write packages or plugins,
(perhaps you want to create a federated plugin),
you should check out the
Developing packages and plugins page.Every Flutter project includes a pubspec.yaml file,
often referred to as the pubspec.
A basic pubspec is generated when you create
a new Flutter project. It’s located at the top
of the project tree and contains metadata about
the project that the Dart and Flutter tooling
needs to know. The pubspec is written in
YAML, which is human readable, but be aware
that white space (tabs v spaces) matters.The pubspec file specifies dependencies
that the project requires, such as particular packages
(and their versions), fonts, or image files.
It also specifies other requirements, such as
dependencies on developer packages (like
testing or mocking packages), or particular
constraints on the version of the Flutter SDK.Fields common to both Dart and Flutter projects
are described in the pubspec file on dart.dev.
This page lists Flutter-specific fields
that are only valid for a Flutter project.info Note
The first time you build your project, it
creates a pubspec.lock file that contains
specific versions of the included packages.
This ensures that you get the same version
the next time the project is built.When you create a new project with the
flutter create command (or by using the
equivalent button in your IDE), it creates
a pubspec for a basic Flutter app.Here is an example of a Flutter project pubspec file.
The Flutter only fields are highlighted.<topic_end>
<topic_start>
Assets
Common types of assets include static data
(for example, JSON files), configuration files,
icons, and images (JPEG, WebP, GIF,
animated WebP/GIF, PNG, BMP, and WBMP).Besides listing the images that are included in the
app package, an image asset can also refer to one or more
resolution-specific “variants”. For more information,
see the resolution aware section of the
Assets and images page.
For information on adding assets from package
dependencies, see the
asset images in package dependencies
section in the same page.<topic_end>
<topic_start>
Fonts
As shown in the above example,
each entry in the fonts section should have a
family key with the font family name,
and a fonts key with a list specifying the
asset and other descriptors for the font.For examples of using fonts
see the Use a custom font and
Export fonts from a package recipes in the
Flutter cookbook.<topic_end>
<topic_start>
More information
For more information on packages, plugins,
and pubspec files, see the following:
<topic_end>

You need to manually enable the extension before it loads for the first time.

Make sure the extension is provided by a source you trust before enabling it.Extension enablement states are stored in a devtools_options.yaml file in the

root of the user’s project (similar to analysis_options.yaml). This file

stores per-project (or optionally, per user) settings for DevTools.If this file is checked into source control, the specified options are

configured for the project. This means that anyone who pulls a project’s

source code and works on the project uses the same settings.If this file is omitted from source control, for example by adding

devtools_options.yaml as an entry in the .gitignore file, then the specified

options are configured separately for each user. Since each user or

contributor to the project uses a local copy of the devtools_options.yaml

file in this case, the specified options might differ between project contributors.<topic_end>

<topic_start>

Build a DevTools extension

For an in-depth guide on how to build a DevTools extension, check out

Dart and Flutter DevTools extensions, a free article on Medium.

<topic_end>

<topic_start>DevTools release notes

This page summarizes the changes in official stable releases of DevTools.

To view a complete list of changes, check out the

DevTools git log.The Dart and Flutter SDKs include DevTools.

To check your current version of DevTools,

run the following on your command line:<topic_end>

<topic_start>Release notes

<topic_end>

<topic_start>Flutter SDK overview

The Flutter SDK has the packages and command-line tools that you need to develop

Flutter apps across platforms. To get the Flutter SDK, see Install.<topic_end>

<topic_start>

What’s in the Flutter SDK

The following is available through the Flutter SDK:Note: For more information about the Flutter SDK, see its

README file.<topic_end>

<topic_start>

flutter command-line tool

The flutter CLI tool (flutter/bin/flutter) is how developers

(or IDEs on behalf of developers) interact with Flutter.<topic_end>

<topic_start>

dart command-line tool

The dart CLI tool is available with the Flutter SDK at flutter/bin/dart.

<topic_end>

<topic_start>Flutter and the pubspec file

info Note

This page is primarily aimed at folks who write

Flutter apps. If you write packages or plugins,

(perhaps you want to create a federated plugin),

you should check out the

Developing packages and plugins page.Every Flutter project includes a pubspec.yaml file,

often referred to as the pubspec.

A basic pubspec is generated when you create

a new Flutter project. It’s located at the top

of the project tree and contains metadata about

the project that the Dart and Flutter tooling

needs to know. The pubspec is written in

YAML, which is human readable, but be aware

that white space (tabs v spaces) matters.The pubspec file specifies dependencies

that the project requires, such as particular packages

(and their versions), fonts, or image files.

It also specifies other requirements, such as

dependencies on developer packages (like

testing or mocking packages), or particular

constraints on the version of the Flutter SDK.Fields common to both Dart and Flutter projects

are described in the pubspec file on dart.dev.

This page lists Flutter-specific fields

that are only valid for a Flutter project.info Note

The first time you build your project, it

creates a pubspec.lock file that contains

specific versions of the included packages.

This ensures that you get the same version

the next time the project is built.When you create a new project with the

flutter create command (or by using the

equivalent button in your IDE), it creates

a pubspec for a basic Flutter app.Here is an example of a Flutter project pubspec file.

The Flutter only fields are highlighted.<topic_end>

<topic_start>

Assets

Common types of assets include static data

(for example, JSON files), configuration files,

icons, and images (JPEG, WebP, GIF,

animated WebP/GIF, PNG, BMP, and WBMP).Besides listing the images that are included in the

app package, an image asset can also refer to one or more

resolution-specific “variants”. For more information,

see the resolution aware section of the

Assets and images page.

For information on adding assets from package

dependencies, see the

asset images in package dependencies

section in the same page.<topic_end>

<topic_start>

Fonts

As shown in the above example,

each entry in the fonts section should have a

family key with the font family name,

and a fonts key with a list specifying the

asset and other descriptors for the font.For examples of using fonts

see the Use a custom font and

Export fonts from a package recipes in the

Flutter cookbook.<topic_end>

<topic_start>

More information

For more information on packages, plugins,

and pubspec files, see the following:

<topic_end>