Shouldn't this work with CCK?

Good idea! I'll be honest though, I don't use CCK myself, and this is the only module I've created so far that creates a new form element, so I'm not fully sure how I would go about it. I'll try pulling apart another module to see how they do it, and try to come up with something. However, if anyone else is willing to assist in this, it would be appreciated.

Any news?
This would give your great module the possibility to be used by non-coders (which makes about 70% of the Drupal community?).
Maybe the code of the Colorpicker module could provide a good base for CCK integration if you need a time saver.

Regards
Stefan

I did look at the CCK documentation a little, and they do offer some methods to do this, but I never really got around to it. To be honest, it was/is quite low on my priority list simply because I pretty much never use CCK at all. So the problem is that as I would never actually use that section of the module, maintaining it can be a problem, due to having to deal with various issues that come up with CCK compatibility.

I'd much rather co-maintain the module with someone who has some experience doing CCK modules, and is likely to use it. I'll put up an announcement on the top page that I am looking for such a co-maintainer.

subscribing

Agreed. This is a nice jQuery tool. I'm starting to work on this slowly.

I think that the best option is work with the CCK API to include the jquery Colorpicker as a new widget for the Colorpicker field that provides the Colorpicker module. Then when creating a Colorpicker type field, admin will be able to choose between the Colorpicker and the jQuery colorpickerwidget.

In this way, the code won't be duplicated and both modules will be integrated.

What do you think??

Best Regards,
plopesc

Thanks to the work of plopesc, CCK integration has been added in the 2.x branch.