Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
097da0dc
Commit
097da0dc
authored
Jun 13, 2003
by
Jack Jansen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documented the fact that the main class now mimicks the OSA "application" class.
parent
880be6f1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
5 deletions
+7
-5
Doc/mac/scripting.tex
Doc/mac/scripting.tex
+7
-5
No files found.
Doc/mac/scripting.tex
View file @
097da0dc
...
...
@@ -31,7 +31,7 @@ In Python, the following code fragment will do the same:
import Finder
f = Finder.Finder()
print f.get(
Finder
.window(1).name)
print f.get(
f
.window(1).name)
\end{verbatim}
As distributed the Python library includes packages that implement the
...
...
@@ -64,10 +64,12 @@ direct object as the first argument and all optional parameters as
keyword arguments. AppleScript classes are also implemented as Python
classes, as are comparisons and all the other thingies.
Note that in the current release there is no coupling between the main
Python class implementing the verbs and the Python classes implementing
the AppleScript classes. Hence, in the example above we need to use
\code
{
f.get(Finder.window(1).name)
}
in stead of the more Pythonic
The main
Python class implementing the verbs also allows access to the properties
and elements declared in the AppleScript class "application". In the
current release that is as far as the object orientation goes, so
in the example above we need to use
\code
{
f.get(f.window(1).name)
}
in stead of the more Pythonic
\code
{
f.window(1).name.get()
}
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment