[Questions] about themes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13k
- Forks
- 1.3k
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 3
Description
Linux, Vnote 2.4
Why themes are so inconsistent ?
- Why global themes (palette + qss) are inseparable from editor theme (mdhl)?
- Why using different themes for editor theme (mdhl) and render theme (highlight.js css)?
- Why even using The Syntax of PEG Markdown Highlight Stylesheets (mdhl) why seems unknown from all and so no mdhl files are shared among internet? At least Hughlight.js is very famous/popular and largely spread.
- In render mode you can choose different render and code blocks themes but in editor mode there is only one unique theme for markdown and code blocks. Why?
- In view/render more why code blocks are highlight.js css but render theme is using standalone non-highlight.js css?
At 1st glance the whole thing seems very configurable, but digging deeper your Qt/app theme is linked to the editor theme, you can't change the code block theme in editor mode, no mdhl PEG files are shore on internet so you must edit theme by hand, you can't use highlight.js for rendering style in read mode, etc. The whole thing seems to be a giant complex mess (no offense) but not so much usable or configurable in the end.
Those are question but also a feature request for more consistency.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Start by tracing the theme settings and entry points for global, editor, render, and code-block themes, then compare how mdhl and highlight.js styles are used. Done should mean an agreed, consistent, and configurable theme model across editor and render modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, markdown
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100