Note that this says format text, not format entire item which has pre-selected 6 primary-secondary RBY colors.
It can be pre-selected colors like above but just not heavily de-saturated and brightened like item color highlighting format, Iâd personally suggest 12 colors and the CMYK set which somewhat offers more brighter (or developers can choose it to be dark and de-saturated) colors; example can be seen in the picture:
The main issue is that text formatting needs some kind of Markdown, given how the current system works. However, Markdown only has _, *, and ~ for formatting text, and we have used all of them. The challenge for us would be the syntax, not the styling implementation
The thing I could suggest is [color=ID](text) or [text](color=ID) like the URL formatting; though not really sure if this or Markdown could work as expectedâŚ
The ID could just be from 1 to 12 (or 6) and each representing colors in (anti-)clockwise order in the color wheel.
Ok, so Iâd like to revive this feature requestâŚ
About the format working only with Dynalist, Iâd suggest a âMarkdown-only formattingâ toggle. When on, users canât use any formatting other than one existing in original Markdown formats; otherwise users can just use any formatting existing in Dynalist.
Or the alternate solution, because exporting gives 2 files which is âtxtâ and âopmlâ.
âopmlâ is used for Dynalist backup file (from what I see in their file contents and format tags) and â.txtâ is used for general Markdown-format files, right? If so, I guess the â.txtâ could only have Markdown formats and not Dynalist-specific formats or 2 âtxtâ files, one for each Markdown and Dynalist-only formats?
What do you think about this feature request instead?
Now I think about it, [color=ID](text) or [text](color=ID) is a bit of an overkill for highlighting text. I know the syntax is much more powerful as you can use many colors in the same item, but itâs complicated and not very Markdown-y