Ω cgLauncher is a small useful utility that allows you to make configurations for your projects (software versions, environments, etc)
For now it only supports Houdini, but it can be extended with plugins to be able to launch any application
"Project" is just a simple folder with your stuff: scenes,scripts, models, etc
you can select any folder to be a project, as well as you may right click on a folder and save it to project list for much quicker access
Project is a list of configurations, where a configuration is a set of parameters how to launch the software. for example you can have "animation" preset that uses one build and launches houdinicore.exe with animation plugins loaded with environment, then you can have "fx" and "lighting" presets, which can use their own build, binary and environment variables. (don't forget to save configuration changes to project with "save" button)
Environment variables can be set for each configuration.
The idea was not to force user into some special config workflow, but to be able to adapt to anyone's workflow, so the most general lowlevel settings are exposed, like environment variables.
So, for example, if you have a modular workflow for houdini, you can specify modules required for your project as a list in HOUDINI_PATH:
The launcher is extendable, a launcher plugin for any software can be written or adapted from already excisting python+pyside written launcher
There's a lot to be done with it so far, like providing custom arguments list to start the application with, and standardizing some classes to be reused for other plugins
But maybe someone will find it useful for structuring home projects.
You can find it here:
https://github.com/pedohorse/cglauncher
"Project" is just a simple folder with your stuff: scenes,scripts, models, etc
Project is a list of configurations, where a configuration is a set of parameters how to launch the software. for example you can have "animation" preset that uses one build and launches houdinicore.exe with animation plugins loaded with environment, then you can have "fx" and "lighting" presets, which can use their own build, binary and environment variables. (don't forget to save configuration changes to project with "save" button)
The idea was not to force user into some special config workflow, but to be able to adapt to anyone's workflow, so the most general lowlevel settings are exposed, like environment variables.
So, for example, if you have a modular workflow for houdini, you can specify modules required for your project as a list in HOUDINI_PATH:
HOUDINI_PATH = /path/to/module1;/path/to/module2;/path/to/module3Or if you are just using different HSITE for different projects - you can specify it there as well
HSITE = /path/to/hsiteEnvironment variable values also accept special tokens that are expanded when application launches. For now there's only one token [PWD] that expands to current project directory
The launcher is extendable, a launcher plugin for any software can be written or adapted from already excisting python+pyside written launcher
There's a lot to be done with it so far, like providing custom arguments list to start the application with, and standardizing some classes to be reused for other plugins
But maybe someone will find it useful for structuring home projects.
You can find it here:
https://github.com/pedohorse/cglauncher