Re: LOGO-L> cloning procedures

[George Mills <mills@softronix.com>]

Your editing what ever part of THE workspace is in front of you.
If you delete what's in front of you, it's gone. If rename what's in front
of you it's renamed, if you clone (COPY and PASTE) what's in front of you
it's cloned.

I also think most people use EDALL because most work is only a few pages
of code (or they use Yehuda's trick to edit everything and maintain
a desired order). Note also, nothing is done until you exit the editor
so you can still quit the edit if you wish.

I don't think the fact that you may only edit part of the workspace changes
anything. Let's say I edit 2 procedures and decide to merge one into the
other (and the merged procedure can be the name of the first original procedure,
or the name of the second original procedure or a new procedure name).
Your done, nothing to think about, you don't have to remember to go
delete the first or the second procedure or both or even have to remember what you
even did. Why make it a 2 step process and perhaps make an error in the second step !!!

I constantly massage the names of procedures. If I had to remember separately
what the old names I had to erase later (the names I did not like in first place
because I could not remember them :-)) I'd go mad.

I ran MSWLogo the UCBLogo way for many years and I constantly had dead code
sprinkled through out. It didn't take any learning curve once I switched it.
What I often did with the UCBLogo way was EDALL, make my changes and then
do an ERALL just before I exited the editor. That's basically what MSWLogo does
now just before it loads the edited changes it erases what ever you launched
the editor with. It you edited only one procedure then only that one is deleted
just before the changes are loaded. If the procedure you started the edit with
is not in the reloaded edit it's gone.

To rename a procedure and expect the old one to still exist and the new one to
exist seems very unnatural to me. With the MSWLogo way you don't have to think about
this issue at all. You just have to learn how to "clone" a procedure. Which just so
happens to be just how you clone just about anything else on a computer (you copy it,
you don't rename it).

Brian Harvey wrote:
> 
> George Mills <mills@softronix.com> writes:
> >The difference boils down to thinking that when your in the editor as Editing
> >THE workspace as opposed to thinking your editing a COPY of the workspace.
> 
> I would believe this more if, in fact, the entire workspace showed up in the
> editor whenever you say EDIT.  (That would be more like the "flip side" model
> of LogoWriter and Microworlds.)  But since in MSWLogo (as in UCBLogo) you edit
> only a subset of the workspace, I find this argument less compelling.
> 
> ---------------------------------------------------------------
> Please post messages to the Logo forum to logo-l@gsn.org.  Mail
> questions about the list administration to logofdn@gsn.org.  To
> unsubscribe send    unsubscribe logo-l    to majordomo@gsn.org.

-- 
===============================================================
George Mills (mills@softronix.com)
http://www.softronix.com/
The www page contains some very powerful educational software.
Our single most important investment is our kids.
---------------------------------------------------------------
Please post messages to the Logo forum to logo-l@gsn.org.  Mail
questions about the list administration to logofdn@gsn.org.  To
unsubscribe send    unsubscribe logo-l    to majordomo@gsn.org.