I want to be able to make a progressive web app using Angular. I want it to be able to download the resources from crosswire and store them with IndexedDB. The advantage of this is nothing needs to be installed on the users machine, everything I write immediately works on every operating system. And because of IndexedDB all Bible resources can be accessed offline. Because of the progressive webapp infrastructure the website itself will also be able to be accessed offline.<div><br></div><div>If I was to place a server between the webapp and the user the user would not be able to download the resources offline. That would surmount to redistribution by myself. However, if the client webapp directly downloads from crosswire via a REST API then that fulfills your distribution agreements.</div><div><br><br><div class="gmail_quote"><div dir="ltr">On Wed, 28 Dec 2016, 6:06 AM <<a href="mailto:sword-devel-request@crosswire.org">sword-devel-request@crosswire.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" id="gmail_block_quote0">Send sword-devel mailing list submissions to<br class="gmail_msg">
<a href="mailto:sword-devel@crosswire.org" class="gmail_msg" target="_blank">sword-devel@crosswire.org</a><br class="gmail_msg">
<br class="gmail_msg">
To subscribe or unsubscribe via the World Wide Web, visit<br class="gmail_msg">
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="gmail_msg">
or, via email, send a message with subject or body 'help' to<br class="gmail_msg">
<a href="mailto:sword-devel-request@crosswire.org" class="gmail_msg" target="_blank">sword-devel-request@crosswire.org</a><br class="gmail_msg">
<br class="gmail_msg">
You can reach the person managing the list at<br class="gmail_msg">
<a href="mailto:sword-devel-owner@crosswire.org" class="gmail_msg" target="_blank">sword-devel-owner@crosswire.org</a><br class="gmail_msg">
<br class="gmail_msg">
When replying, please edit your Subject line so it is more specific<br class="gmail_msg">
than "Re: Contents of sword-devel digest..."<br class="gmail_msg">
Today's Topics:<br class="gmail_msg">
<br class="gmail_msg">
1. Re: CORS API (Troy A. Griffitts)<br class="gmail_msg">
<br class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg">---------- Forwarded message ----------<br class="gmail_msg">From: "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org" class="gmail_msg" target="_blank">scribe@crosswire.org</a>><br class="gmail_msg">To: "SWORD Developers' Collaboration Forum" <<a href="mailto:sword-devel@crosswire.org" class="gmail_msg" target="_blank">sword-devel@crosswire.org</a>><br class="gmail_msg">Cc: <br class="gmail_msg">Date: Tue, 27 Dec 2016 11:47:43 -0700<br class="gmail_msg">Subject: Re: [sword-devel] CORS API<br class="gmail_msg">
<div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
<p class="gmail_msg">Hi Simon,</p>
<p class="gmail_msg">Thanks for your ideas. I'm interested to hear a little about the
use cases you are targeting. Are you trying to server offline
browser users in general, or do you have a specific case you have
in mind?</p>
<p class="gmail_msg">The background here is that we typically don't encourage
transferring data from our format to another. Though we've
accumulated a large library of works and that, in itself, is
useful to other engineer, we don't curate any of these individual
modules and simply have done the work to track down each
authoritative source, get permission for distribution and use as
openly as can be obtained from their curator, and then to convert
their primary data source into our module format. This doesn't
pass along any rights for use to other projects outside those of
CrossWire, and also doesn't provide a primary source for any of
this material-- which an lead to multiplied data conversion issues
when moving on to a second jump from the primary source.</p>
<p class="gmail_msg">We have a C++ engine which runs on most any device you might wish
to support (including web server)-- with many bindings for most
popular scripting languages, and also a native Java engine as
well. Both of these can be used to discover, install, and access
our entire library, if you'd like to start a new application in
our community or contribute to an existing solution.</p>
<p class="gmail_msg">Two web applications which use our engines and might interest you
are:</p>
<p class="gmail_msg"><a class="m_-2270669415137050943moz-txt-link-freetext gmail_msg" href="http://crosswire.org/study" target="_blank">http://crosswire.org/study</a></p>
<p class="gmail_msg"><a class="m_-2270669415137050943moz-txt-link-freetext gmail_msg" href="http://stepbible.org" target="_blank">http://stepbible.org</a></p>
<p class="gmail_msg">Hope this helps. Welcome! Looking forward to sharing in service
together,</p>
<p class="gmail_msg">Troy<br class="gmail_msg">
</p>
<p class="gmail_msg"><br class="gmail_msg">
</p>
<p class="gmail_msg"><br class="gmail_msg">
</p>
<div class="m_-2270669415137050943moz-cite-prefix gmail_msg">On 12/26/2016 03:32 AM, Simon Biggs
wrote:<br class="gmail_msg">
</div>
<blockquote type="cite" class="gmail_msg">Hi,
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">I was hoping to help set up a CORS API for transfer of
crosswire resources to web apps. My hope was to be able to make
something simple, probably written in Python with the Tornado
module and using the sword SWIG bindings. </div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">My thought is the API would simply send whole resources, such
as a whole Bible translation. Any webapp interfacing with the
API would likely download the resources once per user and store
them within the browser's IndexedDB.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">I'm not sure what is the best format to use for the
transmitted content. The easiest option might be using something
like the plain text OSIS format. From my limited exposure to
this project that would mean minimal work on the server end
required to make as many resources as possible able to be sent
this way. What to then do with the OSIS file and how to store it
in the IndexedDB would be up to the client side programmer.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">What are your thoughts? Does anyone have any recommendations
for improvement? If I made something like this, is this
something that crosswire would be willing to have running on
their server for resource distribution?</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Thank you,</div>
<div class="gmail_msg">Simon</div>
<br class="gmail_msg">
<fieldset class="m_-2270669415137050943mimeAttachmentHeader gmail_msg"></fieldset>
<br class="gmail_msg">
<pre class="gmail_msg">_______________________________________________
sword-devel mailing list: <a class="m_-2270669415137050943moz-txt-link-abbreviated gmail_msg" href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a>
<a class="m_-2270669415137050943moz-txt-link-freetext gmail_msg" href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br class="gmail_msg">
</div>
_______________________________________________<br class="gmail_msg">
sword-devel mailing list<br class="gmail_msg">
<a href="mailto:sword-devel@crosswire.org" class="gmail_msg" target="_blank">sword-devel@crosswire.org</a><br class="gmail_msg">
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="gmail_msg">
</blockquote></div></div>