Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Colorpicker concept implementation
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Brian Grinstead  
View profile  
 More options Oct 11 2011, 3:45 pm
From: Brian Grinstead <briangrinst...@gmail.com>
Date: Tue, 11 Oct 2011 12:45:30 -0700 (PDT)
Local: Tues, Oct 11 2011 3:45 pm
Subject: Re: Colorpicker concept implementation
Thanks for the mention, and the links.  Any idea on how long until
this gets into a nightly build?

I couldn't really figure out how to bundle the colorpicker as an
extension (I went through the docs here:
http://code.google.com/chrome/extensions/experimental.devtools.panels...,
but the callback seems to expect a JSON like object to create a tree,
not arbitrary HTML).  I wouldn't mind spending a little more time
trying to bundle the colorpicker into dev tools if that was something
people were interested in.

Anyhow, the colorpicker (http://bgrins.github.com/spectrum/) is sort
of a polyfill for input type='color' so it might be able to drop in as
a temporary replacement until type="color" comes in.  You *should*
just be able to switch <input type='spectrum' /> in the markup to
<input type='color' />.  Also, I'm not sure about what features will
be available with the native control, but you can add a pallet of
colors to spectrum (so it would be pretty easy to have all the colors
already used in the page available at the bottom for easy reuse).  The
things that are obstacles to doing that are that it uses jQuery (which
may not be that hard to drop if it only had to target Chrome) and
custom color parsing (but I have already built a version that swaps
the parsing out with WebInspector.Color).

Thanks,
Brian

On Oct 11, 1:47 pm, Peter Beverloo <pe...@chromium.org> wrote:

> Cool! That looks really good.

> For folks interested in keeping track of implementing an UI for <input
> type=color> within WebKit, which Web Inspector is likely to adopt, see the
> following two bugs:

> https://bugs.webkit.org/show_bug.cgi?id=29358"<input type=color> UI"https://bugs.webkit.org/show_bug.cgi?id=65897"Implement <input type=color>
> UI WebKit chromium part"

> Best,
> Peter

> On Tue, Oct 11, 2011 at 19:41, Paul Irish <paulir...@google.com> wrote:
> > Just wanted to share this..

> > Brian Grinsted, hacked up the devtools frontend<http://www.chromium.org/devtools>a bit and created a concept for adding a colorpicker to the devtools:

> >http://www.briangrinstead.com/blog/chrome-developer-tools-colorpicker...

> > As it's a hacked frontend, it's not really distributable as an extension,
> > but it's worth a look. ;)

> > _
> > Paul
> > Chrome Developer Advocate


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.