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 16
  • Win 11
  • Mac 4
  • Linux 1
May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2
Windows 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 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 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

Readme

Source
raw.​githubusercontent.​com

1. Nuke Tools ST README

Codacy Badge Codacy Badge DeepSource

PackageControl

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

A Sublime Text package to send Python or BlinkScript code inside Nuke.

1.1. NukeServerSocket

Download the companion plugin:

1.2. Features

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

1.3. Installation

The preferred method of installation is via the Package Control.

  • Package Link
  • Inside Sublime, invoke the Command Palette -> Install Package -> NukeToolsST.

1.4. Usage

Demo

Once NukeServerSocket is up and running, you can execute your python/blink file with the new command.

1.5. BlinkScript

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

The extension will create a blinkscript node named after the currently active file. If the node already exists, it will only modify the code and recompile it.

The accepted file extension code are .cpp or .blink.

1.6. Connection

No settings are necessary if the connection is on the same computer. The package will automatically connect to the localhost and use the port configuration found inside $HOME/.nuke/NukeServerSocket.ini. The configuration value is updated every time it's changed inside the plugin.

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

Keep in mind that once the addresses are specified manually, they will always take over the defaults one.

Note: Attempting to establish a connection to a manually specified host which is down (i.e., not reachable) will result in a temporary freeze of the Sublime UI for 10 seconds..

1.7. Package Settings

  • nss_port:integer

Set a different value for the connection. The port should match the one from NukeServerSocket.

  • nss_hostname:string

Same as nss_port. The host could be the local host or the local IP.

  • nss_disable_context_menu:bool

Disable Sublime context menu entry if not needed. Default's to false.

Example

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

1.8. 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 extensions:

  • .py
  • .cpp
  • .blink

1.9. Key Bindings

By default, the package does not include any key bindings. You can add them by following the Sublime Text Key Bindings guide.

Example

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

1.10. 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 show only on specific file extensions.

[0.1.0] 10-21-2021

  • Initial release.

1.11. Overview

example