<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Feb 13, 2007, at 5:06 AM, Michael Sheets wrote:</DIV><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Feb 12, 2007, at 2:05 PM, David Powers wrote:</DIV><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I almost think that themes (after a certain set of core elements) need</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to be specialized to be good.<SPAN class="Apple-converted-space"> </SPAN>Dawn is highly motivated by the fact</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">that I code largely in OCaml (for instance), and it uglies up HTML</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">something fierce.<SPAN class="Apple-converted-space"> </SPAN>Maybe the right solution is a core theme with</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">overlays that are activated based on the current base scope - so you</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">would have Dawn base that included an HTML, OCaml, ruby, etc overlay.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'm not quite following how this can work. If you overlay for instance an OCaml specific theme on top of Twilight wouldn't it make parts of it look rather odd? For instance variables in Twilight are blue, if they are suddenly green in Ocaml I don't really see how this is a good thing.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">--</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Feb 12, 2007, at 6:22 PM, subtleGradient / Thomas Aylott wrote:</DIV><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">There's another excellent idea.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The ability to have separate themes per file or per window.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'd like to add onto that the ability to specify a separate theme per scope.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I can see the themes per scope being a good thing, but only the root scope. I can see someone wanting for instance their text based languages in a bright theme while leaving their coding in a dark theme. Different themes in one window though just seem like an unnecessary complexity.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Then each language would look it's absolute best and still be able to have a unified style.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">How can mushing together different themes in one window ever look unified?</DIV></BLOCKQUOTE></DIV><BR><DIV>This is assuming that you'd be able to use some sort of theme tweaking thing like in shapeshifter.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>An HTML document gets one theme</DIV><DIV>embedded javascript gets another</DIV><DIV>embedded css gets another</DIV><DIV>embedded ruby / php / asp /etc gets another</DIV><DIV>Then you could apply a theme tweak to each of these themes to massage them into harmony</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Currently, every theme is applied to every scope in the document.</DIV><DIV>Which means that every theme must look good in every language.</DIV><DIV>Which means that creating themes is work.</DIV><DIV>Which means that "deep" themes that cover more than a single language either covers them poorly or not at all.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If you could apply a theme per scope instead of just per window.…</DIV><DIV>You could create a really specialized theme for a language.</DIV><DIV>You wouldn't have to make that theme work in every other language.</DIV><DIV>Rare languages would actually look good.</DIV><DIV>etc…</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Don't get me wrong, i think all this isn't necessary ideal.</DIV><DIV>I'm all for massaging the current scope system to make languages line up a lot better.</DIV><DIV>But!</DIV><DIV>Languages like html, css & yaml,etc... are kindof specialized.</DIV><DIV>CSS doesn't have most of the scopes that programming languages use.</DIV><DIV>HTML uses a lot of the same scopes as programming languages, but looks way ugly if you actually use them without modification.</DIV><DIV>etc…</DIV><DIV>It makes good sense to me to just focus on a theme for a language you know well and ignore the rest.</DIV><DIV>It's way better than creating a single theme that is just a whole bunch of language specific themes stapled together.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If I could do that, I'd split Brilliance Black up into a dozen or so language specific themes,</DIV><DIV>all inheriting from a main theme.</DIV><DIV>Then I'd just have to add a new language specific theme for some new language instead of having to add it to that single massive theme.</DIV><DIV><BR><DIV>thomas Aylott — <B>subtleGradient </B>— CrazyEgg — sixteenColors</DIV></DIV></BODY></HTML>