forked from cellularmitosis/ADC-reference-library-2009-july
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathlisting4.html
More file actions
executable file
·681 lines (498 loc) · 27.8 KB
/
Copy pathlisting4.html
File metadata and controls
executable file
·681 lines (498 loc) · 27.8 KB
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
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<!-- BEGIN META TAG INFO -->
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<link rel="home" href="http://developer.apple.com/">
<link rel="find" href="http://developer.apple.com/search/">
<link rel="stylesheet" type="text/css" href="../../documentation/css/adcstyle.css" title="fonts">
<script language="JavaScript" src="../../documentation/js/adc.js" type="text/javascript"></script>
<!-- END META TAG INFO -->
<!-- BEGIN TITLE -->
<title>ScriptingBridgeFinder - /ReadMe.txt</title>
<!-- END TITLE -->
<script language="JavaScript">
function JumpToNewPage() {
window.location=document.scpopupmenu.gotop.value;
return true;
}
</script>
</head>
<!-- BEGIN BODY OPEN -->
<body>
<!--END BODY OPEN -->
<!-- START CENTER OPEN -->
<center>
<!-- END CENTER OPEN -->
<!-- BEGIN LOGO AND SEARCH -->
<!--#include virtual="/includes/adcnavbar"-->
<!-- END LOGO AND SEARCH -->
<!-- START BREADCRUMB -->
<div id="breadcrumb">
<table width="680" border="0" cellpadding="0" cellspacing="0">
<tr>
<td scope="row"><img width="340" height="10" src="images/1dot.gif" alt=""></td>
<td><img width="340" height="10" src="images/1dot.gif" alt=""></td>
</tr>
<tr valign="middle">
<td align="left" colspan="2">
<a href="http://developer.apple.com/">ADC Home</a> > <a href="../../referencelibrary/index.html">Reference Library</a> > <a href="../../samplecode/index.html">Sample Code</a> > <a href="../../samplecode/ScriptingAutomation/index.html">Scripting & Automation</a> > <a href="../../samplecode/ScriptingAutomation/idxScriptingBridges-date.html">Scripting Bridges</a> > <A HREF="javascript:location.replace('index.html');">ScriptingBridgeFinder</A> >
</td>
</tr>
<tr>
<td colspan="2" scope="row"><img width="680" height="35" src="images/1dot.gif" alt=""></td>
</tr>
</table>
</div>
<!-- END BREADCRUMB -->
<!-- START MAIN CONTENT -->
<!-- START TITLE GRAPHIC AND INTRO-->
<table width="680" border="0" cellpadding="0" cellspacing="0">
<tr align="left" valign="top">
<td><h1><div id="pagehead">ScriptingBridgeFinder</div></h1></td>
</tr>
</table>
<!-- END TITLE GRAPHIC AND INTRO -->
<!-- START WIDE COLUMN -->
<table width="680" border="0" cellpadding="0" cellspacing="0">
<tr align="left" valign="top">
<td id="scdetails">
<h2>/ReadMe.txt</h2>
<form name="scpopupmenu" onSubmit="return false;" method=post>
<p><strong>View Source Code:</strong>
<select name="gotop" onChange="JumpToNewPage();" style="width:340px"><option selected value="ingnore">Select File</option>
<option value="listing1.html">/Controller.h</option>
<option value="listing2.html">/Controller.m</option>
<option value="listing3.html">/main.m</option>
<option value="listing4.html">/ReadMe.txt</option></select>
</p>
</form>
<p><strong><a href="ScriptingBridgeFinder.zip">Download Sample</a></strong> (“ScriptingBridgeFinder.zip”, 73.8K)<BR>
<strong><a href="ScriptingBridgeFinder.dmg">Download Sample</a></strong> (“ScriptingBridgeFinder.dmg”, 130.1K)</p>
<!--
<p><strong><a href="#">Download Sample</a></strong> (“filename.sit”, 500K)</p>
-->
</td>
</tr>
<tr>
<td scope="row"><img width="680" height="10" src="images/1dot.gif" alt=""><br>
<img height="1" width="680" src="images/1dot_919699.gif" alt=""><br>
<img width="680" height="20" src="images/1dot.gif" alt=""></td>
</tr>
<tr>
<td scope="row">
<!--googleon: index -->
<pre class="sourcecodebox">File: ReadMe.txt
Abstract: readme file for the ScriptingBridgeFinder sample.
Version: 1.0
(c) Copyright 2007 Apple, Inc. All rights reserved.
IMPORTANT: This Apple software is supplied to
you by Apple, Inc. ("Apple") in
consideration of your agreement to the following
terms, and your use, installation, modification
or redistribution of this Apple software
constitutes acceptance of these terms. If you do
not agree with these terms, please do not use,
install, modify or redistribute this Apple
software.
In consideration of your agreement to abide by
the following terms, and subject to these terms,
Apple grants you a personal, non-exclusive
license, under Apple's copyrights in this
original Apple software (the "Apple Software"),
to use, reproduce, modify and redistribute the
Apple Software, with or without modifications, in
source and/or binary forms; provided that if you
redistribute the Apple Software in its entirety
and without modifications, you must retain this
notice and the following text and disclaimers in
all such redistributions of the Apple Software.
Neither the name, trademarks, service marks or
logos of Apple Computer, Inc. may be used to
endorse or promote products derived from the
Apple Software without specific prior written
permission from Apple. Except as expressly
stated in this notice, no other rights or
licenses, express or implied, are granted by
Apple herein, including but not limited to any
patent rights that may be infringed by your
derivative works or by other works in which the
Apple Software may be incorporated.
The Apple Software is provided by Apple on an "AS
IS" basis. APPLE MAKES NO WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING
THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE
OR IN COMBINATION WITH YOUR PRODUCTS.
IN NO EVENT SHALL APPLE BE LIABLE FOR ANY
SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE,
REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF
THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER
UNDER THEORY OF CONTRACT, TORT (INCLUDING
NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, EVEN
IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Introduction
This file details the steps involved in putting together a project that uses
Scripting Bridge to send Apple events to the Finder application for finding
and launching applications.
1. Start with a new Objective-C application.
This targets the Finder application and was built using the 'Cocoa Application'
Xcode template. The techniques we are demonstrating in this sample can be used
in any Cocoa Application.
2. Add a Scripting Bridge build rule to the project.
The first thing to do is to set up Xcode to automatically generate the
Scripting Bridge source for the application you would like to target. The
following steps describe how you can do that:
(a) Turn down the "Targets" tab in the "Groups & Files" list on the left hand
side and select the main target. In this sample, select the
"ScriptingBridgeFinder" target.
(b) With the "ScriptingBridgeFinder" target selected, open the information
panel (by clicking on the Info icon, or by control- or right-clicking on the
target name and selecting "Get Info" from the pop-up menu).
(c) In the info window, click on the Rules tab and then click on the + button
at the bottom to add a new rule.
(d) Set up the new rule as follows:
Process 'Source files with names matching:' *.app
using: 'Custom Script'
set the script field to:
sdef "$INPUT_FILE_PATH" | sdp -fh -o "$DERIVED_FILES_DIR" --basename
"$INPUT_FILE_BASE" --bundleid `defaults read "$INPUT_FILE_PATH/Contents/Info"
CFBundleIdentifier`
click on the "+" icon below the 'with output files:' field, and then set the
field to contain:
$(DERIVED_FILES_DIR)/$(INPUT_FILE_BASE).h
NOTE: if you're typing this rule in by hand, note that it should all be one
one line, and it must be typed exactly as shown above. If you have difficulty
entering the above command, then copy and paste the command from the readme into
the rule.
(e) All done. You can close the info window. Xcode is now set up to
automatically generate Scripting Bridge source for any applications you add to
your project.
NOTE: this rule uses the sdef and sdp command line tools. To learn more about
these tools, use the following commands in the Terminal window:
man sdp
man sdef
3. Select a target application.
To do this, drag and drop the application you would like to target into the
project files group inside of the "Groups & Files" list in the project window.
You can drop the application among the source files you are using for your
application. Because of the build rule we added in step 2, Xcode will treat the
Finder application as if it were one of the source files during the build.
You should uncheck the 'Copy items into destination group's folder (if needed)'
option so the application is not copied into your project directory. In this
sample we have selected 'Absolute Path' as the reference type so we can easily
move the project around from machine to machine without invalidating the
reference (so long as the Finder application is present in the
System/Library/CoreServices folder, Xcode will be able to find it).
In this case, we are adding the Finder to our project. The Finder application
is located in the /System/Library/CoreServices folder.
4. Add the target application to the Compile Sources.
After you have added the target application to your project, you must also add
it to the main target's Compile Sources. You can do that by adding the
application to the 'Compile Sources' build phase under the main target. In the
"Groups & Files" list, open the "Targets" and the "ScriptingBridgeFinder" target
and the Compile Sources build phase items by clicking on the arrows to the left
of them. Then, drag the Finder.app from the project files group into the
Compile Sources.
5. Add the Scripting Bridge framework to your project.
Turn down the "Frameworks" group in the Groups & Files area, and then
control-click (or right click) on the "Linked Frameworks" sub-group. Select
"Add > Existing Frameworks..." from the pop-up menu. Then, add the
"ScriptingBridge.framework"
(/System/Library/Frameworks/ScriptingBridge.framework) to the project.
6. Add a minimum system version Info.plist key.
Since the ScriptingBridge.framework is necessary for this application to run
and that framework is not present on previous system versions, you should add
the following key/value pair to the Info.plist file for the application. If
someone tries to run this application on a system earlier than Mac OS X 10.5,
then they will receive a notice from launch services letting them know that the
application is meant to be run on a later version of Mac OS X.
<key>LSMinimumSystemVersion</key>
<string>10.5</string>
You can edit the Info.plist file by either clicking on its icon in the
resources section, or by clicking on the ScriptingBridgeFinder target, clicking
on the Info icon, selecting the Properties tab, and then clicking on "Open
Info.plist as File".
7. Make sure the Target SDK is set to Mac OS X 10.5
You won't have to change this setting for this project, but if you are adding
Scripting Bridge to another project that you started an earlier version of the
Mac OS than Mac OS X 10.5, then you will need to update the Target SDK for the
project. In the Groups & Files view, select the ScriptingBridgeFinder project
icon at the top of the list and then open the information window. Under the
General tab, change the Cross-Develop Using Target SDK: setting to Mac OS X
10.5.
8. Build your project.
If you have followed the steps above, Xcode will generate the Scripting Bridge
source for your project. They will be put inside of your build folder in a
place where the linker and compiler can find them.
The build rule that we installed will create a .h file with the same name as
the application. For example, if you added Finder to our project, then the
build rule will create Finder.h. The files will be created inside of the build
directory in the DerivedSources directory where the compiler can find them.
For the Debug build, the Finder.h file will be located in this sub folder of
the build directory:
/build/ScriptingBridgeFinder.build/Debug/ScriptingBridgeFinder.build/DerivedSources/Finder.h
For the Release build, the Finder.h file will be located in this sub folder of
the build directory:
/build/ScriptingBridgeFinder.build/Release/ScriptingBridgeFinder.build/DerivedSources/Finder.h
A convenient way for you to open and inspect these files is to use the 'Open
Quickly' command in the file menu. For most purposes, the .h file will contain
most of the interesting information so to view that file you open the 'Finder.h'
file.
In some cases, depending on what frameworks are in your project, the 'Open
Quickly' command may open the system's 'Finder.h' file that includes constants
and definitions used by the file system and the Finder application. If that
happens for you, then you will need to navigate into the build folder to find
the correct header file.
9. Add in the Finder's Scripting Bridge header.
In the file Controller.h, add '#import "Finder.h"' near the top of the file
below '#import <Cocoa/Cocoa.h>'. This will include all of the Scripting Bridge
definitions for the Finder.
When you're done, the imports section should look like this:
#import <Cocoa/Cocoa.h>
#import "Finder.h"
In your own application, of course, you would import the Finder.h file in the
file where you intend to use the definitions it contains. In this sample, we
are using the Scripting Bridge interface inside of three methods and for a
property in our Controller class so that is why we are importing it into
Controller.h.
10. Roadmap - check out what the Scripting Bridge Finder sample is doing.
So, we've set up our sample and installed the basic parts. Let's take a moment
to look at the bigger picture so we can see where we're going and how Scripting
Bridge fits into this sample.
In this sample we're displaying a list of applications in a window and if the
user double clicks on one of them (or selects one and clicks on the Launch
button), then we ask the Finder to launch it. So, what are the different parts
of that picture, how are we accomplishing that, and how does Scripting Bridge
fit into that picture? The following points should help explain those
questions.
(a) We're storing all of the information about the applications we find in the
Application's folder in a table of records (implemented as an NSArray containing
instances of NSDictionary). For every application we find, we store the
'display name' of the application and a reference to the Scripting Bridge object
for the application in a NSDictionary in the main NSArray.
(b) In the awakeFromNib method, we designate our Controller object as the data
source and delegate for the list in the window. That means that when the list
is being drawn on the screen, it will ask our controller object for the data to
display in the list. In our Controller object we have implemented the methods
numberOfRowsInTableView: and tableView:objectValueForTableColumn:row: for this
purpose. Inside of those methods, we simply return values stored in our table
of records.
(c) There are some other methods associated with the list view for the purpose
of receiving double clicks. For more information about those, see the comments
in the Controller.m file.
(d) Repopulating the data stored inside of the table of records is where
Scripting Bridge comes in. You'll notice that at the end of the awakeFromNib
method we have designated the updateApplicationsTable method to receive
NSApplicationDidBecomeActiveNotification notifications. This means that our
updateApplicationsTable method will be called whenever ScriptingBridgeFinder is
switched into the forground in front of other applications.
And that's a great time to update the list of applications. If our application
was in the background it may very well be the case that the user made some
changes or added some new programs. By refreshing our list every time we're
switched in, we can be reasonbly sure that our list is up to date with what is
actually there.
Inside of the updateApplicationsTable method we call Scripting Bridge to scan
through the Application's folder (two levels deep) to scrounge for applications.
Any applications that we find, we add into the table of records that we are
displaying in the list in the window. And, then we tell the list to re-draw
itself.
(e) The second place where we put Scripting Bridge to work is inside of the
launchSelected: method. We have set up this method so that it will be called
whenever the Launch button is clicked in the window or when the user double
clicks on an item in the list of applications in the window.
In the launchSelected: method we get the scripting bridge object for the
application selected in the list view out of the table of records and then we
use Scripting Bridge to ask the Finder to launch the application for us.
In the following steps discuss adding in the Scripting Bridge parts that fit
into this roadmap into the sample, and we'll provide some additional explanation
along the way.
11. Allocate an instance of the Finder Scripting Bridge object.
In this application the Finder SBApplication object is used in a number of
routines so rather than allocating the object whenever it is needed it is
allocated once at startup time and a reference to it is stored in a property of
the Controller class.
/* allocate our scripting bridge object */
self.finder = [SBApplication
applicationWithBundleIdentifier:@"com.apple.finder"];
Note that the SBApplication object is being created using the
-applicationWithBundleIdentifier: method. This method will dynamically load and
build the Scripting Bridge classes for the Finder from the Finder application.
12. Start populating the list of applications.
The first thing we're going to want to do is start building the list of
applications we can launch. One of the simplest ways to do that, of course, is
to ask the Finder to find the applications in the Applications folder for you.
So, that's what we're doing here. Interesting points about in this section are:
(a) We're using the construct '[[[[finder startupDisk] folders]
objectWithName:@"Applications"] exists]' to determine if a Applications folder
exists. The formulation '[[ <collection> objectWithName: <name> ] exists]' is
a pattern you'll use again and again in Scripting Bridge code when testing for
the existence of named elements.
(b) There's really no searching to do. If we want the applications, we can ask
the Finder for a list of them all by calling the applicationFiles method on the
Application's folder object.
(c) We call the 'displayedName' access on the individual application objects to
find out what name is being displayed in the Finder interface. This value will
be set correctly according to the user's view settings for the file.
(d) We're calling the NSArray method sortUsingFunction:context: to sort the
list of applications. This is a good example of using standard Cocoa
functionality together with Scripting Bridge to accomplish tasks that are
difficult to do in AppleScript alone.
The following code in the -updateApplicationsTable method in the file
Controller.m performs the operations described above. Note we have left out the
part that does a second level search for applications. We'll talk about that in
the next step.
/* if the applications folder exists... */
if ( [[[[finder startupDisk] folders] objectWithName:@"Applications"]
exists]) {
/* first, retrieve all of the applications in the main applications
folder. */
SBElementArray* topLevelApps = [[[[finder startupDisk] folders]
objectWithName:@"Applications"] applicationFiles];
for ( FinderApplicationFile* nthApplication in topLevelApps ) {
/* add each application to our list of applications */
[applications addObject:
[[NSDictionary alloc] initWithObjectsAndKeys:
nthApplication, @"sb-object", /* the scripting bridge
object */
[nthApplication displayedName], @"name", /* name - used for
display and sorting */
nil]];
}
/* step 13 code here -- second level search for applications */
/* sort the list of applications by name */
[applications sortUsingFunction:AppCompare context:nil];
/* tell the table view that the data has changed */
[applicationsTable reloadData];
}
13. The second level search for applications.
Searching the top level of the application's directory really doesn't buy us
much. After all, we could simply open the Application's folder in Finder and
there they all are. It would be more interesting find all those ones that are
hidden away inside of folders in the Applications folder. Displaying those in
our list would be much more interesting because it would save us the trouble of
poking around in sub folders looking for applications.
So, in this step we're going to add in an extra level of search to go through
all of the folders inside of the Applications folder to find applications stored
in there.
Now, you might think, why not make it entirely recursive and go through
everything in the Application's folder? Well, the reason why we've chosen the
two level route here is because it's not too common to have apps buried down
more than two levels deep. And, perhaps more importantly, it is very common for
larger applications to include immense directory hierarchies among their
resources for their help files, and other supporting data. Searching through
all of that would take a long time, and the odds of finding more apps there are
pretty slim. So, there's the reasoning behind our two level approach. Now, on
to implementing the rest of it...
In this step we're inserting some code into the code we added in the last step.
We're adding it into the code we added previously because we would like the
additional applications we find in this step sorted into the list we started
building in the last step.
Here, we ask the Finder for a list of all of the folders inside of the
Applications folder and then we iterate through them adding all of the
applications inside of them to our list of applications.
Adding in our second level search, we replace the comment mentioned in the last
section, '/* step 12 code here */', with the following code:
/* second, search every folder inside of the applications folder for
applications and add all of the applications we find into our list. */
/* get all of the folders inside of the Application's folder on the startup
disk */
SBElementArray* appFolders =[[[[finder startupDisk] folders]
objectWithName:@"Applications"] folders];
for ( FinderFolder* nthFolder in appFolders ) {
/* get all of the applications in the ith folder */
SBElementArray* secondLevelApps = [nthFolder applicationFiles];
for ( FinderApplicationFile* nthSecondLevelApp in secondLevelApps ) {
/* add each of those applications to our list of applications */
[applications addObject:
[[NSDictionary alloc] initWithObjectsAndKeys:
nthSecondLevelApp, @"sb-object", /* the scripting bridge object */
[nthSecondLevelApp displayedName], @"name", /* name - used for display
and sorting */
nil]];
}
}
14. The launching code
So far we have talked about the code to populate the list of applications
displayed in the window. Now that we have that information in place, we can go
ahead and add in code for launching them.
At the point where this code is executed, we have already determined that there
is a selection in the list and we know the index of the selection (stored in the
integer variable theRow). Here, we use that index to retrieve the scripting
bridge object from our table of records and then we ask the Finder to launch the
application.
It's worth mentioning here that though we're asking the Finder to launch the
application through the Scripting Bridge, you may have noticed that the way
we're doing it appears at though we're asking the application object to use the
Finder to launch itself. Namely, we're calling the openUsing:withProperties:
method on the on the selected application rather than calling an open method on
the FinderApplication instance. Here, it's worth pointing out that this is all
perfectly normal and the arrangement of methods here is purely a matter of how
the Finder's scripting dictionary has been set up.
Here is the relevant code from the launchSelected: method near the bottom of
the file Controller.m with the following code:
/* retrieve the selected application from our list
of applications. */
FinderApplicationFile* selectedApplication =
(FinderApplicationFile*) [(NSDictionary*)
[applications objectAtIndex: theRow]
objectForKey:@"sb-object"];
/* ask the finder to open the application. */
[selectedApplication openUsing:finder withProperties:nil];
15. Where to next?
Documentation for Scripting Bridge can be found in the Scripting Bridge Release
Note. To find the Scripting Bridge Release Note, select 'Documentation' from
the Help Menu in Xcode, select "Release Notes" from the "Jump To:" menu in the
top right of the document window, click on the "View the complete Release Notes
List." link near the top left of the window and scroll down to the Scripting
Bridge Release Note.
There are man pages available for the Scripting Bridge command line tools. To
access those pages, enter the following commands into the Terminal window:
man sdp
man sdef
There are two other Scripting Bridge samples available including
ScriptingBridgeiCal and ScriptingBridgeiTunes showing how to use Scripting
Bridge together with the Apps named in their titles.
</pre>
<!--googleoff: index -->
</td>
</tr>
</table>
<!-- END WIDE COLUMN -->
<!-- END MAIN CONTENT -->
<table width="680" border="0" cellpadding="0" cellspacing="0">
<tr>
<td><div style="width: 100%; height: 1px; background-color: #919699; margin-top: 5px; margin-bottom: 15px"></div></td>
</tr>
<tr>
<td align="center"><br/>
<table border="0" cellpadding="0" cellspacing="0" class="graybox">
<tr>
<th>Did this document help you?</th>
</tr>
<tr>
<td>
<div style="margin-bottom: 8px"><a href="http://developer.apple.com/feedback/?v=1&url=/samplecode/ScriptingBridgeFinder/listing4.html%3Fid%3DDTS10004283-1.1&media=dvd" target=_new>Yes</a>: Tell us what works for you.</div>
<div style="margin-bottom: 8px"><a href="http://developer.apple.com/feedback/?v=2&url=/samplecode/ScriptingBridgeFinder/listing4.html%3Fid%3DDTS10004283-1.1&media=dvd" target=_new>It’s good, but:</a> Report typos, inaccuracies, and so forth.</div>
<div><a href="http://developer.apple.com/feedback/?v=3&url=/samplecode/ScriptingBridgeFinder/listing4.html%3Fid%3DDTS10004283-1.1&media=dvd" target=_new>It wasn’t helpful</a>: Tell us what would have helped.</div>
</td>
</tr>
</table>
</td>
</tr>
</table>
<!-- START BOTTOM APPLE NAVIGATION -->
<!--#include virtual="/includes/footer"-->
<!-- END BOTTOM APPLE NAVIGATION -->
<!-- START CENTER CLOSE -->
</center>
<!-- END CENTER CLOSE -->
</body>
</html>