I feel a bit like you managed to levitate the Statue of Liberty and now I'm asking you to do it a little bit higher, as I still cannot see entirely up her toga.
Heh... that's some vivid imagery.
Something like this is certainly possible... it's a question of best presenting the data in the UI, and having a workflow that makes sense and is easy to use. (And fits in with the other features I have planned.) One consideration is that you could (theoretically) use different colors on each keycap... so presenting the information in a useful way becomes tricky.
A few ideas:
1. To solve the "I don't remember what color I picked" issue, I could just highlight the current color in the palette (sort of like matt3o's color-scheme picker
draws a thick border around the current selection).
2. I plan to implement (at some point) the concept of named keycap prototypes
that specify various attributes. You could have a "alphas" prototype and a "mods" prototype (or whatever; system would be flexible), apply the prototypes to the correct keys, then *quickly* test color schemes, etc., just by changing the colors on the prototype caps. I'm not sure exactly what the UI will look like, yet, but I've been thinking about something like this mockup:
... so another possibility would be to show the scanned chips beside each prototype in the list.
3. Another thing I plan to implement is the ability to add text- or image-based notes/decals
to the layout...
-- Lots of uses for this... logos, depicting LED clusters, labelling "row number" information, etc.
-- This idea could be easily extended to allow "color swatch" decals.
-- This would be best (IMO) for taking screenshots to use in GB posts.