From: mills@athena.lkg.dec.com (George Mills)
Newsgroups: comp.archives
Subject: [comp.lang.logo] MicroSoft Windows LOGO Version 3.X is ready (based on ucblogo !!)
Followup-To: comp.lang.logo
Date: 14 Dec 1992 10:19:02 GMT
Organization: University of California, Berkeley
Distribution: world
NNTP-Posting-Host: soda.berkeley.edu
Summary: Msw Logo 3.X ready
X-Original-Newsgroups: comp.lang.logo
X-Original-Date: 7 Dec 92 06:58:56 GMT

Archive-name: auto/comp.lang.logo/MicroSoft-Windows-LOGO-Version-3-X-is-ready-based-on-ucblogo


        MswLogo Version 3.X for Micro-Soft Windows 3.0,1 is ready !!!
        -------------------------------------------------------------

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!! This is a MAJOR change read these notes carefully first    !!!!
!!!! If you PUSH this onto a beginner he/she may get frustrated !!!!
!!!! and not use logo at all. It's a PROTOTYPE                  !!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

LOCATION: itrc::/millspub/mswlgo3x.zip (this is a DEC internal location)
            or
          cher.media.mit.edu on pub/comp.lang.logo/programs/mswlogo
            or
          simtel on PS:<MSDOS.LOGO> (in queue)
            or
          Send the following message to: ftpmail@decwrl.dec.com 
----cut here----
connect 18.85.0.47
binary
uuencode
chdir pub/comp.lang.logo/programs/mswlogo
get mswlgo3x.zip
quit
----cut here----

Note: There is no connection between the ftpmail server suggested here
and cher.media.mit.edu or MswLogo. It is a common service to internet
users from Digital Equipment Corporation. There are other ftpmailers
available but I don't know the addresses.

New features/bugs fixed:

   o This version of MswLogo is now based on a new "core" written
     by Brian Harvey (called ucblogo) at Berkeley. It has the same
     user interface as MswLogo 2.4 and all it's extensions (like
     Bitmaps, Multimedia, etc.).

Notes to ucblogo users:

   o Most ucblogo commands still exist but most of the "character cell"
     commands don't fit well into the windows model. For example many
     logo programs use "readchar" as buttons. Well in windows you have
     buttons so why not use buttons. I hope to have these type features
     in 3.1 +/- a minor rev. Basically a logo programmer should be able
     to create,label, and trap windows buttons. They should also be able
     to present data into a list box etc.

   o Even though "ucblogo" runs on mac and x, it is not running a true
     gui (graphics user interface). In Mswlogo (with the ucb core) you get
     a true gui. You can enable tracing while running your program, you
     can pop up a status windows that give lots of information about
     what the turtle is up to. You can be editing and testing your commands
     in logo at the same time. Online Hypertext help is also a big plus.

Notes to mswlogo users:

   o The major differences are, you have to load and save programs.
     But this is really an enhancement, since you can have many
     procedures in one program.

   o Advanced logo users will be glad to know the new core features
     tail recursion.

   o Sytax is slightly different (no ";" between commands in a list.
   
   o No repcount function :-(, a hack is in place, I fix it or remove it.

   o No goto, I may add it, if Brian Harvey doesn't kill me for even
     thinking about it.

   o performance is is ok until you take advanatage of some of the added
     ucblogo functionality which can be very compute intensive, but also
     very powerfull.

NOTE: Windows 3.0 users there is a seperate executable for 3.0
      due to the MultiMedia enhancements which 3.0 does not have.

To Install it:

Note NO environment variables (set xxx=yyy commands) needed.

1) UnZip MSWLGO3X.ZIP into a directory (e.g. c:\logo)

2) UnZip LOGOLIB.ZIP (included in MSWLGO3X.ZIP) into LOGOLIB
   (e.g. c:\logo\logolib). The library used to be optional on mswlogo
   it is required from now on.

3) UnZip EXAMPLES.ZIP (included in MSWLGO3X.ZIP) into EXAMPLES
   (e.g. c:\logo\examples). These are optional examples.

4) Copy BWCC.DLL (included in the .ZIP) to anywhere in your PATH.
   The desired place is in your root windows directory (e.g. c:\windows).

