From 3fd401321decc9b6b4f42aebd56e3e6a7284f0fd Mon Sep 17 00:00:00 2001 From: Jack Jansen Date: Sun, 16 Mar 2003 20:41:58 +0000 Subject: Lots of textual changes suggested by Matthew Moelter. --- .../macpython_ide_tutorial/index.html | 26 +++++++++++----------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/Mac/OSXResources/app/Resources/English.lproj/Documentation/macpython_ide_tutorial/index.html b/Mac/OSXResources/app/Resources/English.lproj/Documentation/macpython_ide_tutorial/index.html index 70d04abfa5..cf515292f0 100644 --- a/Mac/OSXResources/app/Resources/English.lproj/Documentation/macpython_ide_tutorial/index.html +++ b/Mac/OSXResources/app/Resources/English.lproj/Documentation/macpython_ide_tutorial/index.html @@ -13,7 +13,7 @@

This document gives a very basic introduction to the - MacPython Integrated Development Environment on Mac OS. It was + MacPython Integrated Development Environment (IDE) on Mac OS. It was written specifically for MacPython 2.3 on Mac OS X, but most of it is applicable to MacPython-OS9 too. It is based on "One @@ -47,7 +47,7 @@ menu entry.

This is the interactive window to the IDE, it allows us to enter commands directly into Python, and as soon as we enter a command, -Python will execute it and spit out its result back to us. We'll be +Python will execute it and spit its result back to us. We'll be using this interactive window a lot when we're exploring Python: it's very nice because we get back our results immediately. If it helps, we can think of it as a very powerful calculator.

@@ -86,7 +86,7 @@ page, and start exploring with the interpreter. No time limit here. *grin*

neat, but if we close down Python and start it up again, how do we get the computer to remember what we typed?

-

The solution is a little subtle: we can't directly save what's on +

The solution is a little subtle: we can't directly save what's in the interpreter window, because it will include both our commands and the system's responses. What we'd like is to make a prepared file, with just our own commands, and to be able to save that file as a @@ -113,13 +113,13 @@ to edit windows in other editors such as TextEdit or BBEdit.

What we wanted to do before was save some of the stuff we had tried out on the interpreter window. Let's do that by typing (or -copy/pasting) those commands into our Program window.

+copy/pasting) those commands into our edit window.

Ok, we're done with copying and pasting. One big thing to notice is that we're careful to get rid of the ">>>" -prompts because there's not really part of our program. The +prompts because they're not really part of our program. The interpreter uses them just to tell us that we're in the interpreter, but now that we're editing in a separate file, we can remove the artifacts that the interpreter introduces. @@ -129,7 +129,7 @@ an extra empty print statement so our output ends with a newline.


-

Let's save the file now. The Save command is located under the File menu: +

Let's save the file now. The Save command is located under the File menu:

@@ -155,12 +155,12 @@ the trouble spot.

Python is often perceptive enough to direct us toward the problem, and in this case, it's telling us that we forgot to put something at -the end of this line. In this case, we need to add an additional -quotation mark. Let's add that in now.

+the end of this line. In this case, we need to add a +quotation mark at the end. Let's add that in now.

Other errors, which usually occur later, when your program has already done something, result in a different dialog that allows you -to look at variables and such in addition to only showing you where +to look at variables and such in addition to showing you where the error occurred.


@@ -173,9 +173,9 @@ the output of our program:


As we play with Python, we'll find ourselves "switching modes" -between the Interpreter window and the Program window. However, +between the Interpreter window and the edit window. However, if we try anything more complicated than two or three lines it -is often a good idea to work in an edit window, and align +is often a good idea to work in an edit window. Align your edit and output window such that you can see them at the same time.

This is pretty much all we need to know about the MacPython IDE to actually do @@ -184,10 +184,10 @@ breakdown of things to see and explore: