Adding it is possible.
However, mods.d.tar.gz is optional and you cannot count on it to exist
everywhere. If there is no mods.d.tar.gz then the InstallMgr operates
off the directory listing of mods.d. So adding the option for mods.d.zip
won't get you very far.
That's what I'm doing - downloadin
Sounds like it would be better to look at the mods.d folder inside the main
zipped package.
—
Sent from Mailbox for iPhone
On Fri, Jul 12, 2013 at 9:44 AM, Greg Hellings
wrote:
> On Fri, Jul 12, 2013 at 11:37 AM, Stephan wrote:
>> I want to provide an API to get a list of all modules in a repo
On Fri, Jul 12, 2013 at 11:37 AM, Stephan wrote:
> I want to provide an API to get a list of all modules in a repository. I
>> think libsword takes the mods.d.tar.gz file in every repo and unpack it
>> on the device to get this list.
>>
>> Is it possible to add the same file as a zip compressed o
I want to provide an API to get a list of all modules in a repository. I
think libsword takes the mods.d.tar.gz file in every repo and unpack it
on the device to get this list.
Is it possible to add the same file as a zip compressed one in every
repository, because unzipping in the browser is wor
Because our friend Ryan found this so "hard to find",
I have added a new top section to our file formats page,
based on lightly editing the responses from Peter and DM. See
http://crosswire.org/wiki/File_Formats#SWORD_modules
This should make things clearer to future visitors.
David
--
View
There is no documentation of file formats. The code for it has very little
documentation either. The intention is that SWORD C++ is used directly or via
bindings.
In Him,
DM Smith
On Jul 9, 2013, at 5:16 PM, Ryan Hiebert wrote:
> Thanks for responding Greg. I've had a little trouble f
> Von: "Ryan Hiebert"
> What would you consider the primary documentation for
> the file formats currently?
The source code.
There is no other documentation. The format, while open source is "proprietary"
in the sense that we see no need to document it and certainly no need to stick
to it. We
Thanks for responding Greg. I've had a little trouble finding
documentation on the file formats, though I have found some, mostly
related to the modules.d files. Is there more documentation that you
can point me to? What would you consider the primary documentation for
the file formats currently?
On 07/08/2013 11:06 PM, Greg Hellings wrote:
Why the need to contort a client-side UI language like
JavaScript to read binary file formats?
Case in point, which made me interested in Stephan’s work on sword.js
... https://www.mozilla.org/firefox/os/ (or
https://en.wikipedia.org/wiki/Firefox_O
I don't see that we need to document the file structure any further. If
you want a client-side application to be able to read a module, then you
are more than able to setup and configure a server that can translate
between an installed module and any web-friendly format you desire. If
you can't fi
Hi,
Am 08.07.2013 22:56, schrieb Ryan Hiebert:
Have you looked at untar.js?
https://code.google.com/p/bitjs/source/browse/untar.js?r=0eca1f06d91e1477e3708531939c8071fc877855
Yes, I've tried this but without success. The first files in the archive
are extracted, but than I get broken files.
On Mon, Jul 8, 2013 at 3:56 PM, Ryan Hiebert wrote:
> Have you looked at untar.js?
>
>
> https://code.google.com/p/bitjs/source/browse/untar.js?r=0eca1f06d91e1477e3708531939c8071fc877855
>
> On a tangentially-related note, I've done some work on a python sword
> zmodule reader. It's stalled a bit
Have you looked at untar.js?
https://code.google.com/p/bitjs/source/browse/untar.js?r=0eca1f06d91e1477e3708531939c8071fc877855
On a tangentially-related note, I've done some work on a python sword
zmodule reader. It's stalled a bit now, because I've seen
recommendations to use the C++ libraries,
13 matches
Mail list logo
