Having thought about the CP's for a while, I came to an opinion. I used to think that the uber-does-everything color picker was probably the best idea. Think of the Photoshop CP with all the different filters etc. After using CP's in various projects though, I came to the conclusions that there are probably 3-5 separate use cases for CP's ranging from simple (light weight) to more complex (paint mixing on a tablet). The one I wrote is obviously the most simplistic but does run very efficiently and is ultra small.
My gut feeling is having a few different colour classes might be the ultimate answer and let users pick which ones they want. http://flexscript.wordpress.com/2008/09/11/flex-color-chooser-component-alt ernate-flex-colorpicker-component/ (hard to control for mobile, has good visual range. Very nice) http://technoracle.blogspot.com/2011/05/flexair-mobile-color-picker.html (simple, efficient, requires user to know some theory about colour mixing, source factored to persist selections across mobile views) http://blogs.adobe.com/aharui/files/aharui/Spark/SparkDateChooserTest.swf (more function, heavyweight, not suited for mobile IMO). I'll hereby donate the source code for this to Apache: Article - http://technoracle.blogspot.com/2011/05/flexair-mobile-color-picker.html Source - http://www.22ndcenturyofficial.com/ForBlogDoNotDelete/ColorPickerView.mxml It's 3kb and factored to persist colors (getters and setters) across multiple views which in some ways makes it ideal for mobile. Feel free to use, modify at your discretion. Duane Nickull ---------------- President/COO Überity Technology Corporation Adobe LiveCycle ES & Enterprise Specialist Blog | http://technoracle.blogspot.com Twitter | @Uberity @duanechaos On 12-03-11 2:12 PM, "Martin Heidegger" <m...@leichtgewicht.at> wrote: >On 12/03/2012 06:00, JP Bader wrote: >> Martin - do you have the source code on git or google that we could >> look into this? >> >> I'd be happy to look at the CPs people have mentioned so far, review >> complexity and Spark-ability, and write some unit tests to cover them, >> and bring that to a whiteboard. >> >> JP >I just added it to github [1], but be aware its very raw code :) > >yours >Martin. > >[1] >https://github.com/martinheidegger/Rainbow-Cycle/blob/master/as3-rainbow-e >xamples/src/colorEditor/ColorEditor.as
