[vtp-dev] Execution API thoughts

[Brent D Metz <bdmetz@xxxxxxxxxx>]

For tomorrow's call, and for anyone
who can't make it, here is what I think the implementation of a generic
Execution API would need:

Launch configuration type: org.eclipse.vtp.launching.voicexml
 - Run mode only

Launch configuration dialog tab group:
 - Default pane to choose URL or
file in workspace
 - Browser chooser pane with custom
configuration composite

ILaunchConfiguration implementation:
VoiceXMLBrowserLaunchConfiguration
 - Define common configuration
parameters: URL, ???
 - Delegate launch() method to
IVoiceXMLBrowser


IVoiceXMLBrowser to interact with browser
  start()
  stop()
  pause()?
  setProperty(String propertyname,
Object value)
  throwevent(String eventname)
  sendKeypress(char c)
  sendText(String text)
  sendSI(String SI[])
  boolean hasCapability(String
capability)

VoiceXMLBrowserDebugTarget to implement
IDebugTarget to handle starting,stopping browser,
  notifying UI of changes, loading
Browser UI controls

Throw DebugEvent objects of type MODEL_SPECIFIC
into the Eclipse Debugging framework via 
DebugPlugin.getDefault().fireDebugEventSet()
  - Use setData() to attach VoiceXMLBrowserEvent
objects

New VoiceXMLBrowserEvent object to define
the following VoiceXML-specific event types:
  - Received Keypress
  - Received Speech
  - Received SI
  - Log tag message
  - Generic log message
  - Sent text/audio to user
  - Entered line
  - Loaded resource

--
Brent D. Metz
Enterprise Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be possible."
- Alan Kay