Pipeline test

In December I used my spare time to learn Pyside2 in order to be able to do GUI with Python3. ‘What better way to learn than actually coding?’ I thought, so I created a little tool to manage the assets of my personal projects.

The software allows taking control of the assets you create and have in your project. It creates a general database for all the assets, where it stores the asset name, type, and last modified date. It also creates an additional database for each asset to store more specific information about the ‘asset files’ (the software files used to develop and create the asset). In addition, to be able to store notes about each asset file, it also allows the user to open the asset file by double-clicking in the table.

The naming convention and folder structure that I have chosen is the one that I use in my personal projects. It’s far from being perfect but I think that it’s quite clear and easy to follow.

As for the interaction with the different software, right now the user has to version up the files on its own following the naming convention and the version number. After that, clicking ‘Update’ in the Asset Browser will allow the user to add those asset files to the asset’s database with some notes (if wanted).

Here you have a (boring) video where I show how it works:

You can find the code at my Github website.

I would appreciate any kind of constructive feedback, both code or pipeline related ones.