PBB Priorities (IMO!)

I'm sure the developers know what they're doing without my 'help', but after two weeks of working with PBBs, I thought I'd give my take on what I think the priorities should be going forward. I'm sure other's opinions will vary [:)]

Bug fix: Fix the crashes when compiling some documents
Bug fix: Remove the need for us to 'clean' .docx files before compiling.
Give us some documentation (as a minimum, a list of tags. We can create a wiki page from there)
Bug fix: Prevent milestones showing in the TOC
Bug fix: Prevent resource links being created on top of datatype links
Add support for adding non-English headwords as milestones
Add support for footnotes
Add a PBB option to "Copy location as" (or have PBBs support one of the other formats). Make it easy for us to copy datatype locations as well as resource-specific locations
Add support for tagging lemmas with morphology codes.
Add support for Word's hyperlinks
Bug fix: Fix the Greek/Hebrew font issues
Add support for page numbers from Word (I know this is tricky)
Add support for images and ideally tables
Give us tags so we can add fields to PBBs (vital for Bibles, important for all good quality PBBs).
Give us some generic datatypes so we can create PBBs that use datatypes not currently supported (e.g. a Book of Mormon). We'd need a String, Numeric and NumericHierarchy as minimum, I think.
Add support for hidden milestones (so we can split long articles without creating TOC entries).

I think that's enough to be getting on with [:D]

Find more posts tagged with

Comments

MJ. Smith

You left one important one out:

give us the requirements for each of the document types we can create e.g. commentary, daily devotional ...

JimTowler

https://community.logos.com/discussion/comment/257062#Comment_257062

I have been busy, so have only spent 30 minutes taking a quick peek at PBB (or is it just PB now?).
Anyway, using the Logos 4 PC client, the COM API exposes events that fire as you move around open resources.
Part of the event data is the start and end link (often the same value) of the current location. It seems its the correct format to be used directly for PBB. Hence it will be easy to write a tiny app that could sit behind a toolbar/ribbon button in Word, that could place the required PBB tags, milestone etc at the current Word cursor location, to match the last Logos navigation update. I intend to work on such a thing over the next few days or weeks as I have time. I encourage others to do so also. Or even better, for Logos to use a new developer to do it themselves directly in the app. I would not wish Logos to delay more critical aspects.
I was thinking I might step thru the few thousand resources I have, and compile a list of the link types for each resource I have, and see which already work in PBB. If I do this, I,ll start with some of what are my more important resources. Sorry about poor formatting of this post. iPad and this forum dont play nice!

Mark Barnes

https://community.logos.com/discussion/comment/257120#Comment_257120

I was thinking I might step thru the few thousand resources I have, and compile a list of the link types for each resource I have, and see which already work in PBB.

I've already tried to do that as best I can (without a great deal of success). If you find out more than I did, could you update the Wiki? I'm particularly interested in finding out:

The syntax for the various datatypes links (e.g. ECF) that aren't in the Wiki yet.
The syntax for resource links that use a reference (other than page numbers).

Hence it will be easy to write a tiny app that could sit behind a toolbar/ribbon button in Word, that could place the required PBB tags, milestone etc at the current Word cursor location, to match the last Logos navigation update.

Great idea!