ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Nuke​Tools​ST

by virgilsisoe ALL

A Sublime Text package that allows to send python or blinkscript code to be executed inside Nuke.

Details

Installs

  • Total 3
  • Win 2
  • Mac 0
  • Linux 1
Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Nuke Tools ST README

Codacy Badge Codacy Badge DeepSource

This is a companion extension for: NukeServerSocket and is based on NukeTools.

A Sublime Text package that allows to send python or blinkscript code to be executed inside Nuke.

Features

  • Execute code inside Nuke from a machine in your local network.
    • Get output of Nuke code execution inside Sublime console.
    • When used locally (same machine) no configuration is required, just running the server inside Nuke.
    • Specify a custom address when connection is from/to another computer.
    • Multiple connections can be made to the same Nuke instance.
    • BlinkScript support.

Installation

The preferred method of installation is via the Package Control.

BlinkScript

NukeServerSocket >= 0.1.0 is needed in order for this to work.

You can execute code from the text editor directly inside a Nuke BlinkScript node.

The extension will take the name of the current active file and create a blinkscript node inside Nuke with the name as the current filename. If the node already exists then will only modified its source code. Once done will recompile the source kernel.

The accepted file extension are .cpp or .blink.

Connection

No settings are necessary if connection is expected to be on the same computer. NukeToolsST will automatically connect to the localhost and will use the port configuration found inside $HOME/.nuke/NukeServerSocket.ini. The configuration value is updated automatically each time its changed inside the plugin.

However if connection is between different computers, port and hostname must be changed manually via the package settings.

Keep in mind that, once the addresses are specified manually, will always take over the defaults one. Its best to delete them if you only connect between the same computer.

Note

Attempting to connect to a manually specified host that is down (not reachable) will result in a temporary freeze of the Sublime UI for 10 seconds.

Package Settings

nss_port:integer

A different port for the connection. Port should match the one from NukeServerSocket.

nss_hostname:string

Same as nss_port. Host could be the localhost or the local ip.

nss_disable_context_menu:bool

Disable Sublime context menu entry if not needed (clean up). Defaults to false.

Example

{
  "nss_port": 54321,
  "nss_hostname": "192.168.1.60",
  "nss_disable_context_menu": true
}

Commands

The following command will be available: run_nuke_tools.

A new entry “Run Code inside Nuke” will be added to the context menu (right click) when the active file ends with one of the following extension:

  • .py
  • .cpp
  • .blink

Key Bindings

The package does not include any key bindings by default but you can add them by following the Sublime Text Key Bindings guide.

Example

[
    {
        "keys" : ["ctrl+alt+n"],
        "command" : "run_nuke_tools"
    }
]

NukeServerSocket

Download the companion plugin: Git, Nukepedia.

Changelog

[0.2.0] 11-04-2021

  • Removed most of the commands, leaving only the context menu one.
  • Removed default key bindings.
  • New configuration to hide context menu.
  • Context menu options shows only on specific file extensions.

[0.1.0] 10-21-2021

  • Initial release.

Overview

example