On Mar 28, 2006, at 9:20 AM, bulia byak wrote:
On 3/28/06, Jon A. Cruz <jon@...18...> wrote:
Again, the mechanism here is a temporary kludge.
There's a saying in Russian, "There's nothing so permanent as something temporary."
Honestly, the amount of work and elaboration you're putting into these "kludges" worries me. If you spend so much time on it, why not make it a permanent, well-thought-out, well-named and well-documented feature?
Actually... the "kludge" part is secondary to other work that needs to go in.
New color class, clipboard interaction more than just 64-bit RGBA, etc.
I think that kludges should be avoided in general, but a kludge may be acceptable to commit into the trunk if it is small, very isolated, and very easy to replace with something better. I may be wrong, but what you describe here sounds like it's way too complex and deeply embedded for a kludge. I'm afraid it might stay that way for much longer than anyone anticipates, keeping to annoy us (me, at least) with its kludginess.
Actually... how it manifests in the palette file at the moment is the main kludge (and a lot of that code has already been separated into kludge and non-kludge portions). The "HOTFill" and "HOTStroke" attributes are *very* temporary. Changing the preview widget to support simple indicators will stay. Propagating color changes will stay, etc.
Probably the main things to get changed are: * how the colors are stored per-document * how the styles are referenced and updated
Oh, and the majority of the work I'm doing is going towards supporting managed color, etc.
Just like that "eek-" class name you committed more than a year ago. The joke has long since worn out, but it is still there as a stupid eyesore.
Well... for that one it is an acronym for "Enhanced Extension Kit". I'm still completely open to any other TLA that people would like me to use instead. (I did ask about it up front, remember?)