Hi David,
Thanks for the wiki page. No, we're not about to release 2.0. The
purpose of 2.0 has been a more intuitive API, including regular
camelCase naming of API methods. We've been slowly working toward this
for a number of years, attempting to not breaking API compatibility with
older frontends by leaving the old names around but adding a deprecated
flag to them to produce warnings. When we do finally release 2.0, all
deprecated methods will be removed and we will break API compatibility.
Each .x release, we normalize a few more methods, deprecating the old
names. I only mentioned it because frontend developers might get new
warnings in their code if they are using any of soon to be newly
deprecated methods.
Thanks for asking,
Troy
On 10/22/2016 03:11 AM, David Haslam wrote:
Hi Troy,
Some time back, I added a placeholder in this wiki page.
https://crosswire.org/wiki/Alternate_Versification#1.8.0
Should I change that from 1.8.0 to 2.0 ?
Once the new version is released, I will list all the new av11ns in this
section of the page.
Are there any others besides the three French ones from domcox?
Best regards,
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656504.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
