Thread: [GUI Plugin] Goodreads Sync
View Single Post
Old 04-03-2019, 08:49 PM   #1190
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by lairdb View Post
Sorry if I missed it -- I did search the thread -- but is there a sensible reason this isn't integrated into the Calibre background job mechanism? It's the only plugin I use even semi-regularly that is foreground blocking.
There is added complexity in running jobs in the background. Whether it makes sense depends on exactly what is happening and what user interaction is needed. Plus, there are some things that cannot, or should not, be done in background jobs. How often something is expected to be run and how many changes it is expected to make also affects whether running in the background is worthwhile. For example, running the "Update progress" action in the background is probably not worth it. I rarely do this more than once a day for one or two books. The time taken to do this update is not enough longer than creating the job to make it worthwhile.

Which actions do you think should be run as jobs? I can look at them, but, it I'd need to be convinced of the benefit in doing it.
davidfor is offline   Reply With Quote