(no subject)
Jul. 23rd, 2017 01:14 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jcreedFutzed around with learning the blender python API for most of the day.
I notice a tension between having an api that seems to fit the user interface in a nice way --- like, to be good at cleanly automating UI actions that you would be doing anyway as a person --- versus having an api that makes sense for programming, where you get good, uniform, and ideally functional access to the data structures that you care about.
Blender's seems very heavily biased towards the former. I found myself having to do weird imperative sequences of things as if I was doing a sequence of UI operations; select this, select that, make this active, perform this argumentless operation on whatever happens to be selected, etc. Not really a fan.
but eventually succeeded at making a nice minimal animation that has existed in my head for years and years as a kind of... spatio-cognitive tic. Not sure how else to describe it.
I notice a tension between having an api that seems to fit the user interface in a nice way --- like, to be good at cleanly automating UI actions that you would be doing anyway as a person --- versus having an api that makes sense for programming, where you get good, uniform, and ideally functional access to the data structures that you care about.
Blender's seems very heavily biased towards the former. I found myself having to do weird imperative sequences of things as if I was doing a sequence of UI operations; select this, select that, make this active, perform this argumentless operation on whatever happens to be selected, etc. Not really a fan.
but eventually succeeded at making a nice minimal animation that has existed in my head for years and years as a kind of... spatio-cognitive tic. Not sure how else to describe it.
