[GUI Plugin] Reading Goal

[thiago.eec]

Version 1.6.9 - 08 Oct 2024

- Bug fix: a regression in the last version was causing the 'Abandoned' shelf color to match the 'Read' shelf color for past years

[ownedbycats]

Question to other users: How do you use challenges? I just haven't found any use for them personally.

[thiago.eec]

When @Lys asked for it, these were the examples given:

2023 -> General Fiction Challenge
2023 -> NonFiction Challenge
2023 -> Graphic Novels Challenge
from 1st Jan 2023 to 31st Dec 2024 -> Classical Literature Challenge

I really don't use it as a "challenge" per se, but as sub-goals.

I have three challenges set: Fiction, Non-fiction and Classics. Every book is added to one of the first two. I use it to balance my readings. I try to keep a 2:1 fiction/non-fiction proportion (right now it is 2.14:1).

Another use is to create a time restricted goal, like a monthly goal.

P.S.: The last of @Lys' example can't be done, because the time frame must be restricted to the current year.

[Terisa de morgan]

Originally Posted by ownedbycats

Question to other users: How do you use challenges? I just haven't found any use for them personally.

At this point, I don't use challenges in the plugin because I've already handled my goodreads challenge (bingo, cozy mystery in the month, whatever...) in other way. But, thinking about it, it could be a good way to see how many of the books I've read in the year have been involved in a goodreads challenge, Thank you for having me thinking about this!

[ownedbycats]

Hmm, I'm thinking of creating a challenge for 'books purchased in 202x' from Jan 1 - Dec 31, to see how many of them I actually read that year.

EDIT: though unfortunately I cannot retroactively create ones for previous years

ANOTHER EDIT: Also I notice that selecting Jan 1 on the dropdown instead selected 2023-12-31? It corrected itself when I edited it.

[thiago.eec]

Originally Posted by ownedbycats

Also I notice that selecting Jan 1 on the dropdown instead selected 2023-12-31? It corrected itself when I edited it.

I think it was probably a missclick. I don't quite remember why I had to leave December 31 of the last year available (when you click it, you'll see as 'Undefined' on the calendar, but on the list it appears as a date). It has something to do with an edge case (maybe because of the timezone issues existing at the time). I'll see if I can remove it.

EDIT: Actually, the 'Undefined' thing is why. The first available date is always marked as 'Undefined', so backed up a day to leave Jan 1st as date, instead of 'Undefined'.

P.S.: Notice that each challenge created adds a view in the 'Edit reading goal' dialog, so you can see detailed info.

[thiago.eec]

Version 1.7.0 - 09 Oct 2024

- Make challenge view available for all years in the 'Edit reading goal' dialog. It was only available for the current year.

[ownedbycats]

Would it also make sense to have a Statistics filter for the challenges? I was a bit surprised to see that wasn't a thing.

[ownedbycats]

Also, something I'm wondering: I have an action chain that converts the current page number to #percentread with this template:

program:
	if 
		globals(Current_Page)==''
	then
		$#percentread
	else
		totalpage = $#pagecount;
		currentpage = globals(Current_Page=1);
		newpercent = round(multiply ((currentpage / totalpage), 100))
	fi

I'm currently reading a book that's 446 pages long. While running the chain with a current_page of 190, this converted it to 43%.

However, when I look in Reading Goal, it shows 'pages' as 192. I often get minor differences like this for physical books - just 2 or 3 pages off. What causes it?

[thiago.eec]

Originally Posted by ownedbycats

I'm currently reading a book that's 446 pages long. While running the chain with a current_page of 190, this converted it to 43%.

However, when I look in Reading Goal, it shows 'pages' as 192. I often get minor differences like this for physical books - just 2 or 3 pages off. What causes it?

The difference is because you are rounding the result in your template.

190 / 446 = 42.6%, which was rounded to 43%
0,43 * 446 = 191,78 ≅ 192

Remove the round() bit from your template and the values should match.

EDIT:
Actually, the plugin does the same rounding when calculating the read pages, so it won't matter if you remove the rounding from your template. This happens because I chose to work with integers for the percentage read (as you also did).

[ownedbycats]

Updating the read_pages in the JSON seems to stick, though it's more of a hassle than its worth tbh.

[thiago.eec]

@ownedbycats, try this version.

I removed the rounding when saving the reading progress. Now it only rounds when displaying. It should reflect the exact page count now.

P.S.: You need to remove the round() function from your template too, or it won't work. If you want, you can format your reading progress column as '{:.0f}%', so it will round when displaying in your library (without losing the real value). That's supposing you column's type is float.

[ownedbycats]

Unfortunately, the column is an int-type because Kobo Utilities only accepts that.

[thiago.eec]

Originally Posted by ownedbycats

Unfortunately, the column is an int-type because Kobo Utilities only accepts that.

Then, just ignore the formatting tip.

Now I see. You need the rounding, since it is an integer column.

[ownedbycats]

Huh, looks like KU does take floats (the tooltip was inaccurate), going to test a bit more just to check everything works:



EDIT: I updated the tooltip.

ANOTHER EDIT: After converting everything to a float column and removing round(), the test version gets a more accurate count.