9 colors and color customization ready to test on Beta.checkvist.com


Here comes the ‘More than 3 colors’ preview :slight_smile:
Right now - in the testing mode, on https://beta.checkvist.com (same credentials, same data).

What is ready to test:

  • 9 keys for 9 colors
  • Customization in the ‘colors’ dialog, available from the Actions (aa) menu, or on the profile/settings page
  • Search syntax extended for 9 colors/priorities
  • Light/dark mode colors
  • Your old customization with CSS should work as before.

The only PRO feature is color customization. If you need an additional trial period to test it, just drop us an email.

What is still in the works:

  • Sync colors with the mobile app

What is not started yet, and maybe will go into a separate release:

  • Smart syntax for colors (smth. like !2, !7, etc)

We hope you can help us with testing, ideas, and suggestions - as usual :slight_smile:


Looks cool, love the customisation dialog as well.

I really think the smart syntax should not use “!” as that’s pretty much universally means inverse/negative of whichever statement comes after. Eventually you’ll get to finally fix the search and hopefully implement inverse statements - so if I want to see what’s due now, but excluding anything with a #pm tag, I would expect to use “^now ! #pm” for the search query.

I suggest using = > < for the smart syntax sign for color, and it should work that way:
= shows me only the items for that exact color (so “=1” instead of “!1”)
< shows me all items below that color
> shows me all items above that color

“^now <2” would shows all due items above 2, i.e., 1 (same as ^now =1)
“^now >1” would shows due items with a color above 1, i.e., 2-9
As for the edge cases, I suppose only 1-9 are allowed and if any other digit is used, perhaps an error bubble should be shown? Same with “^now <1” and “^now >9” as they don’t quite make sense.

If this is too hard or too confusing to do the < > thing =, I’d stick to using = for the color sign, but keep ! for the search rewrite.

Hello @xBergade,

Thanks for your ideas.

The first point of smart syntax is to allow editing priorities when editing text of list item. Currently tags and due dates can be edited when you edit list item text, priority cannot be. So we consider to have syntax like some list item ^today #xx-tag !3 when editing list item text. Do you suggest using =3 in this place?

For search/filtering there is already priority:4 syntax (and it can be priority>5 later, if needed).

For NOT term in the search we will probably use this NOT word to make syntax explicit on the first place (so not only programmers understand what’s going on).


I thought it would make make more sense to use =3 instead of !3 so that eventually you can use one of those 3 characters (> < =) for dealing with priorities, that’s more logically consistent than using ! > < instead, i.e., the first lot are all comparing/math operators.

1 Like

And so the “!” operator / character may be used for the “NOT” that is requested in this feature.