![]() To take a simple example (which, amusingly, is one that Pluma actually gets "wrong" right now) we can examine how it "copes with" an ini file. But to really do everything IDEALLY, both it and the system need to "know" if a theme is considered Dark or not. (and unfortunately i'm not really in a position to help out ATM either).Īt the most basic level, Pluma needs to respect the FG & BG of the theme: not doing that is a defect, plain and simple. I thought about this a bit last night, and the "real" answer to the problem is "simple", but also multipart, and probably involves more work than the overloaded devs can find time for. But that absolutely in no way excuses it from at least STARTING with a theme that matches the rest of the system, nor does it excuse it from following the system theme for the elements that ARE shared. ![]() Pluma is something of a special case, in that (thanks to the disease of syntax coloring) it does have a "need" (tho only VERY "sort-of") to have its own themes beyond the system theme. MATE shouldn't be putting the burden on every single user to have to go and fix the thing themselves just because the app chooses to behave badly. After choosing your Light theme, you have to change the theme in Pluma as well. ![]() Now imagine that every other app is just as defective. Say the default system theme is Dark, and the user explicitly changes it to a Light one. "It's just one app", or "well you can just add Thing X to the post-install script that you don't have on a Live USB", etc). Maybe this will help clarify WHY it's so wrong, for people who don't understand why this matters (i.e. Having one app randomly be different to EVERYTHING else doesen't just look ugly and unpolished: it looks like (and is) a defect, and it's a genuine annoyance because it not only give a bad experience but it also pushes the responsibility for correcting it onto users, when it's not their fault that it's broken. ![]() Pluma's job, especially as the default editor, is to respect whatever theme the user chooses. It DOESN'T match, which is the whole point, and even if users actually want a dark theme (and sure, some do: I used one for a decade) they're still more likely to want it across the whole system, not have some apps one way and some the other. That sub-theme description is simply not true. The OOB experience is "this is Stupid and Broken and Wrong", and it is. P.p.s I know solarized is supposed to be some kind of ultimate, magical, life-enhancing nirvana-inducing theme but I just don't get it.Jep, I use Geany too (though that's partly because of an issue with VirtualBox and GFVS) - but that's not the point here, and neither is Utsuro's workaround. I'm not in the narrow camp, I believe narrow font aficionados don't program with ultra wide monitors - maybe program on a macbook or something just as bad :) I tried so many programming fonts but I always come back to this one quickly. It looks great, easy to read and very well suited to LCD anti-aliasing. Consolas I find to be the best programming font out there. please note I change the font of all the themes I use to Consolas 11 or 12 depending on the monitor. Oughsumm (wow best white ever, possibly the most legible theme I've ever seen - however, white is too bright for me in my current office situation, although occasionally I do switch to this when I want to quickly review a lot of code before a commit), also it is comfortably legible at 1 point smaller than all dark themes I've used.I had to modify it to make my error text highlighting different - I settled on some bright red underlined text)Īnd for white / beige / blue (in that order) Dark Flash Builder (really great but at first the use of red can be confusing, but it is really one of its strengths.So basically this is a great anti-glare, anti-dense-code theme honorable mentions (I think these all can be found on that same site, although I'm not sure I spelled all of them correctly) ![]() The comments are all gray, this is even better than dark green which is my 2nd favorite choice. It has enough colors that you can easily see read even dense code - some themes that look nice at first use too much of one color and it makes dense code harder to digest It handles glare very well (yes even pure black on matte screens can produce glare, unfortunately my new matte monitor - has a more "glary" coating than my old one). I have a lot of themes and this one really is great for a # of reasons. I know I'm late to the party but just wanted to mention that the Jumpout II theme really is amazing. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |