LogoWriter Tape 1 (1986)

LogoWriter Tape 1

Speaker 1:                    The following is the first of two videotapes featuring Seymour Papert on LogoWrtier. How to use it, and how to think about it. In demonstrating LogoWriter, Papert uses the occasion to deepen the viewers’ understanding of Logo itself.

Seymour Papert:           That’s one sort of LogoWriter graphics. Much less hard edged, you’ll notice, than what you usually see on Logo screens, though not at all less interesting and rich mathematically. It’s also easy. You should be able to do that sort of thing in your first half hour of contact with LogoWriter. 

                                    In a moment, I’m going to show you something somewhat more difficult. A LogoWriter project that’s a composite. A work by several teams of highly motivated fifth grade students. I think it really represents the level of achievement that a teacher who already knows Logo should be able to obtain after several days of immersion with LogoWriter. This project will be the first of four chapters in this module. In it, I don’t have a specific teaching goal. My goal is to help you set your goals rather than to get you techniques or specific ideas. I’d like you to see what you’re working towards.

                                    The second chapter will have a very specific teaching goal. I’d like to get you to that level in LogoWriter where you can do what you’re used to doing with ordinary Logo. My emphasis will be on getting you used to a new approach to writing procedures, to editing, to saving your work, to getting it back, to the whole area of interface management in Logo.

                                    It’s a third and fourth chapter that will bring us to doing things which really look different from what you’re used to being able to do. We’ll be doing projects that are almost impossible in tradition Logos. Before we get started, let me say something about computers. In the module, we’ll be working with Apple and IBM. As you know, LogoWriter sets out to have a new level of compatibility across computers. Most of what we’ll do will be the same and look very similar on the two computers when occasionally the keyboards dictate differences, we might mention them specifically. Let’s get going.

                                    Let’s boot up our LogoWriter and see what it looks like on the screen. When we obediently press Enter, you’ll see a screen that shows us the first of the major differences between LogoWriter and traditional Logo. The word contents refers to a metaphor used by LogoWriter to represent the material from previous work stored on the diskette. We select an item by moving the cursor down with the arrow. I’m selecting SKEL. I press Return, and you’ll see in a moment on the screen, the graphics and some text, and in a place that I’ll show you later, the procedures that drew them just as they were left, saved automatically by LogoWriter.

                                    Looking at the graphic, you see a second major difference. Look at the fine detail of the graphics. The skeleton was actually drawn by a team of four 5th grade students working together. I think with traditional Logos, they might have been able to draw it, but I doubt if they would have. Finally, the combination of text and graphics here shows us the third of major differences I shall be talking about; LogoWriter’s ability to deal with text, which is why it’s called LogoWriter. 

                                    I’m going to clear the screen and show you the procedures that put up this text and graphics. Start is the name of the procedure that clears the screen and positions the turtle to draw the skeleton. Skel is the procedure that does the actual work. There comes the skeleton. We’ll see later how that’s done. Finally, when cursor blinks again, the procedure what puts up the text. Now when we look more closely at this text, we’ll see the third aspect of LogoWriter in greater depth. This text is not just dead text written on a screen; it’s living text, interactive text. To show what I mean, I’m going to move this cursor, the active-blinking cursor up onto the text part of the screen by doing the up key. Once it’s there, I can move it around using the up arrow, and then the right arrow positioning it there, and you’ve guessed why, because I want to correct the spelling mistake. I type in E, and it’s corrected. In other words, we have here, not merely dead text on the screen, but all the power of a word processor. We can manipulate this text in many different ways. Let me show you one special one.

                                    I’m going to move the cursor down onto skull. I select skull; you’ll learn in a while what that means exactly. It being in red shows that it’s selected, and now when I obey this instruction, doing control-X, the skull turned blue showing which bone of the body was called the skull. I could have selected hand, clavicle, shin, or any other. Let’s see what happens when we press control-V. Control-V is going to get us into a database in which the young programmer has written some more text that tells us about the skull. The skull, he said, has several bones. It protects the brain. Surprisingly, Hamlet once recognized one, and so on. Of course this could have been biological knowledge, it could have been a description of the bones and how they fit together. It could have been advice about how to draw. 

                                    For me, the skeleton project hints at a new integration of computers into learning. First these integrations of computer methods, programming, text manipulation, database manipulation are inextricably mixed together. You can’t say it’s one or the other. There’s also the cause of this integration of the computer methods, a tighter kind of contribution to learning the biological knowledge into learning something just as important, the art of collaboration. I’m sure you’re eager to see what you’ll learn by doing such projects, but I think the best entry point is to begin by looking again at what you already know very well, at what you’re most familiar with.

                                    Let’s take a look once more at the familiar turtle. Here’s our turtle, and here’s a familiar instruction. Press Enter, and it draws a line. Right 144, which you know if we repeat will produce star, it turned. Now to continue the star, we could do forward again, but instead of that, in this version, I can do something very different. Watch the cursor. I put it back on forward, and we’ll see another way in which text remains active in this version, because when I hit Enter, it’ll do forward 100 again. Now it’s on right 144. Hit Enter, and it turned. Arrow key takes it up, and so I can draw the whole star without anymore typing, except hitting the arrow keys and the Enter key. The text of the constructions that have already been run are kept active.

                                    Let’s go back and see in more detail. I put it up once, I put it up twice on forward, I put it up on pen down. What’ll happen if I try again to put it up? It’ll bump against the red line, oh but see? You see there’s more there. These were the instructions that I used to set up the turtle for this demonstration. Clear Graphics clears it all away. Set color 9 made the color blue, pen up, setpos put it in the right place, pen down, forward 100, right, and so we see how the instructions remain active in what we call the instruction buffer. This might seem like a very small example, but it’s a big example to get us thinking about what goes on when we work with Logo.

                                    You may be surprised and [fussing 00:10:12] so much about being to reactivate an old instruction. After retyping forward 100 isn’t all that much work, but you’ll see that LogoWriter’s way of keeping text active is not only very very useful, beyond being useful, it leads us to more coherent, and I think much more concrete ways of thinking about what we’ve always been doing when we do Logo. To make this point, I’ve prepared some simple props that any teacher could make, and I recommend that teacher’s do make them. For example, this one represents the LogoWriter screen. There’s the red line that should be familiar by now. Up here is a star the turtle has drawn. This part, above the red line, is called the page; it’s where the turtle works, it’s where text appears. We saw the skeleton over there. Below the red line is called the command center. This is where we put commands. Here it’s as if a procedure had been written. Star and run, and that made the turtle draw this.

                                    Have you ever puzzled about where these procedures are that make the turtle draw things? Have you puzzled about where children think they are? Sometimes we say, they’re in the workspace, or in a computer’s memory, but these are very abstract ways of talking. Similarly, have you ever puzzled about what happens to old instructions that have been used and spent? We say the computer’s forgotten them, but there they are, often still on the screen. Again, there’s something abstract about the computer having forgotten what’s there visibly on its screen. I think we need much more concrete ways to think about all these issues. LogoWriter has been designed to provide some. 

                                    LogoWriter has a consistent metaphor for where the procedures are. Here’s the page, here’s the turtle’s work. Flip the page over. There’s the procedure, on the flip side of the page. This metaphase carried out consistently right through LogoWriter is a key call the flip key. If you’re on the flip side, press the flip key, you get on the front side of the page. If you’re on the front side, press the flip key, and you get on the flip side. On the flip side, you always find all the procedures. All the procedures that can be used at any given time. If you want to change them, you can use your word processor. When you write a procedure in the first place, you turn to the flip side and you type it in. The procedure is just a piece of text like any other text.

                                    Now what about direct commands? Let’s get rid of this and get this prop. Forward 100, right 144; that should be familiar. Here’s the cursor that we are moving up when we drew the star by direct commands. When the cursor got to the top, what happened? The analogy is with a scroll of ancient times. As we turn the roller, the next instruction comes down. They’re all there. We’re looking at them through a window. The command center, then, is a window through which we [inaudible 00:13:55] a place the instruction buffer where text can be written, and what’s written here is, again, text that can be processed, edited, changed, just like the text on the flip side of the page, just like anything you might write on the front side of the page. It is this concept of text that gives LogoWriter a special degree of coherence that no other Logo has ever had.

                                    We saw how to draw a star by direct instructions. Now with these images of buffers and pages in mind, let’s see how to do it by writing a procedure. We’re back at the Contents page, and I’m going to put the cursor on New Page, because we want a brand-new page. There it is, no name, just the question marks, and the first thing we have to do is give it a name. Why not call it star? Name page star, and you should see the word star appear at the top. We now have the page Star. We don’t do anything on it, we flip it. You see, we’re now on the flip side of the page Star. To make that more concrete, maybe we should leave the screen and see what it looks like on some keyboards.

                                    On the IBM keyboard, the flip stroke is control-F. Press Control, press F, release control. That gets the flip side, that gets the front side. On the Apple keyboard, the flip stroke is open-apple-F. That brought it to the flip side. That brings it the front side, that brings it back to the flip side. 

                                    Back on the screen, we’re on the flip side of the page Star ready to define our procedure. I’m going to call it To Pentagon and leave it to you to decide whether it really is one. In traditional Logo, I would start writing Repeat there, but in LogoWriter I can do something more interesting called formatting. Repeat like that, and then let’s put the first input over there, and then let’s put the next input underneath it. You don’t have to do this. You can lay it out anyway you like. LogoWriter allows you to use any formatting you like that happens to make it readable for you. I think this is very readable. To Pentagon, separated from the body of the procedure. Repeat has its two inputs, indented a little back, and underneath one another. End. Let’s flip back and see if it works. Here we write the instruction Pentagon, and it should draw one. There it did. There’s the pentagon. There’s the flip side. There’s the front side.

                                    Now let’s look at the Contents page which we get by pressing Escape. The disk is whirring. It’s back to Contents, and look there. On our Contents page is Star, and if we go down and select Star, we find it exactly as we left it. Our pentagon. Of course, the buffer for instructions is still there, and if we flip it, there’s our procedure. Escape will take us back to Contents. There’s our Star, added to the other pieces of work that we’ve accumulated.