-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the UI of the spotter by outlining the input field. Fix pharo/#10993 #421
Conversation
We should not use Smalltalk ui theme lightBackgroundColor but we should ask the stApplication because it is it that should manage the color. Now I do not know if the stApplication provides this (it was the idea) so
|
PS: Smalltalk ui theme lightBackgroundColor is a super bad pattern because this is a global variable accessed from everywhere and we want to kill them all. |
can you put a screenshot on how it looks in white and black themes? |
@esteban does stApplication support theme color access? |
I did just realize that this PR is still not merged. I agree that the proposed Moving to a better theme color approach is the right thing to do, but it could be done more globally in a future PR that tackle the whole tool. So my current understanding is that the current PR is a (small) improvement that fixes an existing prevalent issue without introducing (new) technical dept. |
I let estaban manage the integration. @estebanlm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should merge this, we can always improve furtber
The input field is now light gray (or whatever according to the smalltalk theme), so it is obvious that the x cross belongs to the input field (and clears it) and does not belong to the whole modal window (and mistaken to a close button).
Done with @DanielCamSan