Tyvm. I will try this imediately. When (If, but most likely I will) make
something worth telling people about, I shall tell you right after I
tell my friend who codes Java. And thank you for not telling me to go
and write hello world! thousands of times. And if there is ever a time
when I do make a good game that people would pay to play, or pay to get
exclusive features or something like that, you will get everything free.
Course that won't be for awhile.
Hello Joe,
I wrote this email to your personal address with a CC to ruby-talk
(just because I felt proud of how polite and helpful my message was
), hoping that you'd read it from your personal email and reply
directly to me, thus keeping the discussion off-list.
I'd appreciate it if you would, from now on, do that, since I hate
spamming the ruby-talk list with discussions unrelated to ruby or it's
ecosystem.
I'm VERY glad to hear how much fun you're having with Logo (gives me a
warm fuzzy feeling).
I think UCBLogo comes with a manual, but if it doesn't, here is the
online version:
http://www.cs.berkeley.edu/~bh/usermanual
quote:
CLEARSCREEN
CS
erases the graphics window and sends the turtle to its initial
position and heading. Like HOME and CLEAN together.
I see you found Brian Harvey's site at
http://www.cs.berkeley.edu/~bh/
It is very helpful.
My MMORTS was frozen the moment I got a job (a few weeks after I
started working on it), so there's nothing to see yet (the tiles for
the background were almost working and that's about it). If I'd ever
complete it, it'd be set in a 2D world and the graphics would be
skinnable. So I could play a pirates RTS while you, the one fighting
me, would be playing something akin to Warcraft 1, seeing my units as
orcs. The design is VERY VERY cool. But no time for that now.
One last thing: Don't be pissed at the ruby mailing list folks. They
were very nice and helpful (and most of them remained that way even
after you started dissing them). They each gave you very good tips and
directions on how to learn Ruby and programming, referring you to free
books that they liked, etc'. It's just that EACH of them told you to
start with writing "Hello world" once and there were so many helpful
guys there that you were told that over and over
. It was all a huge
miscommunication. Later on, you'll learn ruby and use the list and
discover what a nice bunch they are. Seriously, never seen a kinder
mailing list in my life. They have a rule, MINASWAN: Matz (creator of
ruby) Is Nice And So We Are Nice. Never seen a community that follows
a good example of kindness as a rule
besides these guys. I directed
you to logo because I saw that you don't enjoy the text games at the
beggining of most programming text. Logo was designed to be more fun
to play with at the very beggining (I studied logo at third grade and
the whole year we did nothing but draw geometric shapes. It sucked
If they'd had teached us looping, THEN we could have created the
really good stuff
). I sent you to that simple tutorial first
because the BH book begins with a "Hello world":
repeat 50 [setcursor list random 75 random 20 type "Hi]
boooooring (albeit a bit less),
But don't read that "logo for kids" text you found - once you know
turtle graphics and can play with any idea you get, you are ready to
HAVE FUN LEARNING computer science and good programming from the three
Brian Harvey books. Don't waste time, do that
Aur
P.S. the first page of the Logo book has info on how to save:
quote:
Saving Your Work
If you do write a collection of quiz procedures, you'll want to save
them so that they'll still be available the next time you use Logo.
Certainly you'll want to save the work you do in later chapters. You
can ask Logo to record all of the definitions you've made as a
workspace file using the save command. For example, if you enter the
instruction
save "mystuff
you are asking Logo to write a disk file called mystuff containing
everything you've defined. (The next time you use Logo, you can get
back your definitions with the load command.)
Don't get confused about the difference between a procedure name and a
workspace name. Logo beginners sometimes think that save saves only a
single procedure, the one whose name you tell it (in this example, a
procedure named mystuff). But the workspace file named mystuff will
actually contain all the procedures you've defined. In fact, you
probably don't have a procedure named mystuff.
The format for the name of a disk file will depend on the kind of
computer you're using, whether you're writing to a hard disk or a
floppy disk, and so on. Just use whatever file name format your system
requires in other programs, preceded by the quotation mark that tells
Logo you're providing a word as the input to the save command.
unquote
An additional way would be to write all your code in a file and start
the logo interpreter with the name of that file. From the manual:
Then, under Unix, DOS, or Windows, if you include one or more filenames on the
command line when starting Logo, those files will be loaded before the
interpreter starts reading commands from your terminal.
So you should start logo from a command line (Start->Run cmd [Enter]
cd c:\directory\where\ucblogo\is\ [Enter] ucblogo
name-of-file-with-code)
