David King writes:
I have not found a recoll web caching plug-in for Google Chrome? Is
there one? Are there plans to develop one?
I've done a proof-of-concept for my own use by modifying the existing
Firefox plugin to make it work in Chrome.
What I've got right now is definitely not ready for prime time. I'm
curious if there is any interest in polishing up and integrating in what
I've done? It's not standalone, it would have to be integrated into the
code that JF supports.
The code I've added uses a small, local web service running in the
Python Flask framework which accepts requests from the browser plugin
and writes the recoll webcache files out to their target directory. I
did it this way because I was unable to get the Chrome version of the
downloads.download method used in the plugin to reliably set the
filename of the downloaded file. Chrome has a
downloads.onDeterminingFilename listener that any plugin can instantiate
which can and will modify the filename used in all browser file
downloads. I couldn't find a reliable method to prevent the listener
defined in the "Aria2c Integration" plugin I have installed, for
example, from changing the filenames of my recoll-we plugin download
files. A secondary factor was that, while I like to use the downloads
bar in the browser, I don't like having two recoll downloads show up
there every time I visit a web page. Using a local web service as I did
avoided these problems. On the other hand, adding a web service to this
process adds yet another level of complexity. Fine for somebody like
me, not so good for a user who expects it all to "just work."
I couldn't register on opensourceproject.eu so I couldn't fork JF's
recoll-we code there. Even tried VPNing to an EU IP address but I kept
getting 500 errors no matter where I came from. So, I've put my version
of the plugin on github, at https://github.com/dlk3/recoll-we-chrome. ;
My mods are in the background.js and the new recoll-we-webservice.py
scripts.