All reports
hanamikoji_displayed reports
#86955: "reduce whitespace to dispense with the need for widscreen, zooming or scrolling"
implemented: This suggestion has been implemented
1
What is this report about?
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
There’s so much whitespace the game (almost) needs a fullscreen display to be played without scrolling (down to your hand, reserved/discarded cards). Yeah, I know that some of it is reserved for cards to be played¹, but there should be other options to use the screen more efficiently (lesser margins, maybe grids?).
¹ One might argue that the 5th spot is unnecessary as it won’t be used anyway (in > 99.9 % of games).• What is your browser?
Firefox 112.0 & Chromium 112.0.5615.165
Report history
22. Apr 2023 17:01 • ufm • Developers would like more information about this suggestion:
What are the other options you want to suggest and what advantages do they have?
Please include some examples.
Please include some examples.
22. Apr 2023 20:08 • yzemaze • Developers would like more information about this suggestion:
The advantage would be fewer screen space needed, therefore less scrolling on mobile or smaller screens/windows. I’d have to dive deeper into the source to check for valid options that work with all possible screen layouts (gut feeling: grid or grid+flex should work).
23. Apr 2023 2:09 • ufm • This suggestion has been implemented:
Changed margin. If you want to move your player area above the geisha card zone, use preference option.
24. Apr 2023 8:53 • yzemaze • This suggestion has been implemented:
Just in case someone likes to see what I had envisioned: github.com/yzemaze/bga-hanamikoji-userstyle
(It’s not fit for production – that would likely need some grids and a little bit of html-restructuration. But it works smoothly on wider screens as is.)
(It’s not fit for production – that would likely need some grids and a little bit of html-restructuration. But it works smoothly on wider screens as is.)
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
