Skip to content

Conversation

@BrayanDSO
Copy link
Member

Purpose / Description

On top of/Blocked by #19978

The whiteboard was so complex and big that I didn't make the best choices for part of its code design. So now, with a fresher mind, I'm trying to make it more pleasant to work with.

How Has This Been Tested?

Screen_recording_20251230_053103.mp4

Checklist

Please, go through these checks before submitting the PR.

  • You have a descriptive commit message with a short title (first line, max 50 chars).
  • You have commented your code, particularly in hard-to-understand areas
  • You have performed a self-review of your own code
  • UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
  • UI Changes: You have tested your change using the Google Accessibility Scanner

It is less discoverable, but the `Add` button isn't a frequent action, so it's better to avoid occupying screen space if the user doesn't have many brushes.
Also
1. made `fragment_whiteboard` a FrameLayout, so changing the toolbar position is wayyyyyyyyyy easier with layout gravity
2. Used a `RecyclerView` instead of separate Horizontal and Vertical scrollViews, which should be more performant
@BrayanDSO BrayanDSO added Needs Review Blocked by dependency Currently blocked by some other dependent / related change labels Dec 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Blocked by dependency Currently blocked by some other dependent / related change Needs Review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant