I actually did a port of Tickly to python just for fun - it’s got no tests and a subtle bug, but hey - it’s a start. I should get onto nuke-python one day… https://gist.github.com/julik/7656373
On 29 Jan 2014, at 23:54, Nathan Rusch <[email protected]> wrote: > A similar question came up on nuke-python, so apologies if you already saw > that thread. > > I think rebuilding your own DAG by parsing the script as Nuke does is pretty > much the only option for accurate results, and isn't that hard in and of > itself. The real problem is that unless you have a way of front-loading the > default number of inputs each node class has, you can't really "reconnect" > things accurately. You could certainly cache the input information out to > some kind of a file though; you would just have to make sure you kept it up > to date if/when new plugins were added. -- Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX Amsterdam | The Netherlands | tel. +31 20 330 8250 cel. +31 61 145 06 36 | http://hecticelectric.nl
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
