Tools are probably one of my favorite things to code. Tools and pipeline scripts often do not get the attention they fully deserve or worst yet they get skipped over completely because the task seems so small to waste code on. Most commonly what happens is that tools start to get designed and built as soon as a project starts.
The problem there is that tools are meant to simplify and improve workflow but there is no way you can actually know your problems before you are fully sure of what you are making and what the actual problems might be. Sure you can always give it your best guess and try and have the tools solve problems you think you might run into or to build the workflow that you assume might be best.
The reality is that it is better to grow your tools in the beginning by keeping them small and simple. This way they can grow and change as your project grows and changes and adapt to actual production workflows. This keeps your tools light and super affective at their tasks. Tools should also try and leverage any software you have in your workflow. As an example I use Inkscape for all of my art assets.
Inkscape has a really nice command line interface that I use to automatically export my assets to png images, create room files, objects and anything else I might need. This allows me to use Inkscape not only as my art program but also use it for layout. The added bonus is that it removes me, or rather the human element from needing to export all of my assets to the proper files and update their positions in my room file. Plus I can batch process as many files as I need so I can easily make sure that all of my content is up to date. Almost all software has some kind of command line interface and if you are putting together any pipelines or tool scripts you should always start by taking a look at the software you are using and look into their command lines. You might just find something that you didn't even think about.
The problem there is that tools are meant to simplify and improve workflow but there is no way you can actually know your problems before you are fully sure of what you are making and what the actual problems might be. Sure you can always give it your best guess and try and have the tools solve problems you think you might run into or to build the workflow that you assume might be best.
The reality is that it is better to grow your tools in the beginning by keeping them small and simple. This way they can grow and change as your project grows and changes and adapt to actual production workflows. This keeps your tools light and super affective at their tasks. Tools should also try and leverage any software you have in your workflow. As an example I use Inkscape for all of my art assets.
Inkscape has a really nice command line interface that I use to automatically export my assets to png images, create room files, objects and anything else I might need. This allows me to use Inkscape not only as my art program but also use it for layout. The added bonus is that it removes me, or rather the human element from needing to export all of my assets to the proper files and update their positions in my room file. Plus I can batch process as many files as I need so I can easily make sure that all of my content is up to date. Almost all software has some kind of command line interface and if you are putting together any pipelines or tool scripts you should always start by taking a look at the software you are using and look into their command lines. You might just find something that you didn't even think about.
Comments
Post a Comment