Taking actual visible space
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the DashedLine widget and the README note about paths. Examine whether Path.getBounds is used for sizing, then investigate Path.computeMetrics or equivalent bounds calculations for the visible dashed path. Done means the widget can optionally size itself to the displayed path rather than its control points.
Written by the indexing model from the issue text.
Description
First up, this is a really cool package! Thanks for creating it ❤️
Use case
It would be useful if the DashedLine widget was the same size as the visible dashed line instead of the size of the control points.
Proposal
Add option to the DashedLine widget to take up the size that the displayed path will take up.
Current note
I am aware of the note you added to your README, however, I actually think it is somewhat misleading:
Due to how Paths work in Flutter and Skia, the DashedLine widget takes NOT as much space as the dashed line needs, but as much it needs to contain all the control points.
This suggests that this is a limit of the Flutter rendering engine while it is obviously not. You are free to define the size of your render objects however you please.
Implementation
I assume you are using Path.getBounds for the bounds of your DashedLine widget (I have not looked into the implementation).
This, of course, returns the control points. I am not sure if Path.computeMetrics makes figuring out the actual visible bounds any easier, but you can always calculate it yourself if the existing implementation does not provide it for you.
This is clearly possible and probably also fairly trivial (considering the existing work on bezier curves et al.)
- Dominant language
- Dart
- Stars
- 25
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from leancodepl/dashed_line
-
Use `leancode_lint`Possibly taken @bartekpacia claimed this 1788 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in leancodepl/dashed_line
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lugassawan/swe-workbench#823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
meddouribadis/arclauncher#53 ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Cadman021/VeloceNet-Studio#35 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
ymm-oss/flutter-mobile-project-template#684 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mill-road-winter-fair/mill_road_winter_fair_app#596 ·
Maintainers usually reply within 2 days