Guest Buzby Report post Posted 02/10/2006 11:53 AM Is anyone out there, except us, using VoiceGuide linked with Lotus Domino, rather than with SQL Server etc.? It would be nice to know that we are not alone and perhaps exchange some development tips that we have come across along the way! Share this post Link to post
ktruk Report post Posted 02/10/2006 05:09 PM Guilty as charged. VBS/COM rather than ODBC. Doing server and client. Works surprisingly well. Feel free to get in touch. Share this post Link to post
Guest Buzby Report post Posted 02/10/2006 07:58 PM That's a much quicker reply than expected. Was beginning to think we were the only ones out there! We are doing VBS & COM too - doing lots of nasty agent running as well as document creation/deletion, but overall the stability is not bad, particularly as we are using Domino 7.0.1 which has yet to mature in bug-fix terms. Do you access your DBs through the Domino Server or locally on the Server? Share this post Link to post
ktruk Report post Posted 02/13/2006 11:50 AM Buzby, I've sent you an email !! If you don't get it, let me know. Share this post Link to post
ktruk Report post Posted 03/08/2006 11:40 PM Just an FYI to let anybody interested know that I have a Notes application that reads VG.VGS files, builds a documentation database and links each script/module to audio prompts. This is not perfect, but helps keep larger application developments tracked and documented. If any body is interested, please get in touch. Thanks - ktruk Share this post Link to post
SupportTeam Report post Posted 03/09/2006 12:33 AM Can you post some more information about it? Maybe some screenshots of what the output is? And maybe a sample of an input .vgs and the documented output of your app? Share this post Link to post
ktruk Report post Posted 03/09/2006 10:48 AM Its quite basic, but it reads the VGS file, parses out the modules into separate docs, and for each type, displays a dedicated form for that type. All the basic properties of each module are extracted: The wav files names, the TTS text, the VBS source and module paths (etc). For each WAV you create a separate "prompt" doc and enter your text. You can set a status eg: to do, recorded, etc. The form is 'audited' so any changes to the text are saved away for reference. The main block of text then becomes the basis for getting recordings done, together all the 'todos' becomes the 'script' for the recording session. As each 'module' is opened, it will attempt look up the prompt text(s) for that module. It gets all the texts for all the fields, even if multiple wavs are specified. It can then display the actual prompts on the module. For all the scripts, modules and prompts, there are sorted views, by script, module, prompt-ref, etc. You can search for any word in any prompt. You can drag scripts/modules/prompts to New/todo/complete/obsolete folders and you can work out what goes where. The processing is done by 2 agents. One where you specify the script(s) to read, (and its a read-only one-way process) and one that attempts to link the prompts to the modules to so that you can see if a single prompt is used on many modules. This was just knocked-up for my own use and is not a polished/finished application, by any stretch of the imagination, but could be useful to anybody familiar with Notes/Domino. Some modules are not included (as-yet) such as pager, run, send, email, as I haven't used these modules yet (!) The attached screen-grab gives a flavour of one of the module documents. (Perhaps support will drop the image into this post for me?! - I can't seem to do it myself!) Share this post Link to post
