<div class="gmail_quote">On Sat, Nov 6, 2010 at 1:53 AM, Karl Kleinpaste <span dir="ltr"><<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Jonathan Morgan <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>> writes:<br>
</div><div class="im">>> You can access <a href="http://ftp.xiphos.org/sword/mods.d.tar.gz" target="_blank">http://ftp.xiphos.org/sword/mods.d.tar.gz</a>, crack it open,<br>
>> and see what's available. Just two assumptions:<br>
>> - the zip subdir is at the same level as mods.d<br>
>> - xyz.conf has a corresponding xyz.zip.<br>
<br>
> Agreed. I can and have. I don't expect my average user to, though.<br>
<br>
</div>My point was that a module manager (that is, the InstallManager class)<br>
can do this readily. It should be invisible for http+zip retrieval,<br>
just as it already is for ftp+components retrieval. It should just<br>
happen as part of the request for local refresh of the remote content<br></blockquote></div><br>Indeed. But BPBible does not have InstallManager support.<br><br>Jon<br>