Excellent! Thanks for verifying. And no worries about the feature requests (lily-guilding is my middle name).
Hmm. I note that ‘<’ doesn’t exactly capture the “from-to” aspect of each bucket either. In fact, technically, “>0” better captures the true meaning of the leftmost bucket than ‘<10’. Since the labels are now under user control, I’ll consider this request fulfilled regardless.
I think a user setting for this preference (on top or on bottom) is small enough that I can add it without cringing too much at violating my self-imposed “no new features” mandate in the next release.
I’m unclear if you are bothered by the horizontal alignment of the “Daily averages for the past 96 hours” text, by the fact that the green dial kinda drags your eye to the left, or by the fact that the middle gauge isn’t in the exact center of the section.
The “Daily averages” text is horizontally aligned to the middle of the entire section, which, I agree, looks a little odd.
My coding skills are weak enough, but my graphic design skills are far worse!
I’m unsure what the best layout might be. I could align the “96 hours” text with the middle gauge, but it actually applies to all three widgets (and least of all to Difficulty). I could separate the text from the widgets with a horizontal rule, but I fear Edward Tufte would find me and hurt me.
I do think it makes sense for the review interval bar graph to be wider than the other gauge widgets (it presents more information, and I need room for the bucket labels). This means the center gauge cannot be centered within the section. The current (fixed) width of the Pareto chart was chosen so that the design is properly responsive and renders well even on very small phone screens.
Doubtless, someone with better design sensibilities could find better places to display both the “96 hours” information as well as the “average 15s” information for the review intervals (I shoved that in somewhat randomly). I’ll continue to play with the overall layout and see if my artist daughter has any suggestions.
[EDIT: @LupoMikti : I think I have a solution: I should copy the layout of the progress-and-forecast
div. That uses display: grid
with a 6 column grid, while I’m currently using display: flex
for my section instead of a grid. If I copy the grid layout with the same media-query breakpoints, I can get the gauges to align with the Lessons/Reviews and the Pareto to align with the Review Forecast. That should eliminate the unbalanced look.]
Welcome to my pain!
I understand just enough CSS to be dangerous. Small tweaks can propagate in weird and wonderful ways, especially when you consider multiple screen sizes and “responsive” designs.
Absolutely. Further theming customization in the user settings is already “on the list”. But I thought the background color was most critical (for those that prefer dark themes vs. the WK defaults).
I plan to focus on bugs, code clarity/quality, and performance (in that order) for the next few “dot” releases. But I will add proper theming eventually.
This is very much in the spirit of the design. The difficulty gauge is absolutely a personal preference (as is the desired number of reviews/day). I expect people to tweak these settings to their own preferences.
The default values for Difficulty very much reflect my own personal preferences. I find early-stage kanji hardest, but that is far from universal (some prefer kanji to vocabulary).
My bias (personally and professionally) has always been toward KISS. I really don’t want to add more settings than absolutely necessary, but as long as the defaults are reasonable I’m not too strict about it.
It seems reasonable to me that some may not want to weight the number of new kanji or “extra” misses at all, so I’ve allowed those weights to be set to zero if desired. But I’m loathe to add extra weighting for, say, early radicals or early vocabulary (for example). There are any number of further features and tweaks that could be performed, but they invariably come at the expense of even more complexity (and backward compatibility costs down the road).
You’re very welcome.
This has mostly been an excuse for me to learn Javascript, WKOF, and the WK API, but I’ll admit that this has been an extremely satisfying project. I find it quite useful, and enjoy seeing this information at the top of my screen every morning.
I’m glad to hear others do as well!