How to execute a skill script at command line

You have to have graphics if you use a GUI. -nograph will not work. You need the hi- functions.

Consider your architecture. You should actually have 3 levels of code:

1.  create and display the GUI

2. the form callback: This interprets the form and fields and calls the database operation function.

3. The database operation function. It is independent from the GUI and knows nothing about it. It is driven by the values of the arguments to the function. When executed as part of the form, the form callback reads the form fields, generates the database operation argument values and calls the function. When called from a script, the script figures out the argument values and then calls the function, no form involved.

It is not hard to refactor your code in this way. You already create the form. From your database operation function, separate the form analysis into a callback and the execution into its own function. Probably about 10 lines of code. The database operation function should not reference the form at all, everything should be passed through the arguments. The callback calls the database operation function with the arguments gathered from the form.

For the nonGUI script, the script figures out the arguments, and then calls the database operation function without the GUI or the callback.

By structuring your form/callback/functionality in this way, you increase your testability, you can run unit tests on the database operation function independently from the form and insert them into regression tests. It also improves maintainability, you can make changes with minimal impact. 

Ted

You have to have graphics if you use a GUI. -nograph will not work. You need the hi- functions.

Consider your architecture. You should actually have 3 levels of code:

1.  create and display the GUI

2. the form callback: This interprets the form and fields and calls the database operation function.

3. The database operation function. It is independent from the GUI and knows nothing about it. It is driven by the values of the arguments to the function. When executed as part of the form, the form callback reads the form fields, generates the database operation argument values and calls the function. When called from a script, the script figures out the argument values and then calls the function, no form involved.

It is not hard to refactor your code in this way. You already create the form. From your database operation function, separate the form analysis into a callback and the execution into its own function. Probably about 10 lines of code. The database operation function should not reference the form at all, everything should be passed through the arguments. The callback calls the database operation function with the arguments gathered from the form.

For the nonGUI script, the script figures out the arguments, and then calls the database operation function without the GUI or the callback.

By structuring your form/callback/functionality in this way, you increase your testability, you can run unit tests on the database operation function independently from the form and insert them into regression tests. It also improves maintainability, you can make changes with minimal impact. 

Ted