Programming Do's and Dont's

[Live2 Bicycle]

See attached screen shot.

I have started not defining my prompts in my scripts as variables.  When I define a prompt I simply browes to the prompt container and choose the prompt I want to play.

Is this a bad technique / habit to get in?

[chrismanuh]

I think it's personal preference and also the complexity of your script. suppose you have a prompt named hello.wav that you've used throughout your script. Suppose hello.wav is being used by other scripts as well so you can't simply replace it as you wish. Now suppose your customer ask you to use helloworld.wav instead of hello.wav in one of your scripts, you'll have to comb through your script changing every instance.  If you've used a variable, you'll have just one place to make your chance. it's quick and chances of making a mistake is reduced.

[roymarinf]

The problem is when you have a lot of prompts. Everytime you select a new script in the application manager you need to fill ALL the script parameters. My practice is to use like a parameters only the prompts that i know will be changing regulary, like welcome prompt.

[chrismanuh]

You shouldn't mark your variables as Parameters if you don't intend to change them when you deploy.  If the variables aren't marked as a parameter, they'll not appear in the application management page.