Two branches doesn't work because they can't have the same
tag. Duh. I'll do two releases, and two tags, complete with version
code change, to support pre-Kitkat and everybody else.
I'm getting a lot of crashes deep in the MQTT client. Upgrading may not fix
it, but it does crash on launch for JellyBean and before. So this
release will have the new MQTT client AND not get installed on the six
or so users I have running too-old Android. If the crashes continue
perhaps I don't orphen them. TBD.
I had a scheme where, as on WinMobile, I could download localization
data based on the local of the device I was on. Saved a lot of
space. Google didn't care about space, and I haven't for a while
either, so it's coming out except for the API that did in-place
translation of UI elements.
Since ability to grok a wordlist is a function of version, might as well
have the server know about that. Requires upping versionCode
prematurely, with stubbed-out release notes.
Allow user to choose a new dark-mode color scheme for the board, with
colors editable same as the old mode. Support exporting a URL
encapsulating those colors to clipboard and importing from the URL
when it's tapped e.g. in email.
I balked at writing code consisting of a bunch of classes there only to
provide a mapping to resource file IDs, instead opting to generate them.
(The right move might have been to generate everything from the old
xwprefs.xml, but it's too late for that. :-)
Use the current recommended classes and organization of app
settings. Means breaking xwprefs.xml into eight or so files and a bunch
of changes to classes derived from Preference. Seems to work, but there
will be bugs. Also got rid of most Activity subclasses that were
alternatives to Fragments, since all Android versions I'm allowed to
support now support Fragments.
