<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1">Ditto. My BSV module is nowhere near ready for
submission to CrossWire so I publish the alpha on my web site.
BibleDesktop can access it but Sword requires an FTP site. I can't
afford an FTP site. If HTTP support were available it would help. <br>
<br>
Kermit<br>
</font><br>
<br>
On 5/13/2009 6:07 PM, Daniel Owens wrote:
<blockquote cite="mid:4A0B6EE3.3050804@pmbx.net" type="cite">You've got
my vote. It seems to be an understandable confusion that zipped modules
are available but most front-ends don't support their use. BPBible
implemented the installation of modules using zipped archives, and it
doesn't even have the standard module manager yet. That to me says that
this feature is easy to implement (and in my thinking long overdue).
HTTP repositories are another MAJOR motivation for me too...
<br>
<br>
Daniel
<br>
<br>
Peter von Kaehne wrote:
<br>
<blockquote type="cite">I grow slowly tired (and I am sure I am not
the only one) of the emails
<br>
on the support line regarding "I have downloaded x number of modules
<br>
and where are they now".
<br>
<br>
Wouldn't a feasible and relatively minor yet extremely useful
<br>
improvement to the module manager be the ability to handle
appropriately
<br>
zipped modules (and I do not want to reopen the debate on where is the
<br>
best place to keep your modules ;-))
<br>
<br>
Kind of
<br>
<br>
installmgr -zl ~/downloads/ # lists all zipped modules at a path
<br>
installmgr -zi ~/downloads/*zip # installs chosen zipped modules
<br>
<br>
and along those lines for the frontends?
<br>
<br>
The result would be that
<br>
<br>
a) zipped collections of modules would be better accessible (some non
<br>
CrossWire related websites make such available)
<br>
b) zipped collections of modules would be a good idea for passing
around
<br>
where internet access is difficult (I know there is the possibility for
<br>
local repos, but still)
<br>
c) accidentally created zipped collections (like that of my last
<br>
correspondent on sword-support) could be gracefully handeled along the
<br>
lines ("This was not the best way to get them, but do this and
this...")
<br>
d) It also improves the ability of those who have hosting space but no
<br>
ftp server to put out modules.
<br>
<br>
Peter
<br>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
<br>
<br>
</blockquote>
</body>
</html>