-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathlisting4.html
executable file
·399 lines (296 loc) · 15 KB
/
listing4.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
<!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>AutoSample - /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/idxAutomator-date.html">Automator</a> > <A HREF="javascript:location.replace('index.html');">AutoSample</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">AutoSample</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="AutoSample.zip">Download Sample</a></strong> (“AutoSample.zip”, 170.8K)<BR>
<strong><a href="AutoSample.dmg">Download Sample</a></strong> (“AutoSample.dmg”, 237.3K)</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 AutoSample 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 discusses using the AMWorkflowView and AMWorkflowController classes
to display and execute Automator Workflows, and describes the parts of the
project necessary to support the use of these classes.
The following four items are necessary for any project using the Automator
framework:
1. Add the Automator 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
"Automator.framework" (/System/Library/Frameworks/Automator.framework) to the
project.
2. Add a minimum system version Info.plist key.
Since the Automator.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 version 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 AutoSample target, clicking on the Info
icon, selecting the Properties tab, and then clicking on "Open Info.plist as
File".
3. Make sure the Target SDK is set to Mac OS X v10.5
You won't have to change this setting for this project, but if you are adding
the Automator framework to another project that you started with an earlier
version of the Mac OS than Mac OS X v10.5, then you will need to update the
Target SDK for the project. In the Groups & Files view, select the AutoSample
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
v10.5.
4. Add in the Automator framework header.
In the files where you will be using the Automator classes, add the import
statement '#import <Automator/Automator.h>' near the top of the file. This will
include all of the definitions for using the Automator framework.
Here is the import statement for the Automator framework headers:
#import <Automator/Automator.h>
The remainder of this read me file discusses items specific to this sample.
Overview
This sample displays a single window containing a list of workflows and a read
only AMWorkflowView. The workflows listed are the ones found in the
Application's resources in the folder:
/AutoSample.app/Contents/Resources/workflows/
When the application starts up it scans the workflows folder and loads each
Automator workflow found there as an instance of AMWorkflow. It then stores
these AMWorkflow instances in an array along with the file names. That array is
used as the backing store for the NSTableView in the window.
When a click is received on the name of a workflow in the NSTableView, the
workflow is displayed in the AMWorkflowView on the right hand side of the
window.
When a double-click is received on the name of a workflow in the NSTableView
(or, when the "run" button is pressed), the selected workflow is displayed in
the AMWorkflowView on the right hand side of the window and it is run.
Initialization Details
All of the setup for this sample is performed in the -awakeFromNib method. The
important features to note there are as follows:
(a) The AMWorkflowView is being used for display purposes only. As such, we
mark the view as read only by turning off it's editing features with the
following method call:
[workflowView setEditable: NO];
(b) We don't actually manage the AMWorkflowView ourselves. Rather, we use an
AMWorkflowController to take care of that. In this sample, we have added an
AMWorkflowController to our .nib file and we have set the AMWorkflowView
displayed in the main window as it's workFlowView.
With this arrangement, our Controller object does not have to worry about the
details of operating the AMWorkflowView's user interface, as the
AMWorkflowController will take care of that.
So methods in the Controller object can receive information about the status of
the view we have set our Controller object as the AMWorkflowController's
delegate. With our controller object set as the AMWorkflowController delegate,
the AMWorkflowController will call back to our Controller object to provide
status information about the AMWorkflow it is displaying in the AMWorkflowView.
To run and display specific AMWorkflows, we will want to call methods on the
AMWorkflowController. So we can do that from methods implemented in the
Controller object, we have added an instance variable to the Controller object
where we store a reference to the AMWorkflowController object.
All of these releationships have been set up by control-dragging between
objects in the Interface Builder interface. You can use the connections
inspector in Interface Builder to examine these connections.
(c) We allocate and initialize all of the AMWorkflow instances for the
workflows found in our Resources folder and we store them in a NSArray. It's
worth noting that we populate the NSArray with NSDictionary records that include
the AMWorkflow instance, the file name, and the path.
(d) we have set up an array controller to manage the contents of the
NSTableView. To do that, we have bound the content array of the array
controller to the workflows value stored in our Controller object. In the
column of the table we have bound the value to the arrangedObjects controller
key on the Array Controller. Back in our controller object, we have stored a
reference to the Array Controller in the tableContent outlet so we can access
its arrangedObjects value (to allow us to access the values displayed in the
table no matter how the user has sorted the list by clicking on the table
header).
AMWorkflowController delegate methods
We implement two AMWorkflowController delegate methods in this sample. Namely,
workflowControllerWillRun: and workflowControllerDidRun:. The first method is
called just before a workflow being managed by the AMWorkflowController is run
and the second is called just after it finishes running.
We use these methods to display the progress bar and to set the internal
runningWorkflow flag. We use bindings based on the runningWorkflow flag to
display the progress bar, enable the stop button while a workflow is running,
and disable the run button while a workflow is running. Also, we use the
runningWorkflow flag to prevent certain user actions, such as switching the
AMWorkflowController to another workflow, while a workflow is still running.
Running a workflow
We have set the run method on the AMWorkflowController as the target action for
the run button. Bindings based on the runningWorkflow flag control the
availability of this button (by controlling its enabled state) for starting a
new workflow.
We have set the stop method on the AMWorkflowController as the target action
for the stop button. Bindings based on the runningWorkflow flag control the
availability of this button (by controlling its enabled state) for stopping a
new workflow.
Where to next?
Documentation for Automator AMWorkflowController and AMWorkflow can be found in
the developer documentation. To find the AMWorkflowController and AMWorkflow
documentation, select 'Documentation' from the Help Menu in Xcode, and type
AMWorkflow or AMWorkflowController into the search field near the top of the
window.
</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/AutoSample/listing4.html%3Fid%3DDTS10004313-1.0&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/AutoSample/listing4.html%3Fid%3DDTS10004313-1.0&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/AutoSample/listing4.html%3Fid%3DDTS10004313-1.0&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>