[GUI Plugin] Job Spy

[Marco77]

Hello there,

Thank you for this PI, I've used it sporadically a few years ago and it was useful.

I believe my whole library was modified by adding a custom column recently, and since my default view is sorted by last modified, the ordering is in complete shambles.

Cue Job Spy, but ofc I don't have a backup of those timestamps, furthermore copying from "added time" yields a bit unsatisfactory results, with quite a few empty fields.

So... long story short, I patched the code to add a new function. It retrieves the timestamp from filesystem, assuming it will be authoritative.

- It takes the most recent timestamp found amongst available formats; no action is taken if no file was found
- the file path is computed using "self.guidb.format_abspath" but I left over the libpath path construction code, you might want to clean this up by choosing whichever preferred way
- all queries are wrapped in a single transaction, so it's do-or-die
- apsw cannot prepare queries using datetime objects? Had to manually force the str() conversion. It seems fine when browsing using sqlite3

[Nekrodamus]

Hi Dalton

I usually use the Utility GUI Tool "Copy User Category from Source Library to Target Library", until version 1.0.167 I had no problems, but in version 1.0.170 it doesn't work, at least to me, all the tests I did using Caliber 4.8. I attached some images so you can see what happens. Tell me if you need other data.

Apart from this matter, could an option to copy all categories at once be added to this utility, in the future, so as not to have to copy one by one. This would be wonderful.

On the other hand, thank you very much for such an excellent plugin, it is really very useful.

Regards!!!

PD: Google English, sorry !!

[DaltonST]

My JS test categories had no diacritics, such as Spanish accents. Hence, I did not encounter any copy-category testing issues caused by changing JS to be compatible with Calibre 4.99+ that uses Python 3. My fault. I will add some diacritics to a test user category, fix it, and upload the new version of JS later today.

Thanks for "testing" the new version.


DaltonST

[DaltonST]

Version 1.0.171 -2020-01-12 Technical changes after Python 3.8 testing with Calibre 4.99.3

The "Copy User Category to another Library" GUI Tool uses JSON, which changed just enough recently to unintentionally cause a copied UC to be "renamed" into garbage characters if the original name had non-English characters. The copy worked fine, but the UC name was garbled. Fixed.

Tested in both Calibre 4.8 and Calibre 4.99.3


DaltonST

[Nekrodamus]

Thanks dalton

I tried this new version and it works perfect !!!

Regards!

[Rellwood]

Hi,

I noticed that a few updates ago the plugin required the newest version of Calibre, however I still run a Windows 7 machine and apparently they stopped supporting Windows 7. I plan on keeping Windows 7, but if I end up having to stay with an older version of Calibre, will your plugin be available?

[DaltonST]

Originally Posted by Rellwood

Hi,

I noticed that a few updates ago the plugin required the newest version of Calibre, however I still run a Windows 7 machine and apparently they stopped supporting Windows 7. I plan on keeping Windows 7, but if I end up having to stay with an older version of Calibre, will your plugin be available?

I don't really understand the "I plan on keeping Windows 7, but if I end up having to stay with an older version of Calibre".

I upgraded to Windows 10 as soon as it first came out, and was immediately rewarded with a noticeably snappier machine since Microsoft modularized its functions to optimize its active memory footprint viz a viz Windows 7.

If you are concerned with running old versions of Calibre with old versions of your plugins, "best practices" would say that you should periodically be backing up your "C:\Users\Rellowood\AppData\Roaming\calibre\plugin s" directory into a date-stamped directory name (to avoid overwriting) on an external drive so that you will have all of your old plugins (and their associated preferences .JSON files) in discrete locations for future use if you have to install old versions that are all guaranteed compatible with the version of Calibre in-use at the time of the back up. You might want to download the Calibre version in use at that same time, and move it to the same external drive.

Calibre, its plugins, and the plugins' .JSON files are matched sets that work properly together at any point in time.

I assume that you already know that you can install old versions of Calibre Portable directly onto your hard-drive in specifically named directories, and run each version independently of the others. Just make sure the \calibre\config\ directory is properly seeded for each. Keeping your plugin preferences .JSON files across Calibre versions synchronized could be an issue unless you standardize on a single "old version" to use consistently.

Just my personal opinion, but the above sounds like a lot of needless aggravation just to keep Windows 7.

To finally answer your original question, JS uses Calibre's own application-specific libraries for many purposes, so as Calibre changes, JS has to change with it or one or more of its 62 tools (or even all of JS) will fail and die. Hence, as Calibre changes, the minimum JS version likely will have to increase as well. If you do not upgrade Calibre, then you would be "stuck" on the JS version active at that time. Just be sure to keep a discretely-named backup of the "stuck on" JS .zip file since it could easily be overwritten by a newer file with the identical name. Hence, the advice given previously.



DaltonST

[Rellwood]

Thanks for letting me know.

Question, do you have problems with creating restore points and using previous versions of files? I was under the impressions (after trying Windows 10 many times) that you needed an external drive always connected to your computer to enable that feature.

This was why I stayed with Windows 7. I noticed that restore points and previuos versions of files weren't being made unless the external drive was connected.

[theducks]

File History and Restore points are different beasts.

RP is for OS changes and usually fires off on any program install the invokes UAC

OTOH File History is a safety net, and wants to keep files elsewhere.
You can change that place, as long as it is external

[Tanjamuse]

If you have this tool already, then I apologize, I couldn't find it.

Could you add a tool where it's possible to copy info from a custom column in 1 book? Ideally I would love to have an option too where I can then add it to a different book.

[DaltonST]

Calibre already does that.

[Tanjamuse]

When I add this

{:'re(re(field("#fandoms"),":"," "),"§","&")'}/{#story_id}/{#story_id}

to the Tweak for Per-Library: 'Save-to Template': Default Template it says:

calibre, version 4.8.0
ERROR: JS+ GUI Tool: Save-To Template is Invalid. Reset to Calibre Default Template.

[ilovejedd]

Originally Posted by Tanjamuse

When I add this

{:'re(re(field("#fandoms"),":"," "),"§","&")'}/{#story_id}/{#story_id}

to the Tweak for Per-Library: 'Save-to Template': Default Template it says:

calibre, version 4.8.0
ERROR: JS+ GUI Tool: Save-To Template is Invalid. Reset to Calibre Default Template.

You could try:

{#fandoms:'re(re($,":"," "),"§","&")'}/{#story_id}/{#story_id}

[DaltonST]

Version 1.0.172 -2020-01-23 Allow single and double quotes in the tweak default for save-to template.



DaltonST

[Tanjamuse]

Multi-Reply:

Sorry, I haven't had time to test it before now.

Originally Posted by ilovejedd

You could try:

{#fandoms:'re(re($,":"," "),"§","&")'}/{#story_id}/{#story_id}

It didn't change the § to & when it was saved, but it's okay, because with the following changes DaltonST made to the plugin my original template works.

Originally Posted by DaltonST

Version 1.0.172 -2020-01-23 Allow single and double quotes in the tweak default for save-to template.

DaltonST

Thanks so much both of you.