How about allowing *.cslist's to contain other *.cslist's? Think of handy collections of utility code.
How about referencing a script file (or *.cslist) that is located in another VAR package? Currently script files can only be located relative to the *.cslist they are listed in.
Example:
You would like to write a custom animation driver for my Life plugin. You would need to reference the core plugin and maybe some utility code, potentially derive from some base class (see request regarding abstract classes) put provide the code in your own VAR as it doesn't make sense to release a modified version of the Life plugin.
How about referencing a script file (or *.cslist) that is located in another VAR package? Currently script files can only be located relative to the *.cslist they are listed in.
Example:
You would like to write a custom animation driver for my Life plugin. You would need to reference the core plugin and maybe some utility code, potentially derive from some base class (see request regarding abstract classes) put provide the code in your own VAR as it doesn't make sense to release a modified version of the Life plugin.