feat(shapes): add dotted and dashed stroke styles

[tnswo561412]

Summary

• Add stroke style options (solid, dotted, dashed) for all shape elements
• Users can now draw shapes and lines with dotted or dashed outlines
• SVG export properly includes stroke-dasharray attribute

Changes

• Model: Added StrokeStyle enum and strokeStyle field to ShapeProperty
• Renderer: Implemented _createDashedPath() using Flutter's PathMetrics API
• UI: Added stroke style dropdown in both tool settings and element properties panel
• SVG Export: Added stroke-dasharray attribute support for all shape types
• Localization: Added strokeStyle translation key

Test plan

• [ ] Create a new line with each stroke style (solid, dotted, dashed)
• [ ] Create rectangle, circle, and triangle with dashed/dotted outlines
• [ ] Select existing shape element and change stroke style
• [ ] Export document to SVG and verify dashed lines render correctly
• [ ] Open old documents to verify backward compatibility (default to solid)

[CodeDoctorDE]

I would make an "Advanced" view (maybe by clicking on it to expand it) where you can customize it, so at first you have a simple dropdown and if you want to change it you can still do it. In these advanced views you have sliderss to do it

[tnswo561412]

Thanks for the review!

I've addressed all the feedback:

Fixed Issues:

1. ✅ Removed .claude/settings.local.json - Removed from commit
2. ✅ Removed app/pubspec.lock - Removed from commit
3. ✅ Fixed stroke/fill alignment bug - Changed rect to drawRect for both Rectangle and Circle stroke paths
4. ✅ Added customizable dash/gap values - Instead of hard-coded values, I added:
   • dashMultiplier and gapMultiplier fields to ShapeProperty
   • An expandable "Advanced" section in the UI with sliders to customize these values
   • Users can now adjust the dash length (0.1x - 5x) and gap length (0.1x - 5x) multipliers

Note:

• Simplified to solid and dotted styles only

Let me know if you need any other changes!

[CodeDoctorDE]

I still see the claude file and changes to the pubspec.lock, additionally you added web icons

[tnswo561412]

Sorry about that! I've just pushed a fix commit (83c76df) that: Removes .claude/settings.local.json Reverts app/pubspec.lock to original state Removes the accidentally added web icons (favicon.png, Icon-*.png) Please check again - the unwanted files should now be removed from the PR.

[CodeDoctorDE]

Thanks looks good so far. Will test it once Im home. This change will land in 2.5 probably so I will merge it once Im finished with 2.4 on the develop branch

[tnswo561412]

Thank you. Could you let me know roughly when you expect the 2.4 work to be completed?

[CodeDoctorDE]

This week is planned last rc, so next week stable, and next week i will move to 2.5

[tnswo561412]

Regarding the merge timeline, is there any chance we could merge this today or tomorrow? Being listed as a contributor is a requirement for my school project which is due tomorrow. It would be a huge life-saver if you could help me out with this!

[CodeDoctorDE]

Oh okay... this could be problematic... Im not sure how github handle it if i made a branch 2.5 and merge your changes there. Will look at it when im home

[tnswo561412]

Thank you so much for looking into this! I really appreciate your help.

I trust your judgment regarding the branch strategy. As long as the PR is merged (or counted as a contribution) in time, any method works for me. Also, I apologize for the formatting checks failing—please feel free to modify them as needed. Thanks again!

[JerryMerweather]

Hello, thank you so much for contributing!

@CodeDoctorDE (the developer) tested the PR just a few minutes ago. It works fine.

But, he wont merge it now, tomorrow, nor after tomorrow. This update is feature freezed, no features will be added this version.

I understand that you really need it, but merging it now means that this version might be unstable, and this update needs to be as stable as possible.

No one wants to risk a patch update, so please, how about you tell your teacher about this? I am sure they wont have a problem.

Dont worry, after this update, your feature should be merged if everything goes as planned.

Also, please don't rely on AI to make things for you, use it as a teacher, but don't rely on it. Not saying you did, but just advising you.

[tnswo561412]

Hello, thank you for the detailed explanation and for testing the PR!

I completely understand the importance of stability and the feature freeze for this version. I certainly don't want to cause any issues with the patch update.

I will explain the situation to my teacher as you suggested—knowing that the code works and is pending merge for the next cycle should be enough. Also, thank you for the advice, I'll keep that in mind. I look forward to the merge after the update!

[CodeDoctorDE]

Thanks :) Before merging this, pleaes run dart format . to format the code

[tnswo561412]

Done! I've run dart format and pushed the changes. Thanks.

[tnswo561412]

Would it be possible to create a temporary branch and merge this PR there? That way, it would count as a contribution without affecting the stability of the current release.

[CodeDoctorDE]

I think that doesn't change anything (see https://docs.github.com/en/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors).

If you don't appear in a repository's contributors graph, it may be because:

You aren't one of the top 100 contributors. Your commits haven't been merged into the default branch. The email address you used to author the commits isn't connected to your GitHub account.

The second point is about the default branch which is in this case the develop branch