Quote:
Originally Posted by sbenz
I wouldn't. I had actually thought of use cases where a user might want to put things in this folder. And if they did, it would not affect the db, only the size of the 'book folder,' so there would be no harm. It would be more problematic if a user deleted a file from the folder put there by a plugin. The plugin would have to handle those cases.
SB
|
@
sbenz - maybe the plugin data could be put into a different sub folder eg ...\attachments\plugins or ...\plugins
However, there have been several requests to have an Attachments (Extras, Supplementary) folder within the book folders into which user could put things. Kovid has declined to do that, I can't recall his rationale in detail but at the time it seemed reasonable. Might have been related in part at least to deletions, and what happens if a file in Attachments is locked by another process when there's a move to be done etc. I suggest you ask Kovid for his thoughts.
My observation is that the file handling across different platforms is one of the more 'difficult' issues calibre has to address - case significance, access control, file locking, path lengths etc.
Which maybe brings you full circle to either having the word list stored in the database, or as a 'pseudo_format file', or... in unmanaged space.
Your main objection to the 'pseudo_format_file' was that seeing a file called 'Some Title - An Author.badwords' would confuse the user. But would that be any more confusing than pressing 'O' and seeing an Attachments folder containing a file of a similar name. Or coming to grips with the purpose of ORIGINAL_XXXX.xxxx files. Transparency is often the best way to avoid confusion.
The file wouldn't come into existence unless the user ran your PI, and presumably your PI would hook up to a custom column as a place to store the bad word count. And the user could colour that column based on the count, blue if more than 50, red if more then 20 etc
BR