Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[vtp-dev] Some first insights into the JVoiceXML text based interface

Hi all,

I attached some first screenshots of the text based implementation platform, to give you a short impression about my current activities.

log-view
Here, you can see the output of the logging pane. This was the current implementation.

dialog-view-active
I added another register card to the logging pane to monitor the dialog. I wanted the dialog pane at this point since there is already the DTMF keypad. The input texts should be nearby. This pane is only active (visible) if the browser can be interactive (org.eclipse.vtp.launching.IVoiceXMLBrowser.CAPABILITY_INTERACTIVE). This way, browsers that do not have this capability will simply show the logging pane.

The output of SSML is not really readable. An immediate idea would be to use an XSL transformation to generate some more readable text, probably with some font settings, e.g. bold to indicate emphasizing.

dialog-view-done
The dialog view after a message was sent to the browser. Therefore I use org.eclipse.vtp.launching.VoiceXMLBrowserInput

Still missing is a field for the confidence score.

Now I need some implementation for a hangup. There is already a button for it. First I though to use org.eclipse.vtp.launching.IVoiceXMLBroser.stop() for it, but there is a javadoc comment that this method should not be used to generate a hangup.

That's why I would like to add another method hangup() which can be used for that purpose. Similar to sendInput() it would only be used if the browser is interactive.

Unfortunately this will break the compatibility with the exisiting code of other browsers like TellMe. There needs to be one more method that simply does nothing since this browser is not interactive.

Shall I continue with this approach? What should be different? Are there any more problems?

~dirk

Attachment: jvoicexml.zip
Description: Zip archive


Back to the top