forked from RedhawkSDR/Documentation
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmainli2.html
624 lines (608 loc) · 27 KB
/
mainli2.html
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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html >
<head><title>Glossary</title>
<meta http-equiv="Content-Type" content="text/html; charset="utf-8"">
<meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)">
<meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)">
<!-- html,2,next,javascript,charset="utf-8" -->
<meta name="src" content="main.tex">
<meta name="date" content="2013-03-12 19:46:00">
<link rel="stylesheet" type="text/css" href="main.css">
<script type="text/javascript" src="scripts/shCore.js"></script>
<script type="text/javascript" src="scripts/shBrushCpp.js"></script>
<script type="text/javascript" src="scripts/shBrushJava.js"></script>
<script type="text/javascript" src="scripts/shBrushPython.js"></script>
<script type="text/javascript" src="scripts/shBrushBash.js"></script>
<script type="text/javascript" src="scripts/shBrushXml.js"></script>
<link href="styles/shCore.css" rel="stylesheet" type="text/css" />
<link href="styles/shThemeDefault.css" rel="stylesheet" type="text/css" />
<script type="text/javascript">
SyntaxHighlighter.all()
</script>
</head><body
>
<script>
function f() {
document.getElementById('main_content_wrap').focus();
}
if (window.addEventListener) {
window.addEventListener("load", f, false);
} else if (window.attachEvent) {
window.attachEvent("onload", f);
}
</script>
<div class="header">
<ul class="navbar">
<li><a class="logo-small" href="index.html"><img src="images/RedHawk_Logo_ALT_B_121px.png"/></a></li> <li><a href="index.html">Home</a></li>
<li><a href="gettingstarted/main.html">Getting Started</a></li>
<li><a class="active" href="main.html">Documentation</a></li>
<li><a href="download.html">Download</a></li>
<li><a href="support.html">Support</a></li>
</ul>
<div class="pattern right"></div>
<a id="forkme_banner" href="https://github.com/redhawksdr">View on GitHub</a>
</div>
<!-- Custom MAIN CONTENT -->
<div id="main_content_wrap" tabindex="0" class="outer">
<section id="main_content" class="inner">
<!--l. 1--><div class="crosslinks"><p class="noindent">[<a
href="mainli3.html" >next</a>] [<a
href="mainap3.html" >prev</a>] [<a
href="mainap3.html#tailmainap3.html" >prev-tail</a>] [<a
href="#tailmainli2.html">tail</a>] [<a
href="main.html#mainli2.html" >up</a>] </p></div>
<h2 class="likechapterHead"><a
id="x30-348000C"></a>Glossary</h2>
<dl class="description"><dt class="description">
<a
id="glo:application"></a>
<span
class="cmbx-12">Application</span> </dt><dd
class="description">“Generically, an executable software program which may contain one or more
modules. Within SCA, an application consists of one or more software modules which
implement the Base Application Interfaces and which are identified within a Software
Assembly Descriptor file. When loaded and executed, these modules create one or more
components which comprise the application. ” Source: SCA v2.2.2
</dd><dt class="description">
<a
id="glo:applicationfactory"></a>
<span
class="cmbx-12">Application Factory</span> </dt><dd
class="description">“An instantiation of the <span
class="cmtt-12">ApplicationFactory </span>interface is used to
create an instance of an application. The domain manager creates an application
factory for each Software Assembly Descriptor that is installed. ” Source: SCA v2.2.2
</dd><dt class="description">
<a
id="glo:assemblycontroller"></a>
<span
class="cmbx-12">Assembly Controller</span> </dt><dd
class="description">“The assemblycontroller element of the Software Assembly
Descriptor indicates the component that is the main resource controller for an
application. ” Source: SCA v2.2.2
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:component"></a>
<span
class="cmbx-12">Component</span> </dt><dd
class="description">A processing module that implements the CF::Resource interface that
is deployable by an Application Factory (see SCA v2.2.2 for a description of
CF::Resource).
</dd><dt class="description">
<a
id="glo:Console View"></a>
<span
class="cmbx-12">Console View</span> </dt><dd
class="description">Displays a variety of console types depending on the type of development
and the current set of user settings. The <a
href="#glo:Console View"><span
class="cmbx-12">Console View</span></a> is a part of
Eclipse and the basic use is well documented by the Eclipse documentation:
<a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>. The REDHAWK IDE uses multiple <a
href="#glo:Console View"><span
class="cmbx-12">Console Views</span></a> for
different purposes. There are also third party plug-ins within REDHAWK that have
their own <a
href="#glo:Console View"><span
class="cmbx-12">Console Views</span></a>. For further details see <a
href="mainch19.html#x21-27100019.4.4">Section 19.4.4</a>.
</dd><dt class="description">
<a
id="glo:CORBA Name Browser View"></a>
<a
href="mainap3.html#corba"><span
class="cmbx-12">CORBA</span></a> <span
class="cmbx-12">Name Browser</span> </dt><dd
class="description">Maps names to specific <a
href="mainap3.html#corba">CORBA</a> Servants. The <a
href="#glo:CORBA Name Browser View"><a
href="mainap3.html#corba">CORBA</a> Name
Browser</a> can be used to examine the current contents of the <a
href="#glo:namingservice">Naming Service</a> as well as
perform basic manipulation of that context. The contents of the view will display all
currently bound name contexts (folders) and objects. The <a
href="#glo:CORBA Name Browser View"><a
href="mainap3.html#corba">CORBA</a> Name Browser</a> can
be seen in <a
href="mainch19.html#x21-262002r3">Figure 19.3</a>.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:device"></a>
<span
class="cmbx-12">Device</span> </dt><dd
class="description">“The SCA defines a <span
class="cmtt-12">Device </span>interface class. This interface is an abstraction of a
hardware device that defines the capabilities, attributes, and interfaces for that device.”
Source: SCA v2.2.2. In the context of REDHAWK, a Device is is a software module
that implements the <span
class="cmtt-12">Device </span>interface class.
</dd><dt class="description">
<a
id="glo:devicemanager"></a>
<span
class="cmbx-12">Device Manager</span> </dt><dd
class="description">An implementation of the <span
class="cmtt-12">DeviceManager </span>interface. The Device
Manager is responsible for the creation of Devices and Services.
</dd><dt class="description">
<a
id="glo:domain"></a>
<span
class="cmbx-12">Domain</span> </dt><dd
class="description">“A Domain defines a set of hardware devices and available applications under the
control of a single Domain Manager.” Source: SCA v2.2.2.
</dd><dt class="description">
<a
id="glo:domainmanager"></a>
<span
class="cmbx-12">Domain Manager</span> </dt><dd
class="description">“An implementation of the <span
class="cmtt-12">DomainManager </span>interface, a domain
manager manages the complete set of available hardware devices and applications. It
is responsible for the set-up and shut-down of applications and for allocating resources,
devices, and non-CORBA components to hardware devices.” Source: SCA v2.2.2.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:editor"></a>
<span
class="cmbx-12">Editor</span> </dt><dd
class="description">Depending on the type of file that is being edited, the appropriate editor is displayed
in the editor area. For example, if a .TXT file is being edited, a text editor is displayed
in the editor area. Source: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:Error Log View"></a>
<span
class="cmbx-12">Error Log View</span> </dt><dd
class="description">An Eclipse view that provides details of errors that have occurred with
the running application.
</dd><dt class="description">
<a
id="glo:eventchannel"></a>
<span
class="cmbx-12">Event Channel</span> </dt><dd
class="description">A software object that mediates the transfer of CORBA events between
producers and consumers.
</dd><dt class="description">
<a
id="glo:eventservice"></a>
<span
class="cmbx-12">Event Service</span> </dt><dd
class="description">Software that provides and manages <a
href="#glo:eventchannel">Event Channels</a>.
</dd><dt class="description">
<a
id="glo:extension"></a>
<span
class="cmbx-12">Extension</span> </dt><dd
class="description">This plug-in adds a contribution (extension) to an existing extension point.
Extensions to an extension point are defined in the plug-ins via the plugin.xml file.
Contributions can be code or data.
</dd><dt class="description">
<a
id="glo:extensionPoint"></a>
<span
class="cmbx-12">Extension Point</span> </dt><dd
class="description">If a plug-in defines an extension points it allows other plug-ins to add
functionality based on the contract defined by the extension point. The defining plug-in
is also responsible for evaluating contributions to the defined extension point. Therefore
the defining plug-in contains coding to evaluate the extensions.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:filemanager"></a>
<span
class="cmbx-12">File Manager</span> </dt><dd
class="description">An implementation of the <span
class="cmtt-12">FileManager </span>interface, the File Manager provides
a central access point for all of the file systems available in the Domain
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:message"></a>
<span
class="cmbx-12">Message</span> </dt><dd
class="description">Key/value pairs contained in a single instance of the <a
href="mainap3.html#corba">CORBA</a>::Any type and
passed over the <a
href="mainap3.html#corba">CORBA</a> event <a
href="mainap3.html#api">API</a>.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:namingservice"></a>
<span
class="cmbx-12">Naming Service</span> </dt><dd
class="description">Software that provides a mapping between human-readable names of
<a
href="mainap3.html#corba">CORBA</a> objects and the <a
href="mainap3.html#corba">CORBA</a> objects themselves
</dd><dt class="description">
<a
id="glo:node"></a>
<span
class="cmbx-12">Node</span> </dt><dd
class="description">A single <a
href="#glo:devicemanager">Device Manager</a>, its associated <a
href="#glo:device">Devices</a>, and its associated <a
href="#glo:service">Services</a>.
</dd><dt class="description">
<a
id="glo:Node Editor"></a>
<span
class="cmbx-12">Node Editor</span> </dt><dd
class="description">The Node Editor is opened by double clicking a <a
href="mainap3.html#dcd">DCD</a> file from the <a
href="#glo:Project Explorer View"><span
class="cmbx-12">Project</span>
<span
class="cmbx-12">Explorer View</span></a>. It presents all the content that can be found within the <span
class="cmtt-12">dcd.xml</span>
file in an editing environment designed for human use. The <a
href="#glo:node"><span
class="cmbx-12">Node</span></a> <span
class="cmbx-12">Editor </span>contain an
<span
class="cmbx-12">Overview</span>, <a
href="#glo:device"><span
class="cmbx-12">Devices</span></a>, <span
class="cmbx-12">Diagram</span>, and a raw <a
href="mainap3.html#xml">XML</a> tab which contains the <a
href="mainap3.html#dcd">DCD</a> file
content. For further details refer to <a
href="mainch19.html#x21-26900019.4.2">Section 19.4.2</a>.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:Outline View"></a>
<span
class="cmbx-12">Outline View</span> </dt><dd
class="description">Displays an outline of a structured file that is currently open in the editor
area. The <a
href="#glo:Outline View"><span
class="cmbx-12">Outline View</span></a> is a part of Eclipse and the basic use is well documented by
the Eclipse documentation: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:perspective"></a>
<span
class="cmbx-12">Perspective</span> </dt><dd
class="description">Each Workbench window contains one or more perspectives. A perspective
defines the initial set and layout of views in the Workbench window. Within the
window, each perspective shares the same set of editors. Each perspective provides a
set of functionality aimed at accomplishing a specific type of task or works with specific
types of resources. For example, the Java perspective combines views that you would
commonly use while editing Java source files, while the Debug perspective contains
the views that you would use while debugging Java programs. As you work in the
Workbench, you will probably switch perspectives frequently. Perspectives control what
appears in certain menus and toolbars. They define visible action sets, which you can
change to customize a perspective. You can save a perspective that you build in this
manner, making your own custom perspective that you can open again later. Source:
<a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:port"></a>
<span
class="cmbx-12">Port</span> </dt><dd
class="description">A <a
href="mainap3.html#corba">CORBA</a> object that produces or consumes data and/or commands. A Port is
referred to as “uses” when it is a source/producer/output, and as a “provides” when
it is a sink/consumer/input. A uses Port implements the CF::Port interface (see SCA
v2.2.2 for a description of CF::Port).
</dd><dt class="description">
<a
id="glo:Problems View"></a>
<span
class="cmbx-12">Problems View</span> </dt><dd
class="description">As you work with resources in the workbench, various builders may
automatically log problems, errors, or warnings in the Problems view. The <a
href="#glo:Problems View"><span
class="cmbx-12">Problems</span>
<span
class="cmbx-12">View</span></a> is a part of Eclipse and the basic use is well documented by the Eclipse
documentation: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:Project Explorer View"></a>
<span
class="cmbx-12">Project Explorer View</span> </dt><dd
class="description">Provides a hierarchical view of the resources in the Workbench.
The <a
href="#glo:Project Explorer View"><span
class="cmbx-12">Project Explorer View</span></a> is a part of Eclipse and the basic use is well documented
by the Eclipse documentation: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:Properties View"></a>
<span
class="cmbx-12">Properties View</span> </dt><dd
class="description">Displays property names and basic properties of a selected resource. The
<a
href="#glo:Properties View"><span
class="cmbx-12">Properties View</span></a> is a part of Eclipse and the basic use is well documented by the
Eclipse documentation: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:property"></a>
<span
class="cmbx-12">Property</span> </dt><dd
class="description">“An SCA Property is a variable that contains a value of a specific type.
Configuration Properties are parameters to the <span
class="cmtt-12">configure </span>and <span
class="cmtt-12">query </span>operations of
the <span
class="cmtt-12">PropertySet </span>interface. Allocation Properties define the capabilities required of a
Device by a Resource.” Source: SCA v2.2.2.
</dd><dt class="description">
<a
id="glo:PyDev"></a>
<span
class="cmbx-12">PyDev</span> </dt><dd
class="description">PyDev is a third-party plug-in for Eclipse. It is an <a
href="mainap3.html#ide">IDE</a> used for programming
in Python supporting code refactoring, graphical debugging, code analysis and many
other features
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:Sandbox"></a>
<span
class="cmbx-12">Sandbox</span> </dt><dd
class="description">A Python environment that can be used to easily run and interact with
<a
href="#glo:component">Components</a> without having to create a <a
href="#glo:waveformapplication">Waveform</a> or having to run a <a
href="#glo:domainmanager">Domain Manager</a>.
</dd><dt class="description">
<a
id="glo:SCA Explorer"></a>
<a
href="mainap3.html#sca"><span
class="cmbx-12">SCA</span></a> <span
class="cmbx-12">Explorer</span> </dt><dd
class="description">The REDHAWK <a
href="mainap3.html#sca">SCA</a> Explorer, an application built on the REDHAWK
Core Framework, is used to navigate the contents of an <a
href="mainap3.html#sca">SCA</a> <a
href="#glo:domain">Domain</a>. It provides
capabilities for viewing the contents of the <a
href="#glo:domain">Domain</a>, configuring <a
href="#glo:domain">Domain</a> resources,
and launching <a
href="#glo:domain">Domain</a> <a
href="#glo:waveformapplication">Waveforms</a>. REDHAWK provides both <a
href="mainap3.html#rcp">RCP</a> and <a
href="mainap3.html#rap">RAP</a>
instantiations of the <a
href="mainap3.html#sca">SCA</a> Explorer. The <a
href="mainap3.html#rap">RAP</a> <a
href="mainap3.html#sca">SCA</a> Explorer is provided as a Web
ARchive (<a
href="mainap3.html#war">WAR</a>) file.
</dd><dt class="description">
<a
id="glo:SCA Explorer View"></a>
<a
href="mainap3.html#sca"><span
class="cmbx-12">SCA</span></a> <span
class="cmbx-12">Explorer View</span> </dt><dd
class="description">Allows a user to navigate the contents of an <a
href="mainap3.html#sca">SCA</a> <a
href="#glo:domain">Domain</a>. It provides
capabilities for viewing the contents of the <a
href="#glo:domain">Domain</a>, configuring instantiated resources,
and launching <a
href="#glo:application">Applications</a> in a target <a
href="mainap3.html#sdr">SDR</a> environment. It also provides access to
the <a
href="#glo:Sandbox"><span
class="cmbx-12">Sandbox</span></a>, which is an environment for running <a
href="#glo:component">Components</a> and <a
href="#glo:application">Applications</a>
without <a
href="#glo:domainmanager">Domain Manager</a> and <a
href="#glo:devicemanager">Device Manager</a>. Exploring an active <a
href="#glo:domain">Domain</a> using the
REDHAWK <a
href="mainap3.html#ide">IDE</a> is discussed in <a
href="mainch22.html#x24-30500022">Chapter 22</a>. The <a
href="#glo:SCA Explorer View"><a
href="mainap3.html#sca"><span
class="cmbx-12">SCA</span></a> <span
class="cmbx-12">Explorer View</span></a> can be seen
in <a
href="mainch19.html#x21-262001r2">Figure 19.2</a>.
</dd><dt class="description">
<a
id="glo:waveform"></a>
<span
class="cmbx-12">SCA Waveform</span> </dt><dd
class="description">Deprecated. See <a
href="#glo:waveformapplication">Waveform</a>.
</dd><dt class="description">
<a
id="glo:service"></a>
<span
class="cmbx-12">Service</span> </dt><dd
class="description">Software made available by the <a
href="#glo:devicemanager">Device Manager</a> at the <a
href="#glo:devicemanager">Device Manager</a> startup.
</dd><dt class="description">
<a
id="glo:SoftPkg Editor"></a>
<span
class="cmbx-12">SoftPkg Editor</span> </dt><dd
class="description">The <a
href="#glo:SoftPkg Editor"><span
class="cmbx-12">SoftPkg Editor</span></a> is opened by double clicking an <a
href="mainap3.html#spd">SPD</a> file from
the <a
href="#glo:Project Explorer View"><span
class="cmbx-12">Project Explorer View</span></a>. It presents all the content that can be found within
the <span
class="cmtt-12">spd.xml </span>file in an editing environment designed for human use. If the <a
href="mainap3.html#spd">SPD</a> file
references a <a
href="mainap3.html#prf">PRF</a> or <a
href="mainap3.html#scd">SCD</a> file, additional tabs are made available that represent these
files in similar fashion. For further details refer to <a
href="mainch19.html#x21-26500019.4.1">Section 19.4.1</a>.
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:targetSDR"></a>
<span
class="cmbx-12">Target </span><a
href="mainap3.html#sdr"><span
class="cmbx-12">SDR</span></a> </dt><dd
class="description">The Target SDR refers to the SCA resources which your workspace will be
built and run against. It describes the platform that you are developing for. By default,
points to the file location specified by the environment variable <span
class="cmtt-12">SDRROOT</span>
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:view"></a>
<span
class="cmbx-12">View</span> </dt><dd
class="description">A view is a workbench part that can navigate a hierarchy of information or display
properties for an object. Only one instance of any given view is open in a workbench
page. When the user makes selections or other changes in a view, those changes
are immediately reflected in the workbench. Views are often provided to support a
corresponding editor. For example, an outline view shows a structured view of the
information in an editor. A properties view shows the properties of an object that is
currently being edited. Source: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
</dt><dd
class="description">
</dd><dt class="description">
<a
id="glo:waveformapplication"></a>
<span
class="cmbx-12">Waveform</span> </dt><dd
class="description">A REDHAWK Waveform is analogous to an SCA Waveform Application.
A REDHAWK Waveform is defined as a composition of Components, their
interconnections, and their configuration overrides. This composition is defined in a
Software Assembly Descriptor file.
</dd><dt class="description">
<a
id="glo:Waveform Editor"></a>
<span
class="cmbx-12">Waveform Editor</span> </dt><dd
class="description">The <a
href="#glo:Waveform Editor"><span
class="cmbx-12">Waveform Editor</span></a> is opened by double clicking an <a
href="mainap3.html#sad">SAD</a> file from
the <a
href="#glo:Project Explorer View"><span
class="cmbx-12">Project Explorer View</span></a>. It presents all the content that can be found within
the <span
class="cmtt-12">sad.xml </span>file in an editing environment designed for human use. The <a
href="#glo:Waveform Editor"><span
class="cmbx-12">Waveform</span>
<span
class="cmbx-12">Editor</span></a> contains an <span
class="cmbx-12">Overview</span>, <span
class="cmbx-12">Diagram</span>, and a raw <a
href="mainap3.html#xml">XML</a> tab which contains the
<a
href="mainap3.html#sad">SAD</a> file content. For further details refer to <a
href="mainch19.html#x21-27000019.4.3">Section 19.4.3</a>.
</dd><dt class="description">
<a
id="glo:workbench"></a>
<span
class="cmbx-12">Workbench</span> </dt><dd
class="description">The term Workbench refers to the desktop development environment. The
Workbench aims to achieve seamless tool integration and controlled openness by
providing a common paradigm for the creation, management, and navigation of
workspace resources. Source: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a>
</dd><dt class="description">
<a
id="glo:workspace"></a>
<span
class="cmbx-12">Workspace</span> </dt><dd
class="description">In Eclipse, a workspace is a logical collection of projects that you are actively
working on. Source: <a
href="http://help.eclipse.org/" class="url" ><span
class="cmtt-12">http://help.eclipse.org/</span></a> </dd></dl>
<!--l. 4--><p class="noindent" ><a
id="likesection.2"></a><a
id="Q1-30-394"></a> <!--l. 7--><div class="crosslinks"><p class="noindent">[<a
href="mainli3.html" >next</a>] [<a
href="mainap3.html" >prev</a>] [<a
href="mainap3.html#tailmainap3.html" >prev-tail</a>] [<a
href="mainli2.html" >front</a>] [<a
href="main.html#mainli2.html" >up</a>] </p></div>
<!--l. 7--><p class="noindent" ><a
id="tailmainli2.html"></a>
<div class=license>
<hr>
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png" /></a><br /><span xmlns:dct="http:// purl.org/dc/terms/" property="dct:title">REDHAWK Documentation</span> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.
</div>
</body></html>