API for Logos 6

I wondering if there's an API for Logos 6 that software developers can use to integrate applications with Logos. Back a few years ago I looked into this and there was an API developer website on the main Logos.com website. That seems to have been removed.

Is the API still available? Can you point me to the right location to looking into this?

Best regards,

Jon Rothlander

Austin, Texas

Find more posts tagged with

Comments

Rosie Perera

The Logos COM API is documented here: https://wiki.logos.com/Logos_4_COM_API. That documentation was written when Logos 4 was the current version, but I have not heard that the API has been removed, so it probably still works the same way.

Wade Wickman

Yes, the COM API from version 4 is still there and seems to be working roughly the same. I'm currently using it to develop a Microsoft Office OneNote add-in integration to Logos6. In addition to the documentation sighted above, there is a .NET sample app here: https://wiki.logos.com/Logos_4_COM_API_Demo_Project that also compiles and runs quite easily. I even converted it to Visual Studio 2015 RC with not issues at all.

Doug Trick

Any idea why the COM API seems have stopped working for me? It stopped about a week ago, right after I'd updated Logos software (currently running 6.6 SR-1 6.6.0.0059), and after upgrading from Win7 to Win10 about the same day. So I don't know if this has to do with a change in the Logos version or in the operating system itself.

I like to launch Logos with a specific desktop layout. For example, when I want to work on the book of Daniel, I launch Logos with the following Power Shell script:

$launcher = New-Object -com "LogosBibleSoftware.Launcher"
$launcher.LaunchApplication()

do {} until ($logos = $launcher.Application)
$logos.LoadLayout("Daniel")

The shortcut I use to run that script is:

%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File "C:\Users\ … Auto\PS1\Daniel.ps1"

Suddenly that has stopped working. Any idea what may have happened (and how to fix it)?

Doug

Wade Wickman

Are you getting a specific error or anything?

Can you try running your shortcut with the explicit path to PowerShell.exe instead of the environment variable of %SystemRoot% Not sure if that is the same or automatically registered in Win 10. Although I would think so.

Given PowerShell is the same version from 7 to 10 I'd think your command line switches should be fine.

The only other thing of off the top of my head without any error info is possibly the COM library registration got mucked up on the upgrade from 7 to 10.

I'll double check the Logos version I'm running, but I'm sure it's the latest and it's working for me on Win 10.

Doug Trick

Thanks for this, Wade. No, there's no error message. Nothing (visible) happens - Logos doesn't start. I tried your suggestion and it didn't make any difference. I then made a copy of the folder and placed it in my "Documents" folder, and no difference. I copied the text from the "Properties" box of the shorcut and pasted that into a DOS window, to see if there would be any error messages reported there. After pasting

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File "C:\Users\Doug Trick\Documents\PS1\Daniel.ps1"

into the DOS box and hitting <enter>, again nothing happened (except that the DOS box closed).

Yes, I wonder if something got messed up in tTHECOM library registration at some point. I've tried reinstalling Logos 6 (to see if that would correct the library registration or whatever) but when I try to run the installer, it just says I already have the most recent version installed.