View Single Post
Old 11-13-2012, 08:24 AM   #11
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,922
Karma: 1673776
Join Date: Jan 2010
Location: France
Device: Many android devices
Quote:
Originally Posted by Steve_Haley View Post
Ah, clarification - we don't copy the book to the /kindle/ folder, but perhaps we should! It'd save on confusion for users about trying to get Kindle working, at the expense of duplicating every file.
Shows me that I should actually look at our code before making claims.
Quote:
What we might want to do instead is, if no other reader apps respond but they do have Kindle installed, then we suggest that they move the Amazon formats to the /kindle folder, which then lets Kindle open the books. It also then preserves the mapping of the file CC thinks it's managing, and the file that the user is actually reading. (Which would matter if Kindle has a way of annotating books.)
This is better than copying. The file would be changed only when the user asks that it be changed (resent). CC wouldn't need to work out if the file in its library is different from the file in /kindle. And as you say, it eliminates the double copy. We would still want to touch the last mod date, though.
chaley is offline   Reply With Quote