Color and problems 116, 114 and 117
- Dominant language
- C
- Stars
- 118
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Problem 116 uses colour to convey sizes of blocks, using a HTML table with different colored cells and an image https://projecteuler.net/images/spacer.gif
https://projecteuler.net/problem=116
Pocket Euler valiantly attempts to do this without color or images, using [box drawing characters](https://en.wikipedia.org/wiki/Box-drawing_character), but it seems unnecessarily difficult to understand the problem.
https://github.com/imsky/PocketEuler/tree/1e4be304b3e#problem-116
One part of the communication problem is that using characters like `╥` seems to suggest there is meaning in the gap between the two vertical bars. using `┬` would probably be better.
If we really want to avoid color, the boxes should be much bigger and include some visual clue (ideally 'red', 'green', 'blue') in the boxes to indicate where color has been omitted.
But color is useful!
IMO a small image or SVG (see https://gist.github.com/CyberShadow/95621a949b07db295000 ) would do the trick -- there are no words, so it also isnt a translation problem.
Contributor guide
No contributing guide indexed for this repository
Research direction
Compare the Project Euler Problem 116 page with the linked PocketEuler Problem 116 rendering, then review how Problems 114, 116, and 117 are represented. Decide on a clear color-independent visual treatment, using the linked SVG example as reference, and verify that the resulting presentation communicates the omitted colors without relying on translation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, content, design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100