Another tip, good for learning nodes; in the preferences setting the side arrows length to around '24' reveals the names of the input. That's how I learnt of the 'hidden' extra particle pipe in the ParticleEmitter!
Preferences/NodeGraph/unconnected left/right input arrow length On 6 October 2012 00:19, Neil Scholes <[email protected]> wrote: > Hi > I'm in favor of any technique which helps clarify a network > > Personally I just can't work in nuke unless I take care in layout and the > logic of the flow - otherwise I'm completely confused when coming back to a > script > > The option of color coding pipes etc sounds great - whatever helps > whatever works > > Neil Scholes > Sent from my HTC > > ----- Reply message ----- > From: "Howard Jones" <[email protected]> > To: "Nuke user discussion" <[email protected]> > Subject: [Nuke-users] Nuke Script Layout, was new comp stack node survey > Date: Fri, Oct 5, 2012 8:52 AM > > > Ha. > I introduced red for up purely because it was impossible to read scripts > from a comper friend without it. > > I also like my code coloured, though I only gleam a bit of extra info from > it. Oddly enough my code is just as crap either way ;) > > Howard > > On 5 Oct 2012, at 03:18, Nathan Rusch <[email protected]> wrote: > > Personally I’m heavily against pipe coloring in my own environment. Even > when untangling someone else’s mess, I find it easier to just use Nuke’s > highlighting of the parent hierarchy of the current selection than having > to visually process a mass of neon spaghetti. I think some of the same > logic from this article ( > http://www.linusakesson.net/programming/syntaxhighlighting/index.php) is > directly applicable to overly colorful trees, though I don’t necessarily > agree with all the points he makes. > > -Nathan > > > *From:* Marten Blumen <[email protected]> > *Sent:* Thursday, October 04, 2012 1:52 PM > *To:* Nuke user discussion <[email protected]> > *Subject:* Re: [Nuke-users] Nuke Script Layout, was new comp stack node > survey > > Anyone have thoughts on coloured lines in the Node Graph Just like > coloured Nodes, would colouring lines help reading the flow. i.e like the > London Tube map. I'm experimenting with turning off Node Colors/AutoColor > and manual colouring important nodes. Would it help to be able to do that > to lines? > > Famous Tube map redesign; maybe some ideas in this > http://www.design-technology.info/alevelsubsite/page5.htm > > On 4 October 2012 20:39, Howard Jones <[email protected]> wrote: > >> Might pinch that, however the label I use may be main mattes, rather >> than the last node name. >> >> And of course they can have multi channels in them. >> >> I just found when you have pipes running several 'pages' worth, it saves >> all that scrolling up and down. But requires a bit of copy and paste. >> Obviously there are tools to modify multiple nodes at once on nukepedia. >> >> Maybe the python could be modified to take one master dot at the top and >> copy its label? Hmmmm. >> >> Howard >> >> On 4 Oct 2012, at 03:22, Frank Rueter <[email protected]> wrote: >> >> bugger tcl. >> >> def getParentNode(node): >> >> parentNode = node.input(0) >> >> if parentNode.Class() == 'Dot': >> >> return getParentNode(parentNode) >> >> else: >> >> return parentNode.name() >> >> >> nuke.knobDefault('Dot.label', "[python >> getParentNode(nuke.toNode('Dot1'))]") >> >> >> >> >> >> >> On 10/4/12 1:46 PM, chris wrote: >> >> On 10/3/12 at 12:57 AM, (Howard Jones) wrote: >> >> my favorite - label the dots. And have one just before inputs so you can >> easily see where each input came from. >> >> >> i like that one a lot! just added this to my menu..py >> >> nuke.knobDefault('Dot.label', ' [value input0.name]') >> >> might be worth thinking about how to get the name of the next non-dot >> node when traveling up the tree (in case one uses several dots in a row to >> direct the flow), but no idea how to do that through TCL. >> >> ++ chris >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > ------------------------------ > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
<<attachment: particle node.png>>
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
