Python expressions are already implemented in Nuke 6.2. (for all knobs that
support expressions, which excludes string and file knobs)
However, I think you may have some terms confused (apologies if I'm wrong).
When you say you can use expressions like "this.knob, parent.knob,
root.knob" elsewhere, those are NOT Python. They are a form of TCL that's
handled by Nuke's expression parser directly (instead of the TCL
interpreter), as Nathan pointed out before.
In my opinion, that's still the fastest & easiest way to use expressions in
Nuke (where they are available), and I certainly wouldn't want to replace
something like "Transform1.translate.x" with a Python expression like
"nuke.toNode('Transform1').knob('translate').value(0)", although you can
certainly do so since Nuke 6.2.
I agree that it would be nice to be able to use your language of choice on
any given knob, but for me, speed and flexibility outweigh consistency in
this case.
On Mon, May 2, 2011 at 10:32 AM, Brandon Harris
<[email protected]>wrote:
> To keep everything consistent. Keeps me from having to keep 2 languages in
> my head for this application. Maybe not as valid an excuse as some would
> want it, but consistency is a big thing for me. However, if the only means
> of accomplishing what I want is with TCL then my hand will be forced.
>
> Is there a feature request for python expressions in Nuke?
>
> Brandon L. Harris
>
>
>
> On 05/02/2011 12:28 PM, Nathan Rusch wrote:
>
>> Why are you so intent on avoiding TCL?
>>
>
> _______________________________________________
> Nuke-python mailing list
> [email protected]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
_______________________________________________
Nuke-python mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
