I'd like to propose a change to the way we package the various elements of our software. I think we should go ahead and separate the SDK type features of the software from the main development environment package (OpenVXML). This would result in a top-level component named OpenVXML that would include the visual design environment, server runtime and web app exporter, and the launcher. The elements floating around to allow developers to extend the platform would be gathered into a new top-level component called either Voice Tools Project SDK or OpenVXML SDK.
The split would not only encompass the codebase but the documentation elements as well. I think this will highlight some of the architectural features inherent in the framework (such as support for other interaction types) otherwise hidden away when packaged into OpenVXML. Current SDK items would include the wizards for creating Voice Formatter projects, documentation and wizards related to building custom modules, and any elements associated with supporting other interaction types. This component could also host any efforts to expand the export types of OpenVXML or other packages based on the codebase. Trip Gilman _______________________________________________ vtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/vtp-dev
