Trip -
Does this mean that VTP in future will not be
useful for people who have existing apps written using static VXML when they
want to extend or maintain them? Will the VXML editor be dropped? I have been
kind of suspecting that development, but there has been no discussion about it
that I have seen.
Several times there have been queries in this mail
list and in the newsgroup asking whether OpenVXML would be capable of generating
static VXML pages. So far, the answer has been "NO". I suggest this is
short-sighted. After all, it is the only feature that has been requested more
than once apparently. I come from the Tellme school of voice app development,
where the mantra is design with call-flow diagrams, implement with static VXML.
It's the best way in my opinion, and although there are some diagrams that would
not admit generation of static VXML due to their nature, it seems that when
possible, static VXML is the way to go -- the apps are faster, easier to test
and easier to debug.
I think VTP should extend OpenVXML to admit a mode
where static VXML can be generated, if possible.
-- Mike
----- Original Message -----
Sent: Wednesday, August 08, 2007 6:15
AM
Subject: Re: [vtp-dev] Re: VTP
futures
Mark,
Yes there are
several future plans for the Voice Tools Project. Currently, the 1.0
release of the VTP has a dependency on WTP 1.0 for most of its editing
capabilities. If you download the preview distribution of the VTP,
youll notice that several things are changing in the upcoming release.
In the future, applications will be edited visually using a flow-chart
style paradigm. The only dependency on WTP remaining will be the GRXML
editors that are built on top of the xml editors provided by the
WTP.
Weve had some project slow down while we
were waiting for a couple of third-party libraries to be cleared by the
foundation. The libraries have been approved and the remaining
components that depended on them have been submitted to bugzilla as patches.
Once these patches are submitted, well begin a round of testing and
documentation prior to promoting the new codebase to release
status.
You are correct that the Voice Tools
Project and OpenVXML are different distributions. OpenVXML is a
commercial packaging of the VTP preview codebase. If you need any
information on OpenVXML, feel free to contact them directly. Definitely
check back here over the next couple of weeks as there should be much more
activity as we head towards release.
Trip Gilman
On 8/6/07
1:33 PM, "Mark" <mark.ericson@xxxxxxxxx> wrote:
Now I understand that VTP and OpenVXML are different
projects. I'm still curious if there is any future planning.
On
8/6/07, Mark < mark.ericson@xxxxxxxxx <mailto:mark.ericson@xxxxxxxxx>
> wrote:
I've been searching for any information on future
plans for VTP and unfortunately can't find anything regarding efforts
beyond 1.0. Please forgive me for my ignorance, I'd appreciate
any references to future plans.
One of the questions I have is,
will VTP move to a more current WTP 2.0 base? it seems to currently
have a WTP 1.0 dependency.
Thank you,
Mark
Ericson
_______________________________________________ vtp-dev
mailing
list vtp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/vtp-dev
_______________________________________________ vtp-dev mailing
list vtp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/vtp-dev
|