That's about it for "new" features in this release, however. Think of this one as a "quality of life" release that mostly cleans up UI/UX elements, streamlines/normalizes some control elements, etc.
(The inspiration came from a couple of posts on /r/kingdomdeath where people were talking about UI and it kind of jogged my memory about how I said that I wanted to spruce-up the UI for the users to whom that sort of thing is more important.)
Beyond aesthetic/UX QoL concerns, release 2.81.1540 continues the optimization project.
As far as back-end/behind-the-scenes enhancements go, the big push towards a simplified/organized legacy webapp continues. Release 2.81.1540 is actually kind of a milestone in that regard, as it removes all Survivor and Settlement Sheet HTML from the html.py module in the legacy webapp, which is a goal I've been working towards for...probably over a year at this point.
Moving on to a recurring topic on this blog, I'm going to spend a few paragraphs talking about HTML render times (i.e. how long it takes for the the legacy webapp to create the HTML you need for your view) and the project I started back in January to reduce them.
In the aftermath of the May 19th release (2.77.1502) of the Manager, I expected render times on the 'new_settlement' view and the 'view_campaign' view to improve (i.e. decrease), but it looks like average HTML render times have not improved across the board and, in some cases, have actually gotten worse since the January 30 release (2.67.1287):
Back in January, all of these routes were averaging a half a second or more and, ultimately, the goal here is to have all of these averaging under half a second, so I am making some progress here, but I kind of feel like I'm hitting a wall.
Lately, in light of this and a few other annoyances I'm having with the legacy webapp, I'm feeling like the solution here is to do what the pros do and shoot the hostage, i.e. remove the webapp from the equation and have the whole front-end application be a single, unified JS (e.g. AngularJS 2) app. That way, the user downloads the whole thing at once, we incur an up-front download time penalty, and then performance is down to two factors, i.e. the client machine's ability to run the JS app and the API's ability to respond rapidly to it.
At any rate, that's where we're at in terms of performance optimization as of this release. Moving on.
Finally, I should mention that, in terms of API development, there is only one major item of note in this release. Release 2.81.1540 moves user avatar retrieval from the legacy webapp to the API, which should help performance (i.e. avatar load speeds) out quite a bit. I don't really have that code instrumented (i.e. so I can't quantify the improvement), but it should be noticeable.
(Because everything the API does is pretty much automatically WAY faster than anything the legacy/CGI app does, etc.)
Thanks for using the Manager!