twc/visual-modeling
5
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

fix a few typos

Browse Source
This commit is contained in:
Scott Richmond 2024-12-01 15:39:48 -05:00
parent 5f1b25d5b2
commit 32cf547efb
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ch_1_intro.md
View File

@ -1,6 +1,7 @@
# Chapter 1: Introduction
> "Skill to do comesof doing." Ralph Waldo Emerson
> "Chance favors the prepared mind." Louis Pasteur
### Who I hope you are
@ -122,12 +123,14 @@ Don't smoke and glue at the same time.
### Dialects
Unfortunately, there is not just one Logo.
While some Logos are more alike than others, most have quirks.^[Appendix A in Brian Harvey's _Computer Science Logo Style_, volume 1: _Intermediate Programming_ (Cambridge, MA: MIT Press, 1985), gives a nice summary of the syntactic differences between Logos. It gives no help with the differences in graphics, though.]
While some Logos are more alike than others, most have quirks.
I use Terrapin MacLogo throughout this book.
All the procedures have been written in this dialect using an Apple Macintosh Plus.
Most of the images were generated by Logo procedures and printed on an Apple Imagewriter II printer.
The rest were done by hand, mine.
> Appendix A in Brian Harvey's _Computer Science Logo Style_, volume 1: _Intermediate Programming_ (Cambridge, MA: MIT Press, 1985), gives a nice summary of the syntactic differences between Logos. It gives no help with the differences in graphics, though.
You may have a different machine and a different Logo.
To make life as easy as possible, and to eliminate the need to talk about dialects, I have tried hard to avoid using those components that vary most between Logos.
The bad news: this is a book about graphics and graphics is the area in which Logos differ most.
@ -435,6 +438,7 @@ We started with a list of commands that drew a box of a single size.
Next, we grouped these commands into procedures that could draw boxes of several different sizes.
Next, we generalized the `BOX` procedure with an argument so that it could draw boxes of any size.
Finally, we produced a still more general procedure, `NGON`, that can draw any regular, polygonal "box"--triangles, squares, pentagons, hexagons, and so on--of whatever size we wanted.
### Making the simple more complete
What next?
How can we make these simple polygons more interesting?