[GUI Plugin] Auto Datestamp and View

[eater]

This is a teeny plugin that updates a custom column with the current date and time whenever a book is viewed. It hijacks the built-in View action to add that functionality.

You need to create the custom column in your Calibre. Label it #lastviewed and give it the Date datatype.

Now you can sort your library by most (or least) recently viewed. The View Manager plugin makes this especially easy.

I am the very opposite of an experienced plugin developer, so I welcome comments.

[calijammi]

MERCI en GRAND pour ton plugin, tu peux voir dans ce THREAD:
https://www.mobileread.com/forums/sh...d.php?t=326420
que je m'en sers (si tu as une idée également relativement au fait que cette colonne n'est pas opérationnelle pour le tri à l'ouverture)
PS: j'ai retiré "iso" figurant dans l'image de Marco et je n'ai rien mis dans le format de la date
Bien à toi; Jammi

[theducks]

2 issues with this PI

1) The column name required is #lastopened

2) This PI pops an error every time you use Calibre on a Library that does not have (or want done) tracking Only Affects those with multiple libraries
A per Library configuration would be handy. This could also contain the fieldname to use. no name- no gripe First per Library use adds Library name entry and waits for user input for field (option to create: w/restart requires)

[DaltonST]

Originally Posted by theducks

2 issues with this PI

1) The column name required is #lastopened

2) This PI pops an error every time you use Calibre on a Library that does not have (or want done) tracking Only Affects those with multiple libraries
A per Library configuration would be handy. This could also contain the fieldname to use. no name- no gripe First per Library use adds Library name entry and waits for user input for field (option to create: w/restart requires)

There is a new Job Spy GUI Tool to replace this plugin that is compatible with a multiple-Library ecosystem. It turns itself on or off after Quick-Switching depending on the Libraries stated in Customizing, and whether or not the user-specified custom column exists in the appropriate Library, and whether or not the custom column is a 'datetime' type or not.

It also assumes that every user wants their very own special custom column name to use. Nothing is hardcoded.

Python 3 compatible, of course.

I will release the new Job Spy version after I finish testing the new tool.




DaltonST