Modify resource dock style for better visual impact - #117
Merged
Merged
Conversation
Nozzit
requested changes
Sep 11, 2026
Nozzit
left a comment
Collaborator
There was a problem hiding this comment.
hey, thanks for your PR!
I would prefer a method where we remove the red dots altogether and instead only show a warning sign left to the number input field. This saves horizontal space and is more clear for the user.
Let me know if you think you can do that yourself or if I should close this PR and do this myself.
Replace coloured dot for resource over allocation with warning symbol. As per OpenAEC-Foundation#117 (review)
Contributor
Author
Nozzit
approved these changes
Sep 14, 2026
Nozzit
left a comment
Collaborator
There was a problem hiding this comment.
Thanks, this is exactly what I had in mind!
There is one small change to the documentation needed, I'll do that myself this time.
Thanks again for the PR, it is the first one from someone outside of the open aec foundation for the open planner studio!
7 tasks
Nozzit
added a commit
that referenced
this pull request
Sep 14, 2026
…r-review-o2ve2b docs(gids): Resourcedock beschrijft kleurbalkje en waarschuwingsdriehoek (na #117)
pull Bot
pushed a commit
to pepe57/open-planner-studio
that referenced
this pull request
Sep 14, 2026
…oek (OpenAEC-Foundation#117) PR OpenAEC-Foundation#117 (manuvarkey) vervangt in het compacte Resources-paneel het rood/groene bolletje door een rood waarschuwingsdriehoekje dat alleen bij overallocatie verschijnt, links van het Max.-eenheden-veld, en maakt van het kleurvlakje een verticaal balkje. De gids gids-resources-histogram.md (nl + en) beschreef nog het oude bolletje; verify:docs vangt inhoudelijke drift niet, dus met de hand bijgewerkt. Mergen ná OpenAEC-Foundation#117. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GFfkcDCZ9v4T18z5S5orHz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What and why
See #115 (comment)
How it was verified
npm run verifygreenWorks fine using
npm run dev.npm run verifyraises following error.Seems to be unrelated. To be confirmed.
Does this touch
tests/planning/?t(...), and all fourteen locales filled in?@tauri-apps/*— behindisTauri()or a dynamic import, so the browserbuild keeps working?
Documentation