Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Voicetools » Feedback on VTP's future
Feedback on VTP's future [message #11069] Wed, 01 March 2006 20:20 Go to next message
Brent D. Metz is currently offline Brent D. Metz
Messages: 10
Registered: July 2009
Junior Member
Hi,

I thought I'd let everyone know that we're looking for feedback on where to
go next with the VTP. We've completed what we originally set out to do (W3C
standard editors) and added a little more (VoiceXML Browser & API) -- so
what would you like to see in future voice tools?
Re: Feedback on VTP's future [message #11080 is a reply to message #11069] Mon, 06 March 2006 11:56 Go to previous messageGo to next message
Eclipse User
Originally posted by: mshaw.tesco.net

Brent D. Metz wrote:
> Hi,
>
> I thought I'd let everyone know that we're looking for feedback on where to
> go next with the VTP. We've completed what we originally set out to do (W3C
> standard editors) and added a little more (VoiceXML Browser & API) -- so
> what would you like to see in future voice tools?
>

Hi Everyone,

Top of my wish list would be frameworks for interactive VXML debugging
and automated unit testing that would run in an Eclipse environment.
OK, I know this would not be a small addition... :-)

DEBUGGING:

I guess that creating a VXML browser is outside the VTP scope, but
perhaps defining a remote debugging API isn't. I would see this as
providing a way for a remote system to be informed of events in a
browser and to be able to issue commands to the browser. Hopefully
browser vendors would then provide implementations. A debug session
would run in a VXML debug perspective. Some API functions would be;

Accept debug request, (connection properties, ANI etc, so the remote
debugger can be notified when the test call arrives)

Inform the debugger when events such as starting a form, starting to
play a prompt, finishing a prompt, applying a grammar to an utterance
etc. occurs

Inform the debugger when it processes a new element

Set a break point on a VXML element

Single step over elements

TESTING:

If a debug framework gets developed I expect it could be adapted to
provide automated unit testing



Does this sound sensible / feasible?

Regards,

Marcus.
Re: Feedback on VTP's future [message #11087 is a reply to message #11080] Mon, 06 March 2006 14:54 Go to previous messageGo to next message
Brent D. Metz is currently offline Brent D. Metz
Messages: 87
Registered: July 2009
Member
Thanks for the feedback. It's absolutely feasible and we did our initial
browser APIs with debugging as a future goal. BTW, it's technically possible
to use our existing APIs to create some level of testing. You can
programmatically launch a browser, send it input, and listen for log events
to come back. Not quite a unit test with variable introspection but it's a
start.

"Marcus Shaw" <mshaw@tesco.net> wrote in message
news:duh839$p70$1@eclipse.org...
> Brent D. Metz wrote:
>> Hi,
>>
>> I thought I'd let everyone know that we're looking for feedback on where
>> to go next with the VTP. We've completed what we originally set out to do
>> (W3C standard editors) and added a little more (VoiceXML Browser &
>> API) -- so what would you like to see in future voice tools?
>
> Hi Everyone,
>
> Top of my wish list would be frameworks for interactive VXML debugging and
> automated unit testing that would run in an Eclipse environment. OK, I
> know this would not be a small addition... :-)
>
> DEBUGGING:
>
> I guess that creating a VXML browser is outside the VTP scope, but perhaps
> defining a remote debugging API isn't. I would see this as providing a
> way for a remote system to be informed of events in a browser and to be
> able to issue commands to the browser. Hopefully browser vendors would
> then provide implementations. A debug session would run in a VXML debug
> perspective. Some API functions would be;
>
> Accept debug request, (connection properties, ANI etc, so the remote
> debugger can be notified when the test call arrives)
>
> Inform the debugger when events such as starting a form, starting to play
> a prompt, finishing a prompt, applying a grammar to an utterance etc.
> occurs
>
> Inform the debugger when it processes a new element
>
> Set a break point on a VXML element
>
> Single step over elements
>
> TESTING:
>
> If a debug framework gets developed I expect it could be adapted to
> provide automated unit testing
>
>
>
> Does this sound sensible / feasible?
>
> Regards,
>
> Marcus.
Re: Feedback on VTP's future [message #12448 is a reply to message #11087] Thu, 09 March 2006 13:12 Go to previous message
Eclipse User
Originally posted by: mshaw.tesco.net

Hi All,

Brent's response to my debugging suggestion is very interesting. Would
be great to have an interactive debugger...


