Thoughts about Bible Study Builder....

xnman

Not trying to complain but to look at Bible Study Builder (BSB) with a "critiquing eye"… I know people will disagree with me, but these are my thoughts which I share…

1. First, I think BSB has merit. I think it is extremally lacking in formatting capabilities. We have Sermon Builder (SB), Workflows (WF), Passage Lists (PL) and etc. and etc. But I think the idea of having what BSB seems to want to do is definitely worth the time. But I do think BSB is just another "note taking file" with less formatting capabilities than Notes themselves.
2. I wonder if SB, WF and BSB could be put into one "feature" and could combine all the "functions" of the others into that new one "feature". Call it BSB or whatever.
3. For example, I like WF and SB because of the formatting features, which I think still could be enhanced, but are still better than BSB. I would like for these features to be rolled into BSB (if BSB is to be the one that wins out)and maybe import Sermon Builder files and Workflow files into BSB and thus have one function I could use for all my classes, studies or preaching, even paper writing.
4. WF files do not appear in "Document" but SB and BSB files (and others) do. I would like one raspatory to go to to find all my "created files" which I create in Logos. Currently, for WF files, I have to go to "Guides" to find the files.
5. If we are going to continue to have all these different "file systems" (SB, WF, BSB, etc) then make all of them able to be seen on Mobile App and in Documents. Workflows currently does not.
6. I am of the opinion, it is better to have one "feature" than the many, and then work on improving that one "feature".
7. I honestly think that Logos will not keep on supporting all these different file structures, sometime in the future, as they will eventually become cost prohibited. I programmed years back and I know after a while it takes time and manpower to go back and understand the code so that it can be updated and then to update it. And believe me, all program code has to be updated and maintained if it is to be relevant to the way people use it. And cost of manpower these days is expensive.

For those reasons…. I believe it would be good have one "feature" do do what all these "features" do.

But that's my 2 cents, which if you add $3.00 to, you can buy a cup of coffee in a lot of places.

I am xnman, and I approve this post. 😎lol

Justin Gatlin

Your input for workflows is saved in notes, where each workflow gets its own notebook. I think that sermon builder and Bible study builder should be combined so you can have the formatting and slide generation from sermon builder and the new features of Bible study builder, but I worry they won't be because they are at different subscription tiers. I don't see how workflows could be combined since they are such a different tool.

DAL

Maybe just combine SB and SBB, but not the WF’s

SB needs to become a full fledged word processor in order to be effective.