Class Compiler

Koder has a built in class compiler. Any files in your 'src' directory that Koder thinks are classes can be compiled and loaded into ScriptMaster automatically. Koder considers any files that end in ".java" or "class.groovy" to be classes.

The reason for this is to reduce the number of compiles and project shifting you have to do when you want to use classes to encapsulate logic so you can use ti in many script master functions.

The normal way of doing this is to build your classes and compile them into Jars then load them into ScriptMaster and write some simple wrapper scripts to that use your class. This certainly works but what happens when you have a bug in your class? You have to go back to the project that contains the code for the class, fix the bug, compile the jar, load it into ScriptMaster, test to make sure it works there. Screw that! Way too many steps.

With Koder, you write everything for your ScriptMaster Project in a single project. You can write your classes right in the 'src' directory along with groovy scripts that describe the FileMaker functions. There is no need to write, debug and compile your classes in a separate project.

When you run the class compiler, by clicking the Compile Classes button, Koder searches your src directory for Java Classes and for any Groovy files that end in "class.groovy", and compile them into a Jar file which is automatically loaded into ScriptMaster.