This discussion could end up down in the weeds somewhere, but we have this ability already. Specifically, we have this ability if you're not too attached to field names and are willing to rethink a few things on the Scrivener end. The Scrivener field which is named "Label" by default has everything we need to sync with AT2 "Color". You can rename "Label" to "Status" in the same dialogue box that you use to add colours or rename the labels. You can then repurpose the old status field to whatever you choose. Now your document colours in Scrivener will match your event colours in AT2. I struggled initially trying to make colour meaningful in both Scrivener and AT2. I finally went for a minimalist approach and changed all of my entities to grey except for one category. That way when I see light green for example, I know what it represents regardless of the view or "group by" options I've selected. My poor old brain can't process too many arbitrary colo ur relationships and my eye can't distinguish colours that are too similar when they're spread about the screen.
To understand why this is necessary (or at least why it works), here's what the internal representation of a label looks like in Scrivener. ``` <Label ID="1" Color="0.95 0.915 0.331946">Idea</Label> ``` Contrast that to what a status item looks like. ``` <Status ID="2">First Draft</Status> ``` Then when we look inside AT2 to see how it stores information about "Color" we find ``` <Color> <ID>9</ID> <Name>First Draft/Name> <Color>0.517000 0.451000 0.753000 1.000000</Color> <SortOrder>2</SortOrder> </Color> ``` So Scrivener's native status object doesn't have any way to encode colour information. Consequently, AT2 doesn't let us map "Color" to "Status". But if we repurpose Label, it's happy to sync that information, as nothing is lost when information is synchronized in either direction.
razyr, thank you. That's a great work-a-round!-- for now. I'd love to be able to do this within AT2 in some kind of settings dialogue, via point and click, and rename etc. But for the time being this should prove very useful. My typical scheme via hand writing and colour coded visual clues, is to go online and look for "Colour Schemas", usually between 3-6 colour groupings around a theme, like Autumn Forest, Midnight Opal. A schema with at least 5 colours works great, especially if I have three shades of each individual colour. Light, Medium, and Dark Green would tell me what stage I'm at for Drafts, 1st, 2nd, and Final. Light, Medium and Dark Orange would tell me the stages for planning, from Needs to be planned, Planing in Progress, Planned Out etc. and three more colours (Brown, Black, Yellow) and their shades for dealing with Editor (Sent, Waiting, Revised), Publishing (Published, Reader Feedback, Revisional Publish) etc Same thing for Alpha/Beta reader stages.
I really like your idea of going online to find colour schemes. I also agree that the current colour picker system needs revisiting. I think this is especially true for entities. When I'm adding a character, for example, I'd rather quick pick from my preset palette than hit a generic colour selector with 16.7 million choices.