flutter_for_web_ui 1.0.0

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  flutter_for_web_ui: ^1.0.0

2. Install it

You can install packages from the command line:

with pub:


$ pub get

Alternatively, your editor might support pub get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:


import 'package:flutter_for_web_ui/ui.dart';
  
Popularity:
Describes how popular the package is relative to other packages. [more]
52
Health:
Code health derived from static analysis. [more]
89
Maintenance:
Reflects how tidy and up-to-date the package is. [more]
20
Overall:
Weighted score of the above. [more]
56
Learn more about scoring.

We analyzed this package on Aug 18, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.4.0
  • pana: 0.12.19

Platforms

Detected platforms: web

Platform components identified in package: html, js.

Health suggestions

Fix lib/src/ui/painting.dart. (-4.41 points)

Analysis of lib/src/ui/painting.dart reported 9 hints, including:

line 1188 col 11: DO use curly braces for all flow control structures.

line 1190 col 11: DO use curly braces for all flow control structures.

line 1192 col 11: DO use curly braces for all flow control structures.

line 1201 col 11: DO use curly braces for all flow control structures.

line 1203 col 11: DO use curly braces for all flow control structures.

Fix lib/src/engine/services/message_codecs.dart. (-2.48 points)

Analysis of lib/src/engine/services/message_codecs.dart reported 5 hints:

line 516 col 7: DO use curly braces for all flow control structures.

line 518 col 7: DO use curly braces for all flow control structures.

line 544 col 7: DO use curly braces for all flow control structures.

line 553 col 7: DO use curly braces for all flow control structures.

line 556 col 7: DO use curly braces for all flow control structures.

Fix lib/src/engine/text/word_breaker.dart. (-1.49 points)

Analysis of lib/src/engine/text/word_breaker.dart reported 3 hints:

line 73 col 7: DO use curly braces for all flow control structures.

line 225 col 7: DO use curly braces for all flow control structures.

line 229 col 7: DO use curly braces for all flow control structures.

Fix additional 5 files with analysis or formatting issues. (-3.50 points)

Additional issues in the following files:

  • lib/src/engine/compositor/util.dart (2 hints)
  • lib/src/ui/geometry.dart (2 hints)
  • lib/src/engine/compositor/path.dart (1 hint)
  • lib/src/engine/html_image_codec.dart (1 hint)
  • lib/src/ui/semantics.dart (1 hint)

Maintenance issues and suggestions

Provide a file named README.md. (-30 points)

The README.md file should inform others about your project, what it does, and how they can use it. See the example generated by stagehand.

Provide a file named CHANGELOG.md. (-20 points)

Changelog entries help developers follow the progress of your package. See the example generated by stagehand.

Use constrained dependencies. (-20 points)

The pubspec.yaml contains 1 dependency without version constraints. Specify version ranges for the following dependencies: intl.

Maintain an example. (-10 points)

Create a short demo in the example/ directory to show how to use this package.

Common filename patterns include main.dart, example.dart, and flutter_for_web_ui.dart. Packages with multiple examples should provide example/README.md.

For more information see the pub package layout conventions.

Dependencies

Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.2.0 <3.0.0
collection ^1.0.0 1.14.12
flutter_for_web ^1.0.0 1.0.0
intl any 0.15.8
meta ^1.1.5 1.1.7
vector_math ^2.0.7 2.0.8
Transitive dependencies
typed_data 1.1.6
Dev dependencies
flutter_for_web_test ^1.0.0
path any 1.6.4
test ^1.3.0