<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>Glad to be here, I'm new here and haven't gotten fully how the
sword module works. Still trying to understand it. I'm mainly a
backend developer - PHP, but still can help.</p>
<p>About the Indexeddb, what's the real scope of the app?</p>
<p><br>
</p>
<p>James<br>
</p>
<br>
<div class="moz-cite-prefix">On 25/06/2017 21:20, Troy A. Griffitts
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5235BA33-BDA8-4F8E-9A57-0F1E45AA8A4E@crosswire.org">Hi
Stephan,<br>
We have another new sword-devel subscriber interested in web
development and I wanted to ping your email so he could read
through the quoted thread. I want to support your ideas but am
skeptical right now about supporting format shifting to indexeddb.
Mostly because I'm not sure what can of worms that might open up
for dealing with publishers. Also technically, I've always had
trouble storing anything sizeable into an indexeddb store.<br>
<br>
Troy<br>
<br>
<div class="gmail_quote">On June 25, 2017 9:33:04 AM GMT+02:00,
Stephan <a class="moz-txt-link-rfc2396E" href="mailto:info@tetzels.de"><info@tetzels.de></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre class="k9mail">Hi,
this is an old thread, but I like to second that. It would be really
nice if CORS could be enabled for everything under
<a href="http://www.crosswire.org/ftpmirror/pub/sword" moz-do-not-send="true">http://www.crosswire.org/ftpmirror/pub/sword</a>/
Currently this is one of the main obstacles to write a modern
offline-first (progressive) webapp.
Are there any specific reasons why CORS can't be enabled for the module
repositories?
Thanks
Stephan
Am 28.12.2016 um 15:59 schrieb Simon Biggs:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> 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.
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.
---------- Forwarded message ----------
From: "Troy A. Griffitts" <<a class="moz-txt-link-abbreviated" href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:scribe@crosswire.org"><mailto:scribe@crosswire.org></a>>
To: "SWORD Developers' Collaboration Forum"
<<a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:sword-devel@crosswire.org"><mailto:sword-devel@crosswire.org></a>>
Cc:
Date: Tue, 27 Dec 2016 11:47:43 -0700
Subject: Re: [sword-devel] CORS API
Hi Simon,
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?
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.
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.
Two web applications which use our engines and might interest you are:
<a href="http://crosswire.org/study" moz-do-not-send="true">http://crosswire.org/study</a>
<a href="http://stepbible.org" moz-do-not-send="true">http://stepbible.org</a>
Hope this helps. Welcome! Looking forward to sharing in service
together,
Troy
</blockquote>
<hr>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</div>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<strong>John James</strong><br>
Co-Founder – 4ward NG<br>
Skype: donjajo1 • Twitter: @donjajo </div>
</body>
</html>