One of the wishes made for e-Sword is that for the resources to be able to be sorted out as "Bookshelves." On this idea I really don't know if its a good thing or not to include in e-Sword.
Ignoring your request to not answer the question, your example highlights the dilemma between staying true to the original principles, and honouring user's requests. In this specific instance, I think that "Bookshelves" would help new users, _if_ the books are setup by both subject matter, and perquisite knowledge level. However, done wrong, it will be even more confusing to new users, than the current UI.
I wonder when considering these things, is it in your consideration to whom the program is targeted to?
When I submit RFEs, I tend to ignore the target audience, except when it comes to reasons to not deploy the feature.. In most instances, I state where it might hinder the target audience, in comparison to how it helps those I find to be the "typical" user. In at least one instance, Rick has implemented the RFE, even though the case I presented concluded that the overall effect on the program would be negative, rather than positive.
and that is to whom the program is actually targeted to; the type of user.
Last year, Libronix was targeting pastors, with the aim of getting Libronix declared the official Bible Study Software for the church. The idea being everybody in the congregation purchases their software. They are doing this, despite knowing that their program will end up as shelfware for more than half of their customers. (They also know that the majority of the purchasers of their sub-$400 packages will not purchase any more resources. IIRC, purchasers of their sub $200 packages never purchased additional resources.)
who use this program, the question comes to mind of what is the balance between what their expectations are for e-Sword and for whom the program has been targeted for?
This gets back to wanting to keep with the tried, and true, even though one might have outgrown it.
jonathon