One other thing I would like to see would be some documents / tutorials
to help consolidate where the VTP currently stands. For instance, a
tutorial on how the Tell Me browser was developed would be very helpful
for developing other browser implementations.

Regards,

Marcus.
Re: Feedback on VTP's future [message #573659 is a reply to message #11069] Mon, 06 March 2006 11:56 Go to previous message
Eclipse User
Originally posted by: mshaw.tesco.net

Brent D. Metz wrote:
> Hi,
>
> I thought I'd let everyone know that we're looking for feedback on where to
> go next with the VTP. We've completed what we originally set out to do (W3C
> standard editors) and added a little more (VoiceXML Browser & API) -- so
> what would you like to see in future voice tools?
>

Hi Everyone,

Top of my wish list would be frameworks for interactive VXML debugging
and automated unit testing that would run in an Eclipse environment.
OK, I know this would not be a small addition... :-)

DEBUGGING:

I guess that creating a VXML browser is outside the VTP scope, but
perhaps defining a remote debugging API isn't. I would see this as
providing a way for a remote system to be informed of events in a
browser and to be able to issue commands to the browser. Hopefully
browser vendors would then provide implementations. A debug session
would run in a VXML debug perspective. Some API functions would be;

Accept debug request, (connection properties, ANI etc, so the remote
debugger can be notified when the test call arrives)

Inform the debugger when events such as starting a form, starting to
play a prompt, finishing a prompt, applying a grammar to an utterance
etc. occurs

Inform the debugger when it processes a new element

Set a break point on a VXML element

Single step over elements

TESTING:

If a debug framework gets developed I expect it could be adapted to
provide automated unit testing



Does this sound sensible / feasible?

Regards,

Marcus.
Re: Feedback on VTP's future [message #573683 is a reply to message #11080] Mon, 06 March 2006 14:54 Go to previous message
Brent D. Metz is currently offline Brent D. Metz
Messages: 87
Registered: July 2009
Member
Thanks for the feedback. It's absolutely feasible and we did our initial
browser APIs with debugging as a future goal. BTW, it's technically possible
to use our existing APIs to create some level of testing. You can
programmatically launch a browser, send it input, and listen for log events
to come back. Not quite a unit test with variable introspection but it's a
start.

"Marcus Shaw" <mshaw@tesco.net> wrote in message
news:duh839$p70$1@eclipse.org...
> Brent D. Metz wrote:
>> Hi,
>>
>> I thought I'd let everyone know that we're looking for feedback on where
>> to go next with the VTP. We've completed what we originally set out to do
>> (W3C standard editors) and added a little more (VoiceXML Browser &
>> API) -- so what would you like to see in future voice tools?
>
> Hi Everyone,
>
> Top of my wish list would be frameworks for interactive VXML debugging and
> automated unit testing that would run in an Eclipse environment. OK, I
> know this would not be a small addition... :-)
>
> DEBUGGING:
>
> I guess that creating a VXML browser is outside the VTP scope, but perhaps
> defining a remote debugging API isn't. I would see this as providing a
> way for a remote system to be informed of events in a browser and to be
> able to issue commands to the browser. Hopefully browser vendors would
> then provide implementations. A debug session would run in a VXML debug
> perspective. Some API functions would be;
>
> Accept debug request, (connection properties, ANI etc, so the remote
> debugger can be notified when the test call arrives)
>
> Inform the debugger when events such as starting a form, starting to play
> a prompt, finishing a prompt, applying a grammar to an utterance etc.
> occurs
>
> Inform the debugger when it processes a new element
>
> Set a break point on a VXML element
>
> Single step over elements
>
> TESTING:
>
> If a debug framework gets developed I expect it could be adapted to
> provide automated unit testing
>
>
>
> Does this sound sensible / feasible?
>
> Regards,
>
> Marcus.
Re: Feedback on VTP's future [message #573743 is a reply to message #11087] Thu, 09 March 2006 13:12 Go to previous message
Eclipse User
Originally posted by: mshaw.tesco.net

Hi All,

Brent's response to my debugging suggestion is very interesting. Would
be great to have an interactive debugger...


One other thing I would like to see would be some documents / tutorials
to help consolidate where the VTP currently stands. For instance, a
tutorial on how the Tell Me browser was developed would be very helpful
for developing other browser implementations.

Regards,

Marcus.
Previous Topic:Feedback on VTP's future
Next Topic:Stopping an IVoiceXMLBrowser implementation
Goto Forum:
  


Current Time: Fri Oct 31 12:22:18 GMT 2014

Powered by FUDForum. Page generated in 0.02419 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software