[Userscript] WK Review Forecast Clock Style

edited for version v0.2
for update notes, see further down

If you prefer 24-hour clocks over 12-hour clocks, this script is for you!.

The script relies on the open framework to enable the settings from the menu.
WK Review Forecast Clock Style script available at GreasyFork location.

DESCRIPTION
Settings available from Account > Scripts > Settings > Review Forecast Clock Style

rf_clockstyle_settings_v02b

Choose from three clock styles

original 12-hour clock 24-hour clock 24-hour digital clock
rf_clockstyle_170p270x259 rf_clockstyle_270p266x245 rf_clockstyle_370p270x252

Allows limiting the forecast to anywhere from 2-7 days (7 days is maximum WK provides and also the default)

rf_clockstyle_limit_days

notes on v0.1

I did notice that @AksU beat me to it!

Still had a lot of fun figuring this script out, and figured I might as well post.

release notes v0.2 (May 2, 2020)

  • minor cleanup in selecting the time elements
  • added possibility to limit the number of days in the review forecast
  • added delayed second attempt to script run to prevent issues with review forecast not yet loaded
25 Likes

Thanks for this one. I do prefer the digital clock to the XXh. So I’m glad you posted!

4 Likes

Thank you for making this!

4 Likes

Amazing!

5 Likes

Version 0.2 available. Edited OP for those interested in the contents of the update.

3 Likes

Thanks! I didn’t know I needed this, but I really do! ^>^ :durtle_love:

3 Likes

haha, same! thanks for bumping this :smile: just the other day i experienced some confusion because i mixed up am / pm. well, not anymore! :slight_smile:

3 Likes

It is so…strange. But I can never learn these. *sigh (and here I’m learning almost 2000 kanji. lol :joy: )

3 Likes

This is awesome! Thank you @rwesterhof for the helpful script.
:slightly_smiling_face:

1 Like

Bug report: the settings actually allow me to pick a value outside this range (e.g. -2, 1, 8, 10) even though in practice it’s still the min or max value, 2 or 7.

You can set restrictions on the input like this in HTML:
<input type="number" id="quantity" name="quantity" min="1" max="7">

If you’re going to limit days, not sure why 1 isn’t supported but 2 is, but okay…

This is super minor (but probably also would take 2 seconds to fix) :wink:


Thanks for the great script! :partying_face:
This should really just be a built-in WK setting… :stuck_out_tongue:

1 Like

Not something I can fix. The settings use the open framework’s method of pushing it into the menu, and that doesn’t support min/max settings on the input fields (we could put in a feature request on that script of course). I offer the tooltip that the value is restricted to 2-7, which is enforced by the coding. So yes, you can enter -2, it will treat it as the minimum 2.
The reason 2 is the minimum is because after you finish the reviews for the day, the forecast should at least be showing you tomorrow’s reviews, which wouldn’t happen if it was limited to 1 day (the limit isn’t 24 hours in advance, but just the nr of day blocks the forecast shows). A limit of 1 will just show the empty current day - not much of a forecast.

Yes, but if a user deliberately entered one to just show that current day, it wouldn’t hurt to honor it.

1 Like

Perhaps not something that you would want to do, but you could use the pre_open callback to modify the input field and add min/max attributes

1 Like