1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html >
<head><title>The programming window</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="generator" content="TeX4ht (http://www.tug.org/tex4ht/)">
<meta name="originator" content="TeX4ht (http://www.tug.org/tex4ht/)">
<!-- 3,html -->
<meta name="src" content="nipguide.tex">
<link rel="stylesheet" type="text/css" href="nipguide.css">
</head><body
>
<!--l. 469--><div class="crosslinks"><p class="noindent">[<a
href="nipguidese13.html" >next</a>] [<a
href="nipguidese11.html" >prev</a>] [<a
href="nipguidese11.html#tailnipguidese11.html" >prev-tail</a>] [<a
href="#tailnipguidese12.html">tail</a>] [<a
href="nipguidech4.html#nipguidese12.html" >up</a>] </p></div>
<h3 class="sectionHead"><span class="titlemark">4.4 </span> <a
id="x20-380004.4"></a>The programming window</h3>
<!--l. 470--><p class="noindent" ><a name="nip_label_sec:progwin"></a>
<!--l. 472--><p class="indent" > To pop up the programming window, click on <span
class="phvr7t-x-x-80">Toolkits </span>/
<span
class="phvr7t-x-x-80">Edit Toolkits </span>in <span
class="phvr7t-x-x-80">nip2</span>’s main image processing window. The
window shown in Figure <a
href="nipguidese3.html#x9-800111">2.11<!--tex4ht:ref: fg:Fred --></a> should appear.
<!--l. 476--><p class="indent" > Each of the things down the left of the program window
is a toolkit. Each toolkit is a text file containing a set of
definitions in <span
class="phvr7t-x-x-80">nip2</span>’s programming language. See Chapter <a
href="nipguidech6.html#x31-570006">6<!--tex4ht:ref: sec:program --></a>
for details on the language.
<!--l. 481--><p class="indent" > If you open a toolkit, <span
class="phvr7t-x-x-80">nip2 </span>shows all of the definitions in
that file. If you click on one of these <span
class="phvr7t-x-x-80">nip2 </span>shows the
source for that definition in the main part of the program
window. After editing a definition, click on <span
class="phvr7t-x-x-80">File </span>/ <span
class="phvr7t-x-x-80">Process </span>to
make <span
class="phvr7t-x-x-80">nip2 </span>read what you typed, compile it, and update
itself.
<!--l. 487--><p class="indent" > Click on <span
class="phvr7t-x-x-80">File </span>/ <span
class="phvr7t-x-x-80">New </span>/ <span
class="phvr7t-x-x-80">Tool </span>to add a new definition to a
toolkit, click on <span
class="phvr7t-x-x-80">File </span>/ <span
class="phvr7t-x-x-80">New </span>/ <span
class="phvr7t-x-x-80">Toolkit </span>to make a completely new
toolkit. You can also right-click on tools and toolkits to get a
context menu, and you can left-drag tools to move them
around within a toolkit or between toolkits.
<!--l. 492--><p class="indent" > Some toolkits are loaded from files when <span
class="phvr7t-x-x-80">nip2 </span>starts up,
others are built from the VIPS operation database (for
example, <span
class="phvr7t-x-x-80">_arithmetic</span>), and one (called <span
class="phvr7t-x-x-80">_builtin</span>) contains the
functions that are built into <span
class="phvr7t-x-x-80">nip2</span>. If you select a tool and then
click on <span
class="phvr7t-x-x-80">Help </span>/ <span
class="phvr7t-x-x-80">Help on Tool</span>, <span
class="phvr7t-x-x-80">nip2 </span>will try to display the
relevant section from the VIPS manual in your web
browser. Currently, this works only for things in the VIPS
operation database: try <span
class="phvr7t-x-x-80">_arithmetic </span>/ <span
class="phvr7t-x-x-80">im</span><span
class="phvr7t-x-x-80">_add</span>, for example.
There’s a section in the <span
class="phvr7t-x-x-80">Preferences </span>workspace to control
which web browser <span
class="phvr7t-x-x-80">nip2 </span>uses and how it asks for a
page.
<!--l. 502--><p class="indent" > Toolkits and tools whose names begin with an underscore
character are not displayed in the main <span
class="phvr7t-x-x-80">Toolkits </span>menu. The
idea is that they represent little utility functions, rather
than stuff a user might be interested in. See <span
class="cmsy-10"></span><a
href="nipguidese33.html#x44-800006.12.1">6.12.1<!--tex4ht:ref: sec:tools --></a>
for more information on how tools and toolkits are
displayed.
<!--l. 507--><p class="indent" > You can have several programming windows open at
the same time (often useful, if confusing). The <span
class="phvr7t-x-x-80">Edit</span>
menu lets you search for patterns across all definitions.
The <span
class="phvr7t-x-x-80">Jump To Definition </span>item jumps to the definition of a symbol.
<!--l. 512--><p class="indent" > <a name="nip_label_sec:trace"></a> The <span
class="phvr7t-x-x-80">Debug </span>menu has items which open a trace window
(use this to track the actions taken by <span
class="phvr7t-x-x-80">nip2</span>’s reduction
engine) and which report on unresolved symbols and list all
current errors.
<!--l. 517--><div class="crosslinks"><p class="noindent">[<a
href="nipguidese13.html" >next</a>] [<a
href="nipguidese11.html" >prev</a>] [<a
href="nipguidese11.html#tailnipguidese11.html" >prev-tail</a>] [<a
href="nipguidese12.html" >front</a>] [<a
href="nipguidech4.html#nipguidese12.html" >up</a>] </p></div>
<!--l. 517--><p class="indent" > <a
id="tailnipguidese12.html"></a>
</body></html>
|
