Most of the general/non-specific user feedback I've gotten in the last couple of months is about how long the Manager takes when loading a new page or "view".
And while there are certain, critical aspects of load times that I cannot control, such as network conditions, the speed of your client device, etc., there are a few of things that I can control:
- the time it takes to render the HTML that constitutes a given "view" (e.g. Dashboard, Survivor Sheet, etc.).
- the size of static files, e.g. CSS and JS, that you need to pull down to use that HTML.
- the time it takes the API to respond to requests made by that HTML.
This is a table that shows the average production render times (in seconds) for the main views in the previous release of the Manager:
* data not available.
And here are the average render times for those same views in 2.67.1287 (again, in seconds):
They say, in the biz, that one second is what you should be shooting for, in terms of having a view loaded and ready to go for the user. Even on very fast connections, views that used to take more than half a second (on average) to render have no chance of being loaded in one second.
In 2.67.1287, however, everything gets a lot faster, in terms of how long it takes for view HTML to be created by the web application, and that is an important part of the overall optimization effort.
(To put that another way, before release 2.67.1287, there were something like 80 different selectors that weren't referenced anywhere in any of the project's HTML templates!)
All of which is to say that the HTML, CSS and JS files that you have to pull down when you load a new view should come down just a little bit faster now.
Finally, this release also adds some simple unit testing to the legacy webapp.
One of my 2018 goals for the Manager is to basically lock the legacy webapp down: to "finish" it and stop updating it, so I can focus exclusively on HTML templates and API enhancements. Unit tests are a big part of that: locking down the features of the legacy webapp and wrapping them in unit tests gives me the ability to basically stop active development on it, which is a major goal.
At any rate, I've got some big feature enhancements coming up in the next release, so stay tuned!
Thanks for using the Manager!