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

KSP (Kontakt Script Processor)

by nojanath ST3

Fork of Nils Liberg's SublimeKSP plugin. See README for details.

Details

Installs

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

Readme

Source
raw.​githubusercontent.​com

SublimeKSP

A Sublime Text ¾ plugin for working with and compiling KSP (Kontakt Script Processor) code.

Changes

This fork is based on Nils Liberg's official SublimeKSP plugin, v1.11, and supports all Kontakt versions. However, there are a number of additions and changes:

  • Available in Package Control, which supports automatic updates
  • Updates to the syntax highlighting
  • Support for Creator Tools GUI Designer
  • Numerous additions to the preprocessor, allowing for UI arrays, new macro types and much more
  • See the Added Features section of the Wiki for more information

Installation

  • Install Package Control
  • After installing Package Control and restarting Sublime Text:
    • Open the Command Palette from the Tools menu, or by pressing CmdShiftP (macOS) or CtrlShiftP (Windows)
    • Type “Install Package”
    • Type “KSP” and select “KSP (Kontakt Script Processor)”
    • Press Enter to install
    • Restart Sublime Text

Manual Installation

To use features of SublimeKSP before official package releases:

  • If you already had SublimeKSP installed via Package Control, uninstall it before continuing further!
  • Locate Sublime Text's Packagesfolder by selecting Preferences > Browse Packages from the main menu
  • Clone SublimeKSP repository into this folder via Git (git clone https://github.com/nojanath/SublimeKSP.git "KSP (Kontakt Script Processor")
  • After pulling the latest changes (git pull), reload Sublime Text
  • If you wish to pull in latest changes without restarting Sublime Text, we recommend installing Automatic​Package​Reloader

Running From Command Line

SublimeKSP compiler can also be ran from command line, by simply executing ksp_compiler.py with the appropriate source (and optionally output) file path(s), along with optional compiler switches. For this, you need to use the manual installation of SublimeKSP, in order to have direct access to ksp_compiler.py file. To execute a compilation of a file, it is as simple as typing:

> python ksp_compiler.py "<source-file-path>"

However, various compiler options from SublimeKSP's Tools menu are also available. All of them are set to false if not used, and by including them in the command line, they are set to true:

ksp_compiler.py [-h] [-c] [-v] [-e] [-o] [-t] [-d] source_file [output_file]

positional arguments:
  source_file
  output_file

optional arguments:
  -h, --help                   show this help message and exit
  -f, --force                  force all specified compiler options, overriding any compile_with pragma directives from the script
  -c, --compact                remove indents and empty lines in compiled code
  -v, --compact_variables      shorten and obfuscate variable names in compiled code
  -d, --combine_callbacks      combines duplicate callbacks - but not functions or macros
  -e, --extra_syntax_checks    additional syntax checks during compilation
  -o, --optimize               optimize the compiled code
  -t, --add_compile_date       adds the date and time comment atop the compiled code
  -x, --sanitize_exit_command  adds a dummy no-op command before every exit function call


> python ksp_compiler.py --force -c -e -o "<source-file-path>" "<target-file-path>"

Updates

  • Updates to the plugin will be automatically installed via Package Control.
  • Pull requests are welcome for bugfixes/updates/changes. If you aren't familiar with pull requests, just open an issue here.

Documentation

See the Wiki on GitHub.