API: 4.0d B1: Need notes or docs on new COM API Please

JimTowler

(Maybe we need a new forum for COM API so to not put this stuff into the PC Beta one?)

The Release Notes claim:

4.0d Beta 1

Logos 4.0d Beta 1 (v4.04.3.9992) was released on May 25, 2010.

New Features

COM API implemented.

I have created a new VB Application, and can "see" the new "Logos Bible Software 4 Type Library".

It appears to have an interesting selection of goodies, including what might let us "walk" the list of resources.

I have some code that compiles, however this following code always reports 0 resource, as i have no idea what to put in the string value: "All", "Bible" and "*" returns 0 records.

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button5.Click
' Logos4

Dim LCollection = L4L.Application.Library.GetResourcesByResourceType("All")

AddLine("Resource Count = " & LCollection.Count)
AddLine()

        For Each LResource As L4.LogosResourceInfo In LCollection
            AddLine(LResource.ResourceId)
            AddLine(LResource.ResourceType)
            AddLine(LResource.Title)
            AddLine(LResource.AbbreviatedTitle)
            AddLine(LResource.Version)
        Next

End Sub

Find more posts tagged with

Comments

JimTowler

OK - This works ...

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button5.Click
' Logos4

Dim LCollection = L4L.Application.Library.GetResourcesByResourceType("text.monograph.bible")
'Dim LCollection = L4L.Application.Library.GetResourcesMatchingQuery("type:bible")

AddLine("Resource Count = " & LCollection.Count)
AddLine()

        For Each LResource As L4.LogosResourceInfo In LCollection
            AddLine("ID", LResource.ResourceId)
            AddLine("Type", LResource.ResourceType)
            AddLine("Title", LResource.Title)
            AddLine("Short", LResource.AbbreviatedTitle)
            AddLine("Version", LResource.Version)
            AddLine()
        Next

End Sub

JimTowler

https://community.logos.com/discussion/comment/132356#Comment_132356

Sample output:

Resource Count = 197

ID: asv
Type: text.monograph.bible
Title: American Standard Version
Short: ASV
Version: 2009-10-26T20:39:22Z

ID: bhsmorph
Type: text.monograph.bible
Title: Biblia Hebraica Stuttgartensia—Morphologically Tagged Edition
Short: BHS
Version: 2010-02-01T20:29:37Z

ID: darby
Type: text.monograph.bible
Title: 1890 Darby Bible
Short: DARBY
Version: 2009-10-27T01:19:39Z

ID: gs-netbible
Type: text.monograph.bible
Title: The NET Bible
Short: NET
Version: 2009-11-03T20:28:44Z

ID: gs-netnoteless
Type: text.monograph.bible
Title: The NET Bible First Edition (Noteless)
Short:
Version: 2008-10-18T05:29:47Z

etc ...

JimTowler

https://community.logos.com/discussion/comment/132356#Comment_132356

This gets the same count as in Library using Logos4.

Dim LCollection = L4L.Application.Library.GetResourcesMatchingQuery("rating:>=0")

Bradley Grainger (Logos)

The documentation has been uploaded to http://wiki.logos.com/Logos_4_COM_API

JimTowler

https://community.logos.com/discussion/comment/132440#Comment_132440

The documentation has been uploaded to http://wiki.logos.com/Logos_4_COM_API

Thanks Bradley.

Do you want bug reports and feedback here?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/132544#Comment_132544

Do you want bug reports and feedback here?

Yes, let's keep the discussion in this forum while the API is still "in beta". (We'll consider creating a new forum for it, or merging it with the "Biblia API" forum once we release.)

BTW, the choice to put the documentation on the wiki was deliberate: you're invited to clarify the object descriptions, method behaviours, etc. as you explore the API. (Please keep the wiki page focussed on describing the existing API; hopefully it's obvious that editing the wiki to describe a new method is not a good way to propose an addition to the API...)

spitzerpl

https://community.logos.com/discussion/comment/132555#Comment_132555

the choice to put the documentation on the wiki was deliberate: you're invited to clarify the object descriptions, method behaviours, etc. as you explore the API

Excellent idea.