<div dir="ltr">STEP doesn't use any wrappers per say, but confines all the (J)Sword code to as few places as possible (4-5 classes). The idea being any changes to APIs are only in a few places. It also does mean that if for some reason some other engine comes along with a different format of books, then we'd be able to hook into that. However, on that last note, if that were ever the case, my preference would strongly be to enhance (J)Sword to support a new module format.<div>
<br></div><div style>My two pennies... </div><div>Chris</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 July 2013 19:28, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org" target="_blank">scribe@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not to insult anyone-- please don't feel insulted...<br>
<br>
But what exactly does basing code off of Bibletime instead of SWORD give you? Are any of these things worth having in the engine itself?<br>
<br>
I have looked at the backend 'wrappers' in Bibletime around SWORD a few years back and I was disappointed for a number of reasons-- and so as not to insult anyone-- primarily because they didn't add any value at all, but only 'shielded' developers from using the engine directly.<br>
<br>
I have no idea if this is still the case. I get the impression that Bibletime, itself, has been re-written a number of times and I'm guessing this includes the 'backend' wrappers as well.<br>
<br>
My hope is that if there are any features that are usable by multiple frontend, then we should add these into the engine, if it makes sense. Again, in an attempt to stop this thread from becoming a defense of the Bibletime code or a defense of a 'methodology for an API interface (e.g., stateful vs. stateless container classes) and from degrading into insulting each other, I have not commented on the quality of the Bibletime code. I am simply stating that I don't know what<br>
<br>
* solid, additional features *<br>
<br>
are gained from using the Bibletime base for starting a new frontend instead of the SWORD code directly, and if there are any, can we add these into the engine?<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
Troy</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On 07/04/2013 08:17 PM, Israel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Great!! I will post the git page (to the uBible Developers) if you want me too, or you can head over to<br>
<a href="https://github.com/uBible/uBible/issues/1" target="_blank">https://github.com/uBible/<u></u>uBible/issues/1</a><br>
and post the info yourself if you want.<br>
We have been discussing using Bible Time's backend because @Mark Trompell suggested it.<br>
You can e-mail me off list if you'd like, or post on the Github page...<br>
<br>
<br>
On Thu, 04 Jul 2013 09:22:17 -0700<br>
Gary Holmlund <<a href="mailto:gary.holmlund@gmail.com" target="_blank">gary.holmlund@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am currently working on a second frontend for BibleTime that uses QML.<br>
It is a work in progress and I have some basic features up and working.<br>
Bibles, Commentaries, and Books can be read in multiple windows. The<br>
windows can be tabbed or split views of the screen. The install process<br>
for bibles, etc. is working.<br>
<br>
It requires Qt 5.1 and compiles on linux (ubuntu, fedora, etc.). I am<br>
looking into cross compiling onto android right now. Qt is not making<br>
this easy because they don't support cmake builds for android.<br>
<br>
I have it in a private git repository right now, but expect to put it<br>
into the main BibleTime git repository soon. Help with this would be<br>
welcome.<br>
<br>
Gary Holmlund<br>
<a href="mailto:gary.holmlund@gmail.com" target="_blank">gary.holmlund@gmail.com</a><br>
<br>
<br>
On 07/04/2013 06:25 AM, Israel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It uses QML, so it is part of Qt. I will bring this up to the others<br>
and see what they think about it all.<br>
It may be a good idea. Anyhow we are designing an interface at the<br>
moment to get the features we want, using what capabilities QML has,<br>
and designing it to be fully integrated with the Ubuntu Touch<br>
ecosystem. There are some things about using Bible Time that may make<br>
this<br>
hard, but there very well may be some things we might be able to utilize.<br>
Thanks!<br>
<br>
On 07/04/2013 12:15 AM, Mark Trompell wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Jul 4, 2013 at 2:04 AM, Israel <<a href="mailto:israeldahl@gmail.com" target="_blank">israeldahl@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br>
There are a few of us who have banded together to start work on a<br>
Ubuntu<br>
Touch SWORD app. Is anyone else working on one?<br>
</blockquote>
AFAIK Ubuntu touch uses qt, so maybe just another UI Frontent to<br>
bibletime would do fine,<br>
with the advantage of being easily portable to mer/nemo/sailfish(jolla).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If anyone is interested please join us on github.<br>
<a href="https://github.com/uBible" target="_blank">https://github.com/uBible</a><br>
We are currently in the process of working out the beginning<br>
details, such<br>
as UI setup, features, etc....<br>
May the Lord Jesus bless you all!<br>
<br>
-- <br>
Regards<br>
<br>
<br>
______________________________<u></u>_________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>