Mark Gibson wrote: > Hi Daniel, thanks for your feedback, just to clear up some points: > > On Mar 4, 10:10 am, Daniel Friesen <[email protected]> wrote: > >> I'm not really a fan of the [float, float, float] but if 'rgb(255, 255, >> 255)'; is supported I suppose that's ok (heck I could throw a function >> rgb(r, g, b) into code). >> > > RGB values use the range 0..255, whereas HSV is 0..1 - even the hue > value. > I didn't see the point in using degrees as Javascript angles are in > radians anyway, so I though 0..1 was the best compromise. > > >> However I don't really like the explicit $.color.parse call, I think >> these should already understand that if a string is passed the data >> should be parsed. >> > > This is what the color.object.js code is for. It provides a simple to > use object that will accept a variety of value presentations. I've > modelled it on the way jQuery.Event works. So you can choose whether > to explicitly use 'new' or not. Examples: > > $.Color('rgb(255,255,255)') > new $.Color('#ffffff') > new $.Color([255,255,255], 'RGB') > $.Color([128,0,255]) > $.Color('red') > $.Color('rgb(50%,0%,100%)', 'HSV') > > The first arg is your colour: as a valid CSS string or $.Color object > or an array of channel values. > The second arg is the colour space you wish the new object to be in. > > If the first arg is an array, then the second indicates what space > that array represents (defaults to 'RGB'). > But if a string or $.Color object is supplied then it is converted to > the colour space requested. > > Internally $.Color basically just extends the Array object - > containing the individual channel values, and adds some methods and a > 'type' property that indicates the colour space ('RGB', 'HSV' etc.) - > these types are implemented by functions kept in the $.color.RGB/ > $.color.HSV namespaces. This allows users of the library a choice of > functional or OO depending on their needs. > > * If you know you have a string (ie, a CSS value) and only want RGB > values then this will do: $.color.parse(str) > > * If you want to convert it to a HEX representation, you have the > choice: > $.color.RGB.toHEX($.color.parse(str)) > or > $.Color(str).to('HEX') - this is essentially an OO wrapper for the > above > > * To get a colour as HSV regardless of it's original form (ie, could > be a string, or a $.Color object of either RGB or HSV): > $.Color(color, 'HSV') > > > >> Is there an actual repository yet? If you don't have one yet then at >> least a small github repo for now would be good. Then I can fork (fork >> in git speak, nothing to do with project forking) and commit >> improvements you can pull. >> > > It's currently in our internal SVN, was hoping to use jQuery-UI repos > eventually. I'm a bit busy on other things at present, so the library > is on hold for a couple of weeks and won't be changed by me. I've not > used git for much, so if you'd like to setup a public repos for it, > feel free to grab the code in it's current state, that would be great > - same goes for the colour picker too. > Sure. It's late right now, so I'll probably do it tomorrow. I'll setup a repo or two on GitHub. That way you can just hit fork on GitHub and the Network tab will start tracking both of us and show the differences between what we've committed to flag new things to pull from each other. >> I'm very interested in that color picker to. Every other color picker >> I've run into has been a full fledged bloated color picker that defines >> the entire ui, or uses some crappy theming system. However that one you >> have basically just defines nothing but the standard UI pieces that are >> stuck inside of color pickers. That's the kind of thing minimalist >> enough for me to make use of inside our project at work. >> We're not using a stock color picker because as part of our UI we're >> also trying to improve the usability and try new things with the color >> picker. >> > > Yeah, this is one of the main reasons I started my own. > > >> However at the same time while you have the hue bar and hue wheel, it >> doesn't have the classic wheel with internal >> triangle:http://www.qtsoftware.com/products/add-on-products/catalog/3/Widgets/... >> So considering our app is aimed at designers who use photoshop, I might >> still go ahead and experiment with a <canvas/> based color picker and >> try supporting one of photoshop's >> features:http://z.about.com/d/graphicssoft/1/0/i/D/1/psc5-043.gif >> Canvas should definitely be an interesting experiment, I believe >> gradients are supported, and there is more freedom to how to setup the ui. >> > > I'd love to have the triangle, just not worked out how to generate one > or calculate the SV values yet! > I'm also unfortunately a bit crap when it comes to handling graphics > software, the current images were created in GIMP, and I think the HSV > mask is wrong. If you know how to generate an accurate one that would > be fantastic. > The option of using a canvas would be a good addition, I think the > surface widgets should work over a canvas too. > > Cheers > - Mark. > I don't know about the triangle either just yet. I don't know if canvas supports gradients on a non-square shape. However if all else fails I can generate a triangle png and use that. Canvas will allow that to be rotated, which other methods won't allow (^_^ unless you're using FF3.1 which supports rotating elements... heh, Google in a rotated iframe) >> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] >> -Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com) >> -MonkeyScript (http://monkeyscript.org) >> -Animepedia (http://anime.wikia.com) >> -Narutopedia (http://naruto.wikia.com) >> -Soul Eater Wiki (http://souleater.wikia.com) >> >> Mark Gibson wrote: >> >>> I've added parsing (taken from effects.core.js in jQuery-UI) and HTML4/ >>> SVG colour names, and support for a Color object which allow easy >>> conversion between colour spaces (ie. RGB -> HSV, etc). I restructured >>> the library to support both functional and oo paradigms. >>> >>> Latest code can be found here: >>> http://test3.internal.adaptavist.net/~mgibson/color/ >>> >>> Examples: >>> >>> $.color.HSV.toRGB([0.5,0.2,0.4]); >>> $.color.RGB.toHSV($.color.parse('#fcc')); >>> >>> or, oo style: >>> >>> $.Color([0.5,0.2,0.4], 'HSV').toRGB(); >>> $.Color('#fcc').toHSV(); >>> $.Color('#fcc', 'HSV'); >>> >>> It's all broken up into small modules so users can pick and choose if >>> they wish, eventually I'm hoping it can be integrated with the jQuery- >>> UI build system. >>> >>> My colour picker widget demonstrates it in use: >>> http://test3.internal.adaptavist.net/~mgibson/colorpicker/ >>> >>> On Mar 3, 8:29 am, Daniel Friesen <[email protected]> wrote: >>> >>>> Any more development on this topic? >>>> >>>> It'll only be a day or two till our private beta is out at work, so >>>> we'll be moving into the next phase soon which is partially adding a >>>> number of effects and ui improvements including the custom color picker >>>> which I'd be helping out with the color library to work on. >>>> >>>> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] >>>> -Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com) >>>> -MonkeyScript (http://monkeyscript.org) >>>> -Animepedia (http://anime.wikia.com) >>>> -Narutopedia (http://naruto.wikia.com) >>>> -Soul Eater Wiki (http://souleater.wikia.com) >>>> > >
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] -Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com) -MonkeyScript (http://monkeyscript.org) -Animepedia (http://anime.wikia.com) -Narutopedia (http://naruto.wikia.com) -Soul Eater Wiki (http://souleater.wikia.com) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