5) Start Windows and add an Icon as follows:

   a) Select the applications (or other desired) group box.

   b) Go into Program manger FILE menu and click on New.

   c) Select Program Item and click OK.

   d) Enter the command for logo (e.g. c:\logo\logo).
      Windows 3.0 users MUST use logo30 (e.g. c:\logo\logo30).
      You may also delete the .EXE you do not use here.

      This can also be where you select the size of the image (NOT the size
      window). The switches "-h number" (to select height) and "-w number" (to
      select width). The default has been and still is 1000x1000. For example
      to change to a 500x500 image (using 1/4 the amount of memory) enter:

      c:\logo\logo -h 500 -w 500

   e) Include a working directory (e.g. c:\logo\work) or you'll have logo
      files all over the place (this available only to 3.1 only). I'll try
      to come up with a better solution soon.

Start it from Windows by double clicking the Logo Icon

Start it from DOS by typing "win logo [options]" at DOS prompt (assuming
logo.exe is in your PATH).

Try typing "DEMO" in the "Input Box".

Standard features:

   o Supports Text in all available fonts and sizes.
   o Cut, Paste and strecthing bitmaps.
   o Zoom.
   o Tail recursion.
   o User error handling.
   o "Standard" Logo parsing.
   o Floodfill.
   o Save and restore images in .BMP format.
   o 16.7 million pen and background colors (using windows dithering).
   o Supports color palette (256 solid colors).
   o Standard Windows Hypertext Help.
   o Standard Windows Printing.
   o Supports separate library and work area.

Recommended usage:

   o If your a ucblogo user and waiting for a windows version.
     Use it now, I think you'll like it.

   o If your a former mswlogo user and you, your child or students
     are happy with their progress and usefullness on mswlogo 2.4
     then stick with it for now. Once you've reached some of mswlogo 2.4's
     weaknesses (like limits in recursion, large programs hard to manage
     etc. then you may want to give it a try now). 

Bugs / Basic Missing features:

   o Real mode is not supported.
   o Printing on (very few) printers still doesn't work.
   o Need arrow-key command recall.
   o Character cell operations missing, setcursor etc.
   o Cross refernces in help.
   o Online help that a younger user can understand.
   o User controlled buttons and dialog boxes.
   o Bugs you find.

   o If a bug is really bugging you or feature you really want to see done,
     say so, by sending me email. This will help me determine what's important.
     No promises, but it will help. I love any feedback good or bad.

Reporting bugs:

   Report bugs to George Mills (mills@athena.lkg.dec.com). I do have
   an account on compuserve but I do not regularly login so reporting
   bugs there will get unpredictable acknowlegment.

   You can also report bugs to Brian Harvey (bh@anarres.cs.berkeley.edu)
   if you think it's the core (or a possibility of the core). If you know
   it's related to the enhanced functions or the Windows front-end Brian
   probably won't care to know about it.

Sources:
 
   I hope to release sources by version 3.0 or 3.1.

Trouble shooting:

   o Logo accesses the disk everytime it draws a square in the DEMO
     (part 3). This is related to your buffers command in config.sys
     buffers=20 or more is typical for a "windows environment". 

   o Logo seems to run extremly slow and the disk is always thrashing.
     Your probably paging. You may be running with 256 color driver
     with out the memory to support it. Try 16 color mode or reduce the
     image size (or both).

   o Loading in an .BMP does not seem to have the right colors.
     If you had been using logo for a while you probably have used up
     part of the color palette. It's not a bad idea to clear the palette
     before loading in a .BMP.

Wish list:

   o Sound generation.
   o Clipboard support.
   o Multiple Turtles.

Public domain Logo's (on IBMPCs):

LADYBUG - Simple cute (barely logo) program. The thing that is impressive
          is how the author added music (using the PC speaker). CGA-DOS.
          NO support.

DOSLOGO - Based on Lincoln Subury Regional High School and Boston Childrens
          Museum (Brian Harvey was involved with the enhancements that the
          High school added). It was running on Unix and VMS (and others)
          when I ported to DOS a in 1990. I did not release it to
          Outside of DEC until MSWLOGO. It runs fairly well be has some
          Architectural problems (non "standard parsing", no tail recursion,
          limit of one routine per file). Poor user interface. NO support.

MSWLOGO24 or older - Based on DOSLOGO. Many graphical extentions a nice user
          interface but still has the same problems as DOSLOGO. NO support.

UCBLOGO - Brian harvey at Berkely started over with this project and is
          a Decent core. But again under DOS has a weak user interface.
          Supported. Best public Domain for DOS.

MSWLOGO3X or newer - Based on UCBLOGO and MSWLOGO24 (the best of Both)
          Good user interface and good core. Supported. Best public Domain
          for Windows (that I know of at this time).