Thanks Lonnie for the quick response.
I agree and understand the issue about the exporting static VXML scripts.
About the build as deployable plug in, unfortunately I am still not able to do so. I did
-- open plugin development perspective
-- right click on org.eclipse.vtp in the Package explore, Expert, Deployable plug=ins and fragments
-- then not able to see any "available Plug-ins and Fragments" at all. I had cvs check out the while org.eclipse.vtp to my default workspace as well. I had also tried to find "available plug-ins and Fragments" under each of the core/desktop/editors/framework/simdebug...nothing.
-- in fact I also blindly try to create a New wroking set, and click and choose all 34 working set contents of the org.eclipse.vtp.XXX
apparently I am missing something important? The Eclipse I use is downloaded from the OpenMethod site. ( not from the Speecktek CD).
One last question, if I plan to deploy on another target VXML browser of which is not W3C vxml 2.0 (yet), where in the vtp java code/runtime or within Eclipse that I can change it to some other namespace? Apparently the default namespace that comes out of OpenMethod is VXML 2.0. This same question applies if I want to try on a VXML 2.1 target. When I do a search for "2.0" I found about a hundred appearances ...may be this one?
\workspace\org.eclipse.vtp\editors\plugins\org.eclipse.vtp.doc\references_toc.xml(9): <topic label="VoiceXML 2.0 Specification" href=""/>
Thanks
Ben Kao