Table of contents does not completely appear for Anchor Bible Dictionary
I can only read the first 30 entries under each letter of the alphabet. For example, under A the last entry is Abigail. In the book, the last entry is Azzur. Same for "B" and so on.
So far, I'm disappointed with the many problems of the iphone / ipod application. The concept is a truly good one, and I'm excited about the possibilites, but obviously someone did not do adequate testing and jumped the gun on this. I hope you guys can finish the programming soon ... this was not a very good start out of the gate.
Comments
-
I think it is a bug that the TOC subindex has a limit of 30 items, and I'm sure Dave knows about it (well I've reported the same bug a couple days earlier [;)])
I see the app differently though. I really appreciate all the lengths Logos went into to making the app, and let us have our library in our hands as soon as possible. Don't you think it's a blessing for us Logos + iPhone users? I think the app is nicely designed, it may have some shortcomings at the moment but it's getting better everyday. For me it's not a big problem, it's far better to have the convenience of the library in our hands while we wait for the app to improve ("Already, and getting there"), than to wait and not see when there would be something that we can use ("Not ready, not yet and maybe never"). So thanks to everyone at Logos, and Kudos to you all!
0 -
This problem exists on lots of resources. Lexicons are difficult to use since you can't go to a word through the TOC.
[quote user=""]
So far, I'm disappointed with the many problems of the iphone / ipod application. The concept is a truly good one, and I'm excited about the possibilities, but obviously someone did not do adequate testing and jumped the gun on this. I hope you guys can finish the programming soon ... this was not a very good start out of the gate.
I would disagree about jumping the gun. In my opinion, the sooner you get it in the hands of the user the better. Thats the best way for Logos to get user feedback, resolve issues and build features that users want. It's basically a free app, so what is the down side for you that Logos has released it?
0 -
I agree with what Amy has to say. Thanks for the blessings.
I think you will find the same issue with any book that has a lengthy TOC. for example, BDAG is the same, but when I use BDAG, I know what word I want to read, so I just use the search function and I am taken directly to that entry. I have not tried it, but I believe the it will work with finding all the citations for a certain scriptural reference.
0 -
Lexicons and dictionaries have thousands of entries, so for performance reasons we clipped the display to a manageable number. You should see support for pulling down "More.." in the future.
But our thought was that when there are hundreds/thousands of items, searching probably makes more sense than browsing the list.
-- Bob
0 -
The limited table of contents is an intentional compromise due to the size of the data. We will likely improve the way TOC work in a future release.
0 -
I would like to see the full table of contents, even if you must select "more."
0 -
I have another program on my iPhone that allows me to search for words in a classical Greek lexicon. As I type letters in it dynamically filters the list. It is a really quick way to find words since just a few letters will usually display the word I want on the screen. Another option would be to add another layer in the the TOC hierarchy.
What ever you end up deciding, I think you have done a good job and I love the product. Thanks for your efforts.
0 -
Removed
0 -
Bob Pritchett said:
But our thought was that when there are hundreds/thousands of items, searching probably makes more sense than browsing the list.
I would disagree. I might not know the exact term used and browsing contents is sometimes easier to find what terms might be listed.
Could you do the following?
-D
--Da - Di
--Di - Du
etc... just adding sub TOCs to get the overall TOC broken down into manageable segments?0 -
John Eggen said:
Could you do the following?
-D
--Da - Di
--Di - Du
etc... just adding sub TOCs to get the overall TOC broken down into manageable segments?That is the plan. The problem is finding the time to do it
0
