How would I been able to embed the VerbotPlayer?

[karell]

How could I embed the VerbotPlayer in my own software so that the player could become an interface (input/output) to my application?

I am trying to create a new type of active/passive interface and this could be very interesting.

[JonC]

Not quite sure exactly what you mean by this Karell and I don't think there is an easy way to do this, but:
You can get the Verbot to startup with:
Verbot5Engine.exe --input="input text"
(where the --input command provides an initial 'spoken/typed' input.
Now, if you wanted the bot to make a spoken reply to something happening on your website, then provided that the "something" was translated into an input (to replace "input text") then you should start the Verbot and get a response.
---
Second, on startup the bot can execute a _startup rule. This allows you to decide on a sequence of "startup" events etc - depending on how you write the _startup rule.
---
Now, I know nothing about Website design; but it is also worth bearing in mind that the Verbot can accept input from a Speech-to-text program.
Therefore, in principle, it can accept typed input from an external source.
This suggests to me that you might be able to "fool" the bot into thinking that the input from your Website was STT input.
---
My final thought is that using c# vcm code, you could (in principle again) persuade the bot to accept input into a vcm function and use that to control the 'bots actions, since the 'bot normally expects to get data out of a vcm function.
---
I'm sorry to be a bit vague in my suggestions, but Wedsite-bot interfacing is definitely not something I've ever tried!

[karell]

Hi JonC,

Thanks for the reply,

Actually, I'm trying to embed Verbot into a Windows Form application, NOT a website.

My fault, I was very broad in my question.

More precisely, I'm trying to design a desktop application that has section that includes the Verbot player.

[JonC]

Still not really my area (and I mis-read your post you did say "own software" not website after all!), but using the command line startup should get the Verbot "up and running" when your software starts.
---
Alternatively, the Verbot has the command line in all of its outputs, so perhaps you could tackle the problem the other way around, using the Verbot _startup rule to activate your own software?
---
I am still not clear as to whether you intend the Verbot to be permanently visible or to "pop up" when it is needed.
If the latter, then the command line start up and an <exit> command to close it again once it has "done its thing" might be a solution, perhaps coupled with the use of the <load knowledgebasename> command to make sure it is talking sense (I think that would need to be mediated by the "input text" mentioned earlier directing <send ...> commands on startup).