Btw Is there any real advantages with generating the script with stringmanipulation compared to using the python nuke-w? It's just seems like a hassle to me
On Wed, Dec 2, 2015, 21:01 Johan Forsgren <[email protected]> wrote: > Basically it's a template, with a readnode(a custom thing that processes > data, which the buildscript also initializes) on one end and a write-node > on the other, and literally nothing else inbetween. Well, theres 4 dots and > a backdrop node thrown in there as well. But aside from that nothing. > Everything else is added by the buildscript. > > On Wed, Dec 2, 2015, 20:55 Ron Ganbar <[email protected]> wrote: > >> Sorry Den, I misunderstood your request. But generally I was saying that >> since a Nuke script is just text, you can easily manipulate it in that >> level. >> >> Johan, what are skeleton files? >> >> >> >> Ron Ganbar >> email: [email protected] >> tel: +44 (0)7968 007 309 [UK] >> +972 (0)54 255 9765 [Israel] >> url: http://ronganbar.wordpress.com/ >> >> On Wed, Dec 2, 2015 at 9:52 PM, Johan Forsgren <[email protected]> >> wrote: >> >>> Over here we open up nuke skeleton files and populate them with whatever >>> is defined in our client orders using the nuke command line. It works great >>> for us, we generate custom luts, crops images and shuffle out whatever >>> elements the pythonscript thinks might be handy. Work great for us, but I'm >>> guessing you want more low-level functionality? >>> On Dec 2, 2015 7:21 PM, "Den Serras" <[email protected]> wrote: >>> >>>> Thanks Justin! I tried importing hiero from Nuke 9 command line, and >>>> got an error "No module named _fnpython", and I can't get Studio to launch >>>> as command line. Have you been able to do that? >>>> >>>> Thanks Ron. I am not sure what you mean, however. I'm trying to find a >>>> way to have Nuke server-side generate the script, so that all the proper >>>> configs are applied without me having to pre-generate a template whenever >>>> anyone updates code that would affect new files. >>>> >>>> Den >>>> >>>> On Wed, Dec 2, 2015 at 1:59 AM, Ron Ganbar <[email protected]> wrote: >>>> >>>>> You can create a file on the filesystem and open it all through Python. >>>>> >>>>> >>>>> >>>>> Ron Ganbar >>>>> email: [email protected] >>>>> tel: +44 (0)7968 007 309 [UK] >>>>> +972 (0)54 255 9765 [Israel] >>>>> url: http://ronganbar.wordpress.com/ >>>>> >>>>> On Wed, Dec 2, 2015 at 11:46 AM, Justin GD <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Den, >>>>>> >>>>>> I guess you could create a nuke script as same as a Nuke Studio nuke >>>>>> script exporter.. >>>>>> >>>>>> >>>>>> [...]pythonextensions\site-packages\hiero\core\nuke\Script.py >>>>>> >>>>>> You have the ScriptWriter class with a method called *writeToDisk *that >>>>>> uses* nuke.saveToScript( scriptFilename, fileContents )* >>>>>> >>>>>> Maybe that could help ? >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Justin >>>>>> >>>>>> >>>>>> 2015-12-01 16:38 GMT+00:00 Den Serras <[email protected]>: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Due to our pipeline, we have to create the Nuke file for the artist. >>>>>>> We currently create a template which is duplicated and moved into the >>>>>>> correct spot, but I'd prefer to do it more dynamically so every time I >>>>>>> push >>>>>>> a change to the setup I don't have to generate a new file. I tried >>>>>>> launching the CLI and then saving the file, but none of my init scripts >>>>>>> that actually modify the file seem to be running in the CLI. Don't know >>>>>>> if >>>>>>> I'm doing something wrong or this method won't work. Anyone have a >>>>>>> dynamic >>>>>>> way to create a script, or are those who prebuild scripts always using >>>>>>> templates? >>>>>>> >>>>>>> Thanks! >>>>>>> Den >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Nuke-python mailing list >>>>>>> [email protected], >>>>>>> http://forums.thefoundry.co.uk/ >>>>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Nuke-python mailing list >>>>>> [email protected], http://forums.thefoundry.co.uk/ >>>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Nuke-python mailing list >>>>> [email protected], http://forums.thefoundry.co.uk/ >>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Nuke-python mailing list >>>> [email protected], http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>> >>>> >>> _______________________________________________ >>> Nuke-python mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >>> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
