| 1 |
<html> |
| 2 |
<head> |
| 3 |
<meta name="author" content="Christian Schoenebeck"> |
| 4 |
<title>Latest development about NKSP instrument script editor</title> |
| 5 |
<navpath>Instrument Script Editor (2016-05-04)</navpath> |
| 6 |
<meta name="description" content="Latest development about NKSP instrument script editor."> |
| 7 |
<link rel="stylesheet" href="http://doc.linuxsampler.org/css/preview.css"> |
| 8 |
<script type="text/javascript" src="http://doc.linuxsampler.org/js/preview.js"></script> |
| 9 |
</head> |
| 10 |
<body> |
| 11 |
<h1>NKSP Script Editor</h1> |
| 12 |
<p> |
| 13 |
There is some progress regarding the <a href="nksp.html">NKSP instrument script</a> |
| 14 |
editor. With LinuxSampler 2.0.0.svn8 and gigedit 1.0.0.svn13 working on |
| 15 |
instrument scripts for sounds became much more convenient. Gigedit's integrated |
| 16 |
instrument script editor starts to become an |
| 17 |
<i title="<b>Integrated Development Environment</b>: A software application that provides comprehensive facilities for software development."> |
| 18 |
IDE |
| 19 |
</i> |
| 20 |
for instrument script development. |
| 21 |
</p> |
| 22 |
|
| 23 |
<img src="script_editor_gigedit_1_0_0_svn13.png" caption="NKSP Instrument Script Editor of Gigedit"> |
| 24 |
|
| 25 |
<h3>Syntax Highlighting</h3> |
| 26 |
<p> |
| 27 |
Gigedit's integrated instrument script editor supports now tight coupling |
| 28 |
directly with LinuxSampler's actual instrument script parser backend. |
| 29 |
That provides several improvements for the script editor. For example |
| 30 |
colored syntax highlighting of scripts is now displayed appropriately and |
| 31 |
simply looks much better now. Previously there was some small hard coded |
| 32 |
script parser code on Gigedit's side which however was buggy and simply |
| 33 |
did no great job. |
| 34 |
</p> |
| 35 |
|
| 36 |
<h3>Error Reporting</h3> |
| 37 |
<p> |
| 38 |
Another major improvement possible due to the direct coupling with LinuxSampler's |
| 39 |
script backend, is support for showing all issues related to the script (errors |
| 40 |
and warnings) directly within the script editor in real-time while you are |
| 41 |
typing. The actual erroneous locations of the script are automatically |
| 42 |
highlighted with red background color, locations of the script with |
| 43 |
warnings are automatically highlighted with yellow background color, and |
| 44 |
when you move your mouse over the respective code location, the precise |
| 45 |
error/warning message is displayed as a tooltip. And last but not least |
| 46 |
there is a summary of issues displayed in the status bar of the script |
| 47 |
editor. Since LinuxSampler's instrument script backend is actually doing |
| 48 |
all the work for the script editor, all aspects of the language, all |
| 49 |
details about built-in functions and variables, and all potential issues |
| 50 |
with their precise cause and messages are automatically covered by the |
| 51 |
script editor. |
| 52 |
That way you immediately know whether or whether not your script |
| 53 |
is OK with every character you are typing, and without requiring to |
| 54 |
actually load the script with an instrument into the sampler. |
| 55 |
</p> |
| 56 |
|
| 57 |
<h3>Live Development</h3> |
| 58 |
<p> |
| 59 |
Previously, when you made any changes to scripts, you had to manually |
| 60 |
tell the sampler to reload the respective instrument to actually being |
| 61 |
able to try out your changes and play it with some sound. This is not |
| 62 |
needed anymore. You can now simply open the respective script of the |
| 63 |
sound you are currently playing with, change the script with Gigedit's |
| 64 |
integrated script editor and click either on the "Apply" button or use |
| 65 |
the Ctrl-S keyboard shortcut. The sampler will immediately reload the |
| 66 |
script and the new version of your script will immediately become audible |
| 67 |
with the sampler. That makes working on scripts much faster and convenient. |
| 68 |
</p> |
| 69 |
|
| 70 |
</body> |
| 71 |
</html> |
Parent Directory
| 
Revision Log