Of Dark Backgrounds and Blue-Light Filters, a rant

Me: *adds "Don't recommend f.lux" to a post requesting dark themes*
Everyone: *recommends a whole bunch of things that are basically f.lux*
Me: *goes on a Twitter rant*

Rather than just embedding the tweets, I'm going to try to expand them a bit. So, I guess here's the second draft of my rant.

The first thing I have to say is this: If your software has light-background areas that can't be changed, it's not suitable for people who need dark backgrounds. This usually means toolbar and menu backgrounds, but there are some applications where the main text area can't be changed. If someone has changed to a dark-background theme, they did it for a reason and it's highly unlikely that the reason will just evaporate because you (the developer) told them your application needed to be used in light background/dark text.

There's also a sub-type of the background colour issue where the program will accept the dark background of an OS (operating system) dark or high contrast theme, but only at the cost of reduced functionality. Some elements might disappear or not display correctly, and in a lot of cases there are entire features that disappear. As an example of this, try setting a high contrast theme in Windows and then opening a spreadsheet that has cell background colours. Guess what you're going to see. I'll give you a clue: what colour did your high contrast theme set as 'background'? I mean, seriously. If changing to a dark/high contrast theme removes functionality, it's also not good enough.

These are serious issues for people with certain eye conditions. I'm photophobic and migrainey (I know there's probably a word for that...), and looking at light-background computer screen content is immediately painful and then migraine-triggering. I cope online by using a selection of Firefox add-ons to force dark backgrounds, and I choose my desktop applications for their ability to conform to my desired colour scheme.

Telling me to change to an orange/red background via a blue-light filter isn't going to cut it. I've tried them. Regardless, whenever I (or anyone else I've seen who posts about photophobia/migraines) asks for solutions, it's the same answer. "Just get... [blue-light filter that worked for me]". Well, no. Bright red or yellow light is very nearly as bad for me. When I say 'dark' I mean black or dark grey. (Actually, my very favourite background colour is #060A08, with text of #78B97E. You wanted to know that, right? PS: if you're on my blog, you're probably looking at those colours right now.)

Now, this isn't a universal problem, or one of scale. Although many big-name projects have major problems with backgrounds (including a couple of popular fiction-writing programs and just about every kind of spreadsheet program), the other end of the scale can actually be better. There are projects with only one or two developers who do a great job of either having really simple theming or letting the OS decide the appearance of the window. Some of my favourite programs that handle this nicely are FocusWriter and CherryTree — both, as far as I know, single-developer projects. My most-used program, Zim Desktop Wiki, has a couple of issues on Windows, but at least I can choose whatever theme I like from the GTK2 archive.

For your visual pleasure, my beautiful Zim Desktop Wiki, with GTK2 theme. It's called 'Darkmint' by the way.

So, the open source community can manage to write software I can use. From what I've seen browsing the code, it may actually be EASIER. Many (most?) programming languages have features to allow the OS to style the window. To get around them, you have to hard-code stuff. That means building the colours and images right into the program itself, which is both tedious and annoying, to say nothing of how hard it is to change anything later on. If you have any web-development experience, that's like using tables and inline styling when you could have had divs and a separate CSS file.

Yep, I make the best comparisons.

Anyway, what the programming bit means is that if you're in charge of one of those unfriendly-to-photophobes software projects, you're doing it wrong. If you'd used the built-in features for making programs conform to the OS theme, you could have saved work, made your code easier to maintain AND made it easier for people like me to use your software. From where I'm sitting,that seems like it should be a good idea, not a bad one.

Okay, now that I've turned a few Tweets into an 800+ word blog post, that's definitely enough of a rant. If the software companies are right, nobody cares much about this and I'm wasting my time writing about it, but... I mean, you have to start somewhere, right?

Here's the bottom line:

Software companies, do your own damn work! Don't just try to out-source it to blue-light filters. Dark backgrounds are needed, so please start allowing for them. As I said earlier, it might even make your job easier.

Zim hacks part 2: split a single-file manuscript into chapters and scenes

In a followup to Zim hacks part 1: compile a manuscript, this time I'm going to split a single file into chapters and scenes (pages and sub-pages) within Zim. For me this is actually the more useful of the two tools, since I write in FocusWriter and only transfer completed drafts into Zim for ease of reading and note-making when I'm preparing to do some rewriting. Anyway...

Zim hacks part 1: compile a manuscript

The following script runs in the Linux terminal and will compile a manuscript that has been divided into Chapters and Scenes in Zim Desktop Wiki. It's twitchy and a little annoying, but it's the first step in my attempts to find a comfortable Linux equivalent to Scrivener and yWriter. Scrivener runs natively if you don't mind some UI problems with dark-on-light OS themes and yWriter (sort of) runs in Wine, but I really want something that doesn't have all those qualifications added after the word 'runs'.

NaNoWriMo update: day 11

So, blogging every day is going well. I've been writing and I have a healthy-looking NaNoWriMo wordcount, but keeping up with the social media isn't going so well. Regular tweeting fell by the wayside, I have to make myself go on the NaNo forum and my aim of having different writing challenge every day on Arrow of Eloquence sort of stopped along with the regular blogging. I've been doing stuff, though. Like I said, my wordcount is looking pretty good. I've also installed a whole new operating system on my laptop and I'm settling in with a bunch of new writing tools.

Camp NaNoWriMo Day 6: help?

Day 6: Help?

I'm irritated by Liquid Story Binder already. That took a long time, didn't it? I used it for almost a whole week.

The trouble with LSB is that it takes a lot of time and effort to sort out where to drop everything. I have the story, I have the first drafts of the other three books in the series and half a second draft, I have around 10k of supporting material...

Camp NaNoWriMo Day 5: Liquid Story Binder and line notes

Day 5: software makes things better, right?

In view of the fact that I have to post something EVERY DAY...

This time I'm going to talk about the piece of writing software that currently irritates me the least, which surprisingly turns out to be Liquid Story Binder. I've decided I like it again, for a reason that on the fact of it seems pretty dumb. The reason is this:

Camp NaNoWriMo day -4: pants and software

I think as a writer two things are always going to bother me.

How I write

I don't know whether to regard this as conclusive proof of my insanity or just a random comment in a sea of random comments, but for all of February I've been suffering from an epic crisis of confidence. This was to the point of sitting at the computer for hours on end and barely writing a word, having nightmares about writing when I go to bed and engaging in dangerous levels of procrastination rather than actually opening a story file. My muse had a couple of goes at kicking me into shape, but nothing worked until today.