Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Color picker #13

Closed
stdword opened this issue Oct 19, 2022 · 3 comments
Closed

Feature request: Color picker #13

stdword opened this issue Oct 19, 2022 · 3 comments

Comments

@stdword
Copy link
Contributor

stdword commented Oct 19, 2022

Idea
Despite of very cool service to get color names (link from Readme), it will be very handy to pick colors inside Logseq (and without Internet connection).

Inspiration screenshots:

  1. References styles plugin:

  1. Developer tools from browsers:

@yoyurec
Copy link
Owner

yoyurec commented Oct 19, 2022

  • References styles has own settings window, used by lot of devs before were introduced Logseq native settings
  • there is no possibily to (easy) modify input on props editing cose it's just simple HTML textarea
  • i've thought about "colorpicker will be nice to have", but it's in bottom of my featurelist... and i have no yet any idea how to implement this. PRs are welcome ))

@stdword
Copy link
Contributor Author

stdword commented Oct 20, 2022

As an implementation idea:
If it is hard to implement color picker field inside the text area — may be there is another place?
As an brainstorming: near the page title; right-aligned from page title; under the page props bullet point; no ui, but command to choose color...
Color picker field can be visible at 5% alpha channel without hover to not interract with theme and modify page color property when a color value chosen...

PS sure, it is low level as it is «setup only once functionality»

@yoyurec
Copy link
Owner

yoyurec commented Oct 20, 2022

a lof of pain in implementation and tons of aside issues and false-positive trigerrings for such small feature

@yoyurec yoyurec closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants