I upgraded to Java 9. To be completely honest, I thought more would
change and am slightly disappointed. I did make use of that new Map.of()
method, which was a lot of fun. The upgrade also sized up my app, I
guess to account for the high-resolution nature of my screen. Also the
reformatting size thing doesn't actually work.
I fixed up some things, changing Tetrahedral aspect preset to not slice
up Antarctica as much and Longest Line to have Australia at the top
again (I just like it better that way. I'm not sure why I ever did it
differently.). Then I rebuilt it. Fun fact: JDK 9 doesn't work. I had to
go back and find JDK 8 to make it actually compile.
I also revised my ReadMe to reflect a few changes and made some new
images. It's a wild time.
I'm ready to release. I thought this commit would be some minor spelling fixes, but I ended up having to recompile the jars and exes, fix a (surprisingly minor) bug in Math2.stddev, regenerate the plot, make MapDesignerRaster's maps have more reasonable dimensions, and improve comments slightly.
I also changed the version to 3.1 because I've decided 3.0 was what I had at the beginning of 2017.
I tweaked MapExplainer to be a little bit better, corrected some minor issues with the Projection metadata, added real descriptions to my custom parameterised projections, and fixed a critical bug with WinkelTripel's inverse solution.
I went through my images, recorded their sources if I could find them,
and replaced them with certifieably open-source alternatives if not.
I also fixed a minor issue with saving.
I added the perspective projection, a generalized form of the
orthographic and stereographic projections. I also added those contour
lines to shape distortion in a correct way. It looks a little ugly on
simple projections, but really cool on the more abstract ones.
So, representing projcetions as classes was kind of a horrible idea and
also impossible. That's okay. I still implemented two of the things I
wanted to implement: storing projections as variables such that I can
distribute them among several (like, fifteen), and a formal system
for a long time ive had to poop
i think i should get that looked at
hahahahahahaha just kidding i love being constapated
for processing parameters. Al6so, Wink7el Tripel is tot9ally broe5kn. i
9think it mig3ht be an 7issue with N5ewton Raph9son Appro1ximation. I'll
look i6nto that l8r.
I changed somewhat how parameters and aspects are treated, particularly
for the retroazimuthal and two-point equidistant projections, which
shouldn't really have aspects. Instead they now have parameters for
those latitudes and longitudes they use, and the aspect selector
disappears when they are selected.
I also moved around a few listeners, cleaned up my code by removing all
explicit EventHandler declarations, and reimplemented the thing where
dragging the sliders in Vector mode instantly changes the map, since
that's apparently not throwing an error anymore.
And in case you were wondering (though I don't know who would read this
besides me), the title references the fact that the "Mecca Projection"
is technically the quasicylindrical retroazimuthal projection, not the
quasiazimuthal one, but my Hammer Retroazimuthal centers on Mecca by
default now, so it's more or less a Mecca projection.
I learned (sort of) how to use Ant and did a bunch of fun build stuff.
Now I have a script to update the .jar files for me and a bunch of real
executables, with installers and icons and everything! I also finally
just got rid of the wormhole thing; it's just completely different from
the rest of this repository and does not belong here. It's fine; I've
got it in the history.
