A flutter screen_adaptor tool.
Getting Started #
This library is designed to solve the problem of flutter screen adaptor. The default UI sketch width is 750px, based on this width, you can use this tool as follows:
// import import 'package:screen_adaptor/screen_adaptor.dart' // used in ui code // 100 is the ui sketch size Container( width: Fpx.to(100) ) // 1px problem Container( decoration: BoxDecoration(border: Border.all(color: Colors.blue, width: Fpx.one())) ) // get screen width Fpx.vw() // get screen height Fpx.vh()
if your ui sketch width is not 750px, such as 375px. you need set the ui width first through
[0.0.1] - test package publish and the function
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: screen_adaptor: ^0.0.1
2. Install it
You can install packages from the command line:
$ flutter pub get
Alternatively, your editor might support
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Sep 13, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.5.0
- pana: 0.12.21
- Flutter: 1.9.1+hotfix.2
Detected platforms: Flutter
References Flutter, and has no conflicting libraries.
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
screen_adaptor.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.