<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 19, 2017 at 1:52 PM, Matt Zabojnik <span dir="ltr"><<a href="mailto:mattzab@gmail.com" target="_blank">mattzab@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I don't mean to derail this in any way. I've previously only had experience with HTML/PHP/SQL, and I'm now learning Python (in order to develop a SWORD-related Android app)<div><br></div><div>Would it be beneficial to port the whole project to Python? That seems to be a widely known and easy to learn language.</div><div>Forgive my ignorance if this question is completely unreasonable. I've previously only ventured into hack-together type of workaround stuff when it comes to computers, rather than true programming. (Learning RegEx has been an amazing eye-opening experience in module making)</div></div></blockquote><div><br></div><div>Not likely. There is already an existing Java port, and there is little interest in maintaining more than the one official port. The language is not a significant barrier to improvement, adoption, or advancement. In fact, being written in decently portable C and C++ is one of the best technical merits of the engine. It allows us to offer bindings to Perl (for scripting) and Python (for BPBible and the like), and wrappers into Objective-C (for our Mac and iPhone apps), and into the JNI interface (for at least one Android app). Maintaining a pure-Java port gives access to other environments (Java Swing UI, web, and native Android) and could allow easy access to others as well (e.g. Jython, JRuby, JavaScript).<br><br></div><div>If you were going to start a whole new port into a language like Python you would begin to open the door to format shifting the modules, and a whole host of other things that would be incompatible with the current project. Not many Python developers are going to happily attack the binary flat format that a Sword module currently lives in. They're going to want to use something else, most likely. You're going to lose out on around two decades of support, features, bug fixes, and small tweaks and have to start again to re-gain the code maturity that the engine already has. And there's far more you'd lose out on.<br><br></div><div>No, a new port is not likely to happen within the community. Not to say it couldn't happen outside of the community. But you're not likely to get core developer support for abandoning the current library and shifting to a new port into a language like Python. The closest you'll probably get is forks, like the existing Sword++ fork. Or people who have wrapped Sword in order to format shift content, e.g. into a SQL database or JSON or such, for use in a new application.<br><br></div><div>--Greg<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>I know BPBible was written mostly in Python. If I get good enough at Python and have the time I may fork and develop that front-end where I can. I'm still pretty green though to say the least.</div></div><div class="gmail_extra"><div><div class="m_6386721833253732607h5"><br><div class="gmail_quote">On Sun, Feb 19, 2017 at 11:06 AM, David Haslam <span dir="ltr"><<a href="mailto:dfhmch@googlemail.com" target="_blank">dfhmch@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are we any closer to a release of SWORD v1.8 ?<br>
<br>
cf. Troy started this thread last October.<br>
<br>
As someone without any experience of C++ programming, I sometimes wonder how<br>
many C++ programmers are still active in CrossWire. It seems far, far fewer<br>
than when I first linked up with CrossWire in 2008.<br>
<br>
cf. Last month, Karl noted some anniversaries that are passing us by yet<br>
again....<br>
<br>
Which known bugs in the engine will be fixed in v1.8 ?<br>
<br>
Best regards,<br>
<br>
David<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656698.html" rel="noreferrer" target="_blank">http://sword-dev.350566.n4.nab<wbr>ble.com/Release-Wrapup-tp46565<wbr>01p4656698.html</a><br>
Sent from the SWORD Dev mailing list archive at Nabble.com.<br>
<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://www.crosswire.org/mailm<wbr>an/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="m_6386721833253732607HOEnZb"><font color="#888888">-- <br><div class="m_6386721833253732607m_3989808202736948381gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">------------------------------<wbr>------------<div>PGP ID: 0x5fa5cbaecfd5690c<br></div><div>------------------------------<wbr>------------<br></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://www.crosswire.org/mailm<wbr>an/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div></div>