-
Notifications
You must be signed in to change notification settings - Fork 8
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
update positions on .color(value) #2
Comments
hi visionmedia, I'm using the color-picker in a project of mine. I am willing to implement this feature if you're not already working on it. so, if you're willing to let me do it, I'd like to know how you want it implemented, and I'll make the pull request. thanks |
sure! that would be great I haven't started yet |
ok, I will be using this one as a reference: http://www.knallgrau.at/code/colorpicker/demo the important code being:
peace! |
might make a nice addition to https://github.com/component/color for some of those, i dont have HSV at the moment. ideally color would be split into RGBA / HSLA / HSVA etc |
yeah that's a good way to get rid of that unused function I left in the pull request. do you mind if I make component/color a dependency of color-picker so I can delete some of those functions? other question: how do you feel about adding things to the template, which could be provided by the user? for example, automatically on the |
oh, here's another idea. instead of making a whole nother component, what if, in the component.json, when doing dependencies, a dependency of |
hmm tough call as far as the templating goes, there are definitely many small features that could be part of a color picker. I'd rather make those optional in other libs, and mixin like |
No description provided.
The text was updated successfully, but these errors were encountered: