Dear Maintainer, I would like to draw your attention to the feature request submitted upstream: https://sourceforge.net/p/djvu/feature-requests/100/ It seems there is a way to restore the full functionality of djview4 for Internet documents despite the lack of NPAPI support. Regards - Janusz
Good idea. There's a way to get some URLs sent to external programs, like magnet: links to transmission, or some files to evince. In Firefox it's Settings > General > Applications. Should be able to key off mime types I think, although I don't see djvu files there.
Good idea. There's a way to get some URLs sent to external programs, like magnet: links to transmission, or some files to evince. In Firefox it's Settings > General > Applications. Should be able to key off mime types I think, although I don't see djvu files there.
On Sun, 18 Oct 2020 21:10:41 +0100 "Barak A. Pearlmutter" <barak@pearlmutter.net> wrote: > Good idea. > > There's a way to get some URLs sent to external programs, like magnet: > links to transmission, or some files to evince. In Firefox it's > Settings > General > Applications. Should be able to key off mime > types I think, although I don't see djvu files there. > > Yeah but you can add to that list from the ui. You have to write a mozilla or chrome extension which is an art that requires a lot of study (more than I have time for). In addition it would be good to start djview with the URL before getting the data. This would allow djview to handle all the communication with the server, which is useful for indexed multipage documents. Djview already does that : just pass a URL instead of a filename. Alternatively you could even have djview decode the data and returns a bitmap for mozilla/chrome to display. Essentially this means using a small native server that decodes the data quickly, talking to this server with websockets, and implementing the djvu plugin UI in javascript. But first one has to spend a couple months learning all this extension programming business and make it work across browsers... - Leon
The problem is solved: https://github.com/andy-portmen/external-application-button/issues/50 The question is only how to distribute it in Debian. Regards Janusz
The problem is solved: https://github.com/andy-portmen/external-application-button/issues/50 The question is only how to distribute it in Debian. Regards Janusz
That's great. If the extension is in Debian, than djview4 could "Suggest:" it. Or maybe would could just put appropriate instructions in /usr/share/doc/djview4/README.Debian, if you have wording for such a paragraph I'm happy to slip it in. Cheers,
That's great. If the extension is in Debian, than djview4 could "Suggest:" it. Or maybe would could just put appropriate instructions in /usr/share/doc/djview4/README.Debian, if you have wording for such a paragraph I'm happy to slip it in. Cheers,
I think the extension is worth a separate package in Debian, but for djview for a configuration file is needed (cf. the end of the issue thread). I think it can be distributed with djview, but perhaps you will ask the author of the extension for an advice? Regards Janusz
I think the extension is worth a separate package in Debian, but for djview for a configuration file is needed (cf. the end of the issue thread). I think it can be distributed with djview, but perhaps you will ask the author of the extension for an advice? Regards Janusz
Looks like the server part of External Application Button is ready for packaging in Debian: https://github.com/andy-portmen/native-client What about making the package an official one? Regards Janusz
Looks like the server part of External Application Button is ready for packaging in Debian: https://github.com/andy-portmen/native-client What about making the package an official one? Regards Janusz
Sure. I could package it, but I'm not a browser expert, so if there is one who could take primary responsibility that would make sense. If they're not a debian developer I could sponsor the package in, etc.
Sure. I could package it, but I'm not a browser expert, so if there is one who could take primary responsibility that would make sense. If they're not a debian developer I could sponsor the package in, etc.