01-10-2021, 01:18 PM | #76 |
I'm not a number!
Posts: 244
Karma: 11496
Join Date: Jul 2011
Location: Quebec City
Device: Kobo Elipsa
|
KOReader become a link in the NickelMenu, you start it as you would start an app on your cellphone. When you exit the app, you return to the Kobo normal UI. It really worth it to try it imho, I'm just sad that I waited that long to switch.
|
01-17-2021, 05:02 PM | #77 | |
Member
Posts: 12
Karma: 12048
Join Date: Aug 2012
Device: Kobo Touch
|
Quote:
|
|
Advert | |
|
01-17-2021, 05:35 PM | #78 |
Guru
Posts: 738
Karma: 7025494
Join Date: Aug 2017
Location: Italy
Device: Kindle Paperwhite, Kobo Elipsa, Pocketbook Inkpad 4, Inkpad Color
|
|
01-17-2021, 05:45 PM | #79 | |
Diligent dilettante
Posts: 3,441
Karma: 49052774
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra H2O
|
Quote:
Over the weekend I have spent more time in KOReader than in Nickel, and so far, I don't get the raves. Or rather, I get that the raves confirm it's not going to be my first choice. It's a competent reader for sure, there's nothing wrong with it. But the features most rave about (Wallabag, ligatures, "real" page numbers etc.) are of no interest to me, and I DO miss being able to plug my Libra in and have Calibre with all its wonderful plugins available. I also REALLY miss the easy access to series and collections. Having to scroll through a File Manager listing all 650+ books by author is much less appealing than being able to go straight to my TBR, my Romance collection, etc, or to simply pick a book based on its cover. I am going to read a few more books on it to try the stats that have been lauded, but so far, the impression it gives me is one common to a lot of FLOSS software - designed to be fun for those who love tinkering and customizing as an end in itself, but for those who just want to pick up a book and read, not so much. Last edited by Uncle Robin; 01-17-2021 at 06:18 PM. |
|
01-17-2021, 06:41 PM | #80 | ||
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Quote:
Quote:
---- The rest was discussed in the sibling thread, so it doesn't come as much of a surprise . I've also discussed the chunked vs. papyrus rendering tradeoff at length in the past... somewhere in a couple of those 11000 posts ^^. Last edited by NiLuJe; 01-17-2021 at 06:47 PM. |
||
Advert | |
|
01-17-2021, 06:55 PM | #81 |
Diligent dilettante
Posts: 3,441
Karma: 49052774
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra H2O
|
I can't see a way to filter those searches by "unread", "Date added" etc?
|
01-17-2021, 07:49 PM | #82 | |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Quote:
They're *technically* in the on-device metadata dump, so they could be handled, but I don't personally see much use for the Date Added one (I don't *think* it matches the on-device file's ctime, for instance, and *that*, on the other hand, is a bit of data that might be interesting). The read status might be useful, but is trickier to handle: it's a custom column, so it'd need user input to set it properly (name & format), and it's not nearly as useful on its own, which means it'd only be useful for compound searches (i.e., search filters), which aren't currently supported . EDIT: Some of those "date" columns could be useful as a *sort* method, though. But, again, not implemented yet ^^. EDIT²: (Thinking out loud). In the interim, what might be easier to implement (both UI & code-wise) would be graying out read items from search results. Last edited by NiLuJe; 01-17-2021 at 07:54 PM. |
|
01-17-2021, 08:13 PM | #83 |
Diligent dilettante
Posts: 3,441
Karma: 49052774
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra H2O
|
This would be a very useful enhancement. Also, thanks for confirming that, at least on this occasion, I had not missed some feature or functionality. I would have been happy to RTFM if only there were one - the wiki not exactly setting the benchmark for comprehensiveness and/or usefulness.
|
01-17-2021, 08:15 PM | #84 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
But they don't really do anything useful if you don't use nickel. And calibre will not see the books on the device if you don't do the import. For those who only want to use KOReader, I recommend using either "Connect to folder" or the User Defined USB driver. Both of these will let calibre see and manage the books without looking at the database.
|
01-18-2021, 12:04 AM | #85 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@davidfor: Hmm, good point on the fact that the Kobo driver uses nickel's db to do the on-device check, I'd forgotten about that because I tend to actually do the import in between usbms sessions . (e.g,. I sync ko read status to the nickel db, so keeping it in sync is part of the work flow. Might not do it right after loading the books, but it'll happen eventually ;p).
@Uncle Robin: Yeah, doing a cursory pass over the wiki to make it slightly less depressing keeps getting pushed back down the TODO list, unfortunately... Last edited by NiLuJe; 01-18-2021 at 12:06 AM. |
01-18-2021, 12:23 AM | #86 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
|
01-18-2021, 06:47 AM | #87 | |
Diligent dilettante
Posts: 3,441
Karma: 49052774
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra H2O
|
Quote:
In the attached shots, Kobo's click per minute count is pretty much spot on. But if that rate is used to calculate the time remaining, the answer should be 16.8 hours, not 44. The KOReader stats are MUCH more accurate. At exactly 4 clicks per minute, the time taken to finish the book should be 12.366 hrs - VERY close to KOReader's estimate, very much unlike the Kobo count. The book is Calibre converted kepub too, so it's impressive that KOReader counts and extrapolates so much more accurately than does Nickel. |
|
01-18-2021, 08:47 AM | #88 | |
cosiñeiro
Posts: 1,317
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Quote:
The raison d'être of the wiki is documenting specific features. Most of these features are quite advanced, like dictionary support, keymapping or gestures. Also, since KOReader is a very hacked up reader, nobody expects than the average user/contributor/maintainer actually knows (or wants to know) more than 10% of that extra stuff. Personally I think new users are the best to write end user documentation, if that's something in the scope of the program. I would doubt it sometimes. It was a hacked reader for its author at first. Then others used (and hacked) it. Mainstream, even in a niche product like aftermarket ebook readers, was never a goal. It was and still is an ebook playground. So no doubt why nobody writes end user documentation. Actual users are more interested in writing code or just use the program to read. After all they all know how to handle the program. So my approach with the RTFM would be: some new user with genuine interest and a few hours of free time writes glue code on a few topics, and that, paired with some info of the wiki, makes a manual to read. See my suggestion Once there's a manual it is way easier for others to tell the manual isn't good enough and suggest changes. |
|
01-18-2021, 12:14 PM | #89 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@pazos: Yep! It'd be a great base for a dev actually familiar with the code in question to then do a quality check pass on top of that to fix mistakes or simplify things.
(That's essentially what I ultimately want to with the current wiki. I even had a slot in the schedule for it and everything, but then the new icons came along, and I went: well, if I have to take new screenshots anyway, better wait for that to land... and then, well, shiny new thing happened, and happened, and happened... ;p). |
01-18-2021, 12:20 PM | #90 |
BLAM!
Posts: 13,494
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@Uncle Robin: A not necessarily obvious thing is that you actually control the initial state (e.g., what happens when you open a brand new book).
Each book is a blank slate, there's no cross-book tracking. Instead, there's a setting available¹ for the thresholds: a floor (if a page was shown on screen for *less* than this amount, it's not counted in the stats. The intent being ensuring skimming doesn't pollute the stats), and a ceiling (if a page was shown for *more* than this amount, the time is capped to this value. The intent being having spent time in the dictionary/wikipedia/menus/whatever doesn't skew the stats too much). That's used to seed the initial computation of "time spent reading a page" (at 50% of the cap). ---- [1]: This is KOReader's unofficial motto: "there's a setting for it" . Last edited by NiLuJe; 01-18-2021 at 12:25 PM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
advantages to jailbreaking | cylemmulo | Amazon Kindle | 5 | 01-15-2013 08:18 AM |
Software advantages | Sarthak | Barnes & Noble NOOK | 15 | 11-18-2011 09:33 PM |
Classic Advantages of 3G Version | Hitchcockfan | Barnes & Noble NOOK | 1 | 06-28-2010 07:27 PM |
What other advantages do BlackBerries have? | c-otwa | Alternative Devices | 0 | 12-08-2009 01:26 PM |