[Sidefx-houdini-list] HDA script management
parker.jon at gmail.com
Tue Feb 23 19:15:13 EST 2016
Peter already mentioned "hotl" which I was going to mention. With
some binary exceptions, this will uncompress everything within a .otl/hda
file to a plaintext file/folder structure that you can then edit / use
version control to work with. You would want to create some context
menu scripts for Houdini to automate this, I imagine.
Honestly, if SESI were to just add a menu option "Save as New
Version/Copy...", that you could use after making an asset editable,
in addition to the "Save Node Type" option, this would go a long way
to convenient version management. There must be a technical reason
why this hasn't happened yet, I guess, as I know I'm not the only one
who has wished for it.
On Tue, Feb 23, 2016 at 10:40 AM, Andy Nicholas <andy at andynicholas.com> wrote:
> Hey folks,
> I've been getting further into HDA authoring and have been writing a lot of
> HDA embedded python scripts. One thing I'm missing is not writing Python in
> my favourite IDE (PyCharm) with all the benefits that brings, like reuse of
> code, being able to do Diffs, and being able to manage code versioning
> through Git. Ideally I'd like to have all my HDA Python code stored
> So I was just wondering if anyone had got a workflow going with versioning
> HDAs and externally imported python modules? Seems like it could be a can of
> worms having to make sure that the version of the asset matches the correct
> version of imported python module. Any HDAs used on a job would have to have
> a corresponding python module available in the path and it's hard to see how
> conflicts could be managed easily (especially since multiple versions of the
> same HDA could be used in the same Hip file).
> Anyone have any experience trying to manage this in their set up?
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list