View Single Post
Old 06-11-2008, 02:59 PM   #94
=X=
Wizard
=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.
 
=X='s Avatar
 
Posts: 3,671
Karma: 12205348
Join Date: Mar 2008
Device: Galaxy S, Nook w/CM7
Quote:
Originally Posted by beowulf573 View Post
I'd rather not recreate web2lrf features in javascript if I don't have too. Too much work and too much duplication.
I completely understand. Why re-invent the wheel. My personal feel then is to stick with using the web2lrf. (Or have a toggle button on your options page where the user can specify which to use [1]web2lrf or [2]html2lrf)


Quote:
Originally Posted by beowulf573 View Post
Actually, I can't just read the pref information. There are several plugins to override the default behavior; for example determining which proxy to used based on a regexp or to use a random proxy. I can query the proxy interface to determine what proxy would be used for a given url, however the low level library used by calibre only supports http proxies. If you're using SOCKS you're out of luck.
Yes as long as your able to poin to the proxy that should be fine for me. My corp. uses SOCKS, but I've been able to determine what is the actual proxy used by the company.

Thank you
=X=
=X= is offline   Reply With Quote