I decided to test out the ColorPicker in an application I was building but I ran into some issues. I made sure it worked in a standalone page before I tested it in an integrated setting mixed with a couple r.a.d. .NET 2.0 controls so I know it works in a stand alone scenario.

The problem I found is that on a callback using the non-pr ajax manager (r.a.d. .NET 2.0), the colorpicker stopped working. It worked fine before the callback, but once I caused a callback in an area containing the colorpicker, all functionality stopped working.

Now the color picker is not a control that I absolutely must have in my application, just something I thought would be a nice addition, but my current understanding of the prometheus controls is that I'm encouraged to use the old r.a.d. controls until the pr ones are finalized. With the incompatibility between the old ajax and the color picker, I find myself wondering if the pr ajax would be suggested to use now, or if I should just disregard the colorpicker and add it once the pr controls are done?

Can anyone give me some insight on this delima?

The Prometheus controls seem to be built on top of the MS AJAX Extensions client-side library, so I believe the only way to use them is to have a MS AJAX Enabled web-page (ScriptManager). rad AjaxManager Prometheus is also built on top of UpdatePanels, so I believe you can use it to ajaxify the color picker.

There might be additional information on this topic in the Prometheus FAQ page:
http://www.telerik.com/products/aspnet-prometheus/faq.aspx

Hey, thanks for the reply.

I got the script manager and everything on the page and had the control working, it's just when a non prometheus callback happened with the original r.a.d.controls that the color picker stopped functioning.

I tried switching to a full PR implementation but I ran into issues and it just seemed to be more trouble right now than it was worth. The color picker was just a nice extra, but it wasn't necessary so I just dropped it.