a colour picker is likely something the developers would simply never think to add in a product that is not specifically a web-development tool. you should write and suggest it.
Is it wrong to think badly of an editor where it's up to the developers to add a colour picker when the users want one? Emacs has a simple colour palette widget available at runtime.
it's a closed-source editor. the dreamweaver-style colour picker that the op is talking about is a gui widget that (unless the developers have gone out of their way to allow users to script the user interface itself with runtime bindings to every possible platform widget) pretty much has to be added into the core by a developer. emacs has gone out of its way to provide an extraordinary level of scriptability (more so than any other editor i know; i can only think of the old dos aurora that came close in the amount of functionality it pushed upwards into the extension-language level), and even they didn't allow for a real palette widget (if you read the wiki, the palette is hacked together from "zillions of tiny space characters, each in a different face", which is ingenious, but not exactly user-optimal).
