-0700
Von: "Troy A. Griffitts" <[EMAIL PROTECTED]>
An: SWORD Developers\' Collaboration Forum
Betreff: Re: [sword-devel] sword module repository
> Just a few of the usual, cold, chiding remarks scattered below...
>
> > Yeah, we use a "custom" HT
Just a few of the usual, cold, chiding remarks scattered below...
> Yeah, we use a "custom" HTTP method rather than a "custom" FTP method.
Actually the 'standard' SWORD mechanism for remote module installation
is defined by the C++ SWORD engine. If the purpose of JSword is to be a
Java alterna
Peter,
JSword uses HTTP tunneling to get to the modules' zip files and to
the catalog of modules. Specifically it expects the following structure:
www.xyz.com/a/b/c/root/
(note: a/b/c/root can be any path of your choosing)
www.xyz.com/a/b/c/root/packages/rawzips/*.zips
(no
Hi all,
Time for me to chime in. Since Troy threw down the gauntlet. (BTW,
we are good friends and I know he is teasing me for the differences)
Yeah, we use a "custom" HTTP method rather than a "custom" FTP method.
JSword uses a plug-in model for an installer and as such can accept
p
It might also be good to point out that using the modules (and having
them available at that website above) in zipped format will also
result in much happier customers and downloads from the site, as they
will be able to download smaller files :)
--Greg
On 11/6/06, Troy A. Griffitts <[EMAIL PROTE
Hey Peter,
Officially, a SWORD module repository merely requires FTP access to a
standard install of SWORD modules.
ftp://crosswire.org/pub/sword/raw
This should allow all frontends which use the SWORD engine's install
classes to use your repository (BibleCS, GnomeSword, Bibleti
I have created a collection of sword modules for which i have only limited
rights of distribution - i.e. our church can distribute them without any
complaint, but I think I would end up in trouble if I uploaded them into the
sword repositories. I do presume this will be resolved at some stage, b
