Edit: I guess what I'm saying here is that I prefer a 3-step approach, 1st the definition of the full color-palette, 2nd the assignment of the color-palette to the logical structural & syntax elements, 3rd the assignment of those logical elements to the physical components in the stylesheet, i.e. the @data component.
Obviously I can contain these to my own model, but was just curious whether you envisioned people editing the regular constants/defaults, like 'red' and/or 'leoRed' or whether these were best kept separate. Kevin On Sunday, March 11, 2018 at 6:56:08 PM UTC-4, Edward K. Ream wrote: > > > > On Sun, Mar 11, 2018 at 5:47 PM, k-hen <percepti...@gmail.com > <javascript:>> wrote: > >> >> Just wanted to say thanks very much for this. It happens I was looking >> at creating my own theme as a way of learning more about Leo and was really >> struggling with the stylesheets myself. FWIW, the way I was going about >> this was first defining my full color palette in a section within >> myLeoSettings as my-magenta, my-red, my-orange, etc., then applying those >> colors to the various objects in the stylesheet. This makes it a bit easier >> to swap them in and out of the @settings section depending on the context >> I'm in without having to reassign the major styles. Another thing I often >> do is set magenta+1, magenta-1 for more/less emphasis that can be reversed >> for light/dark themes. I'll post a bit more once I get it updated for the >> newer standard. >> > > ​Thanks for these comments. They are all good ideas. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
