[sword-devel] leningrad, av11n, xiphos
Troy A. Griffitts
scribe at crosswire.org
Sat Apr 11 13:39:20 MST 2009
Thanks for the report Matthew. The primary practice we used to
encourage with using the engine was code like:
VerseKey commonVerseKey;
commonVerseKey.Persist(true);
module1.setKey(commonVerseKey);
module2.setKey(commonVerseKey);
module3.setKey(commonVerseKey);
module4.setKey(commonVerseKey);
commonVerseKey = "jn.3.16";
This would position all modules to the entry for John 3:16.
Now in the world of av11n, modules can have keys that contain different
books, different maxChapters per book, different maxVerses per chapter,
different orders of book-- basically, in the same way as currently
focusing any individual GenBook causes us to repopulate the navigation
controls, so now focusing any Bible should cause the same activity.
Does this make sense?
-Troy.
Matthew Talbert wrote:
> A big thank you to whoever put up the Leningrad module for testing.
>
> After a few minutes of testing, it is obvious that Xiphos has a long
> way to go to support av11n. It is impossible at this point to even
> determine whether there are any problems in sword in this regards,
> because we are clearly assuming in way too many places that we are
> using KJV versification. Just a few of the problems we have:
>
> 1. Book dropdowns do not show books in correct order.
> 2. Book dropdowns show books that aren't actually present.
> 3. Treeview navigation has the same problems
> 4. It is impossible to navigate to a verse that doesn't exist in KJV,
> even though they show up correctly in the chapter view (eg, Mal 3:24
> actually goes to 1 Chronicles, but our navigation says it is in Mal
> 4:6; quite confusing)
>
> I'm no expert at how this stuff is implemented in sword or Xiphos, but
> it is apparent that we have some issues.
>
> Matthew
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel
mailing list