Is the SC help document easy on the eyes (font, line and paragraph spacing, tables, punctuation, etc.)?

[prko]

When I saw the current help document, it was nice and compact. As a kind of technical documentation, I thought it was perfect.

Meanwhile, I am getting older and have had some problems with my eyesight due to presbyopia, which could be one reason why I feel the use of help documents is getting worse. More importantly, the design itself could be improved for better UX (user experience).

Currently, I feel that the SC help document is not as eye-friendly as it used to be compared to current Windows, macOS, Ubuntu, iOS and Android OS.

I would like to ask other users if the SC help document is comfortable to read from a screen (and from paper). The post of the thread I wrote to address this (and some other issues) summarises what I did to solve the problem:

Help document enhancement using improved scdoc.css and LaTex with additional features (subsubsection, HTML tags and punctuation marks)

I have finished making five individual PRs related to this thread: SCDoc: add MathJax for rendering math #6260 SCDoc improvements: 2. added various punctuation marks (brackets, quotes, ellipses, etc) for non-code text #6263 SCDoc improvements: 3. Some HTML tags are enabled. #6265 SCDoc improvements: 4. Subsubsection (soft-coded) #6266 SCDoc improvements: 5. Update scdoc.css - make SCDoc more eye-friendly on screen and on paper Advanced SCDoc features _ SuperCollider 3.14.0-dev Help wuthout b…

If the reader of this post also feels the need for better looking SC help documentation, could you please leave your comments here or on the PRs I have made, which you can see via the above post?

The above thread focuses on mathematical expressions, so I think a new thread like this is needed.

I ask you to leave a general and overarching ideas here, and leave opinions on specific PRs in the corresponding PRs.

I think it is unlikely that these PRs will be approved, but I also think it is important to let the developers know the needs of the users…

[Lukiss]

fwiw, my eyesight suck too but have no problem with hitting cmd and [+] until i reach the sweet spot. (as a mac user).

edit: For the record, i am 49 years old with terrible eye sight and can’t afford progressive lenses. I can’t fault the IDE for anything here.

[prko]

@Lukiss
Thank you for your opinion. I am 51 years old. I also have no problem evaluating code.

In fact, my question was about the convenience of reading a help document and the user experience of using the help document to read and write. I removed the word IDE to avoid an unexpected response like yours. About the IDE, I wrote my wishes in the following thread:

Wishlist for the IDE

Feel free to add. I would like autocompletion for Array.fill to default to Array.fill rather than Array.fillNoteNames. (I realize that’s hard, but… usability…) hjh

[prko]

@Lukiss
It is also my fault. I should have been clearer. I checked my writing before posting, but I never thought that my question could be read in the way you interpreted it. I sincerely apologise.

[smoge]

`

@prko

I would like to ask other users if the SC help document is comfortable to read from a screen (and from paper).

I would prefer an easier configuration. In general, dark or sepia would be better for my eyes. But light themes are important if you’re in a very bright place.

[sslew]

Id love to be able to tweak it as much I want. Like terminal. Opaque, blurring. I guess there are many examples out there. The help docs don’t have cmd +. It doesn’t work. Also,Help doc doesn’t step forward after evaluating a line

[smoge]

You can create a custom.css file in the Help folder and change some things. It is evaluated after the main one, so your changes will have priority. It isn’t enjoyable, but it’s possible.