Thread: [GUI Plugin] Reading List
View Single Post
Old 07-31-2011, 09:37 AM   #182
capnm
Groupie
capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'
 
Posts: 156
Karma: 10001
Join Date: Feb 2011
Device: sony
Quote:
Originally Posted by kiwidude View Post
Not so sure about this one. I would assume this is perhaps for similar reasons as Vaesse of wanting to keep track of books on the device and potentially having tags set? Or some other reason? I can see that it could be useful for people to have say a tag for each such list, which would allow them to see at a glance who has what on their devices. Or even just being able to see a list without the tags.

There are however a number of issues that come to mind.
- Such a list needs to be kept up to date after any other actions cause the device to be updated, whether you manually use the remove or send to device menus, or force sync another list to the device. I don't even know if it is possible to hook into those non plugin menu actions, and once your list loses integrity, you will have to Force Sync it or reconnect the device to get it back up to date.
- Also such a list might need to be read only from a user perspective, or else you will get into conflict situations. So not allowing manual add, remove or clear actions.
- Would you allow even changing list ordering - possibly I guess.

Will ponder this one, it might involve a fair amount of work and I gave less spare time nowadays. Feel free to comment on whether my understanding is correct and whether you think it useful.
My workflow keeps evolving as the tools evolve

I find that I'm using auto-synced add and remove lists as the main (but not only) means of loading/unloading readers, and having multiple add lists turns out to be really handy.

Then, after the auto-sync, I'm manually setting a list to what's on the reader so that I can later (in Calibre) enter notes, decide what to add/remove, know which reader has what, etc.
Which isn't exactly a hardship -- but I admit it would be nice to have the last auto-sync job be creating that list, so I could just plug the reader in, forget about it for a while, then unplug & go.

I'm fine with the idea that it is only a snapshot at the time of the last [auto]sync -- if I indulge in manual updates/syncs I can certainly reconnect or force sync to update it (or even edit it) if I care.

I wouldn't make it read-only -- in fact I can imagine times I might prefer to mess with it.

Thanks for running the 'remove' jobs first -- it makes it possible to swap out a bunch of books automatically
capnm is offline   Reply With Quote