View Single Post
Old 11-03-2024, 07:57 AM   #8
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by dovfa View Post
So if I got you right, your message quoted above (together with your preceding one) boil down to a warning like:
"Koreader-Calibre WiFi connectivity is intended for advanced users. It may get you in trouble. Don't use it unless you are really sure you know what you are doing".
I have browsed again the Koreader User Guide (23.01), and found no such warning.
Nope. That's quite stupid. Please don't put those words on my mouth.

It is what it is:

1. calibre is a complex piece of software intended to be used with devices running their stock program.

2. that's what you get when you connect your device to your computer using usb using the stock drivers (for kobo, in your case).

3. you'll need to workaround that following the 3 easy steps quoted above if you want to share the same set of documents using usb and via wifi.

But there's nothing that could cause you trouble that's not under a warning: https://github.com/koreader/koreader...eless.lua#L214

And that's exactly what happens if you try to mix a wifi/smart device app folder with one initializated by calibre following your device specs.


From the PoV of KOReader we assume calibre users have some understanding about the software they use, so things like "device templates", "device drivers" et al are quite mandatory to figure out an integration that works for you.
pazos is offline   Reply With Quote