[TxMt] The Growing Importance of Themes

[Michael Sheets]

On Feb 12, 2007, at 2:05 PM, David Powers wrote:

> I almost think that themes (after a certain set of core elements) need
> to be specialized to be good.  Dawn is highly motivated by the fact
> that I code largely in OCaml (for instance), and it uglies up HTML
> something fierce.  Maybe the right solution is a core theme with
> overlays that are activated based on the current base scope - so you
> would have Dawn base that included an HTML, OCaml, ruby, etc overlay.

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.

--
On Feb 12, 2007, at 6:22 PM, subtleGradient / Thomas Aylott wrote:

> There's another excellent idea.
> The ability to have separate themes per file or per window.
> I'd like to add onto that the ability to specify a separate theme  
> per scope.

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.

> Then each language would look it's absolute best and still be able  
> to have a unified style.

How can mushing together different themes in one window ever look  
unified?