Well we had an internal discussion about it and I was voted down in first round :/ The other guys felt it would be competitive to our job, which I didn't.
But I guess there's no problem in sharing my thoughts about it. The idea was to have a modular application, managed by guice. VoiceIt in the beginning would provide only a way to receive DTMF's, to keep it simple. Your modules would consist of panels that implemented courtesy methods, so in your special application you could add grammar support etc, this would be configured by extending a special VoiceIt application similar to the Wicket application. So you would not program in the ordinary wicket way. But just use java and the special panels (which where similar to ordinary wicket panels), I think that could speed up development a lot. In the future there would be to bonus options one was to be throwing in our own custom db framework (where you can configure almost every thing). And the big thing, integrating support for Eclipse VTP or alternately ripping their ui (I've got permission for that). This was some thoughts, I probably forgot something. Oh and one could never know what could happen if you wrote off list to me. Regards Nino 2010/2/1 shetc <[email protected]> > > Nino -- before I go recreating the wheel, do you know whatever happened > with > something called VoiceIt? > http://www.ohloh.net/p/voiceit http://www.ohloh.net/p/voiceit > -- > View this message in context: > http://old.nabble.com/Wicket-VoiceXML-framework--tp22058044p27403820.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
