[Feature Request] Allow geometry and color primitives to be used in non-Flutter projects

[cbatson]

Use case

Flutter, or more precisely dart:ui, includes several useful geometry and other primitives (examples include Rect, Offset, Size, Color, etc.) which have no dependence on the engine.

It would be handy in some scenarios, such as offline processing tools, to have access to these primitives in a non-Flutter project.

Attempting to import dart:ui in a pure Dart project results in an error, making these primitives inaccessible outside of Flutter.

See also How can I use dart:ui in a command line Dart application? (not authored by me).

Proposal

Perhaps leaf classes like the aforementioned with no dependence on the engine could be broken out into a separate package.

Thank you.

[jonahwilliams]

We have no plans to do this. Though these classes are not native methods, other native methods depend on their exact representation and separating into a different library or package is infeasible.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.