MSWLogo retained the UCBLogo base, but added new commands that took advantage of features unique to Microsoft Windows. This became the standard Logo for Windows. To understand what an accomplishment UCBLogo and MSWLogo were, it's worth considering what the world of personal computing was like in 1993. Download mswlogo for windows 10 for free. Development Tools downloads - MSWLogo by Softronics, Inc and many more programs are available for instant and free download. MSWLogo is an implementation of Logo with multimedia enhancements. Runs on Windows with a GUI interface and extensions. Elicia (Logo Implementation) Elicia is a Logo implementation that allows 3D animation of user-programmable objects. It requires Windows XP. TinyLogo - Logo Programming Environment. MSWLogo - An Educational programming language that brings the power of Windows and Logo together, now supports 3 dimensional geometry. This language will never cease in amazing you! Combined with the Great Logo Adventure Book by Jim Muller, it's hard to beat. Download MSWLogo From: Download Link #1. Development Plan. There is a lot of work to do on FMSLogo. The code base lay in atrophy for five years before I picked it up. It will take a lot of work just to bring it up to date, even without making any major updates in functionality.
'david_costanzo' <Use-Author-Address-Header@[127.1]> writes:
>Internationalization is a big request (MSWLogo was not written with
>i18n in mind).
How To Mswlogo For Mac Os
I think Daniel is asking only for 8-bit-language internationalization, not
Unicode. UCBLogo has a (kludgy) internationalization scheme that could be
used pretty easily by MSWLogo.
> I was thinking that I'd first port MSWLogo to a free
>GUI toolkit, then try to get some help on it.
You might want to wait until fall, when I expect to release the wxWidgets-
based UCBLogo GUI. But it isn't as GUIish as the MSWLogo -- it has a menu
bar, for example, but not those big buttons in the lower right. OTOH it
lets you type instructions into a real text window, not that one-line thing.
>As for dropping in UCBLogo's engine, I'll take a look at that, because
>I definately want to remain consistent with advances in the Logo
>standard. Hopefully, it'll just be a drop-in replacement.
MSWLogo already uses the UCBLogo engine; it's just a question of updating
to the current version. (There will be a 5.5 this summer, soon I hope; you
might want to wait for that. It won't be amazingly different from earlier
versions except that it has mouse support, but it will have some bugs fixed.)
Mswlogo For Pc
>> I would also be nice if we could paste more than one line directly
>> into the Command window.
>
>Yes, that's been annoying for me, too. I'll look into that today.
Using the wxWidgets version would fix that.
On the other hand, I believe MSWLogo reads keyboard input differently from
UCBLogo; I think it's event-driven, the way Windows applications are
supposed to be. The wxWidgets UCBLogo has a separate (event-driven) thread
that handles I/O, and buffers characters for the Logo thread.
Seymour Papert (and others) designed the Logo language to be powerful enough for computer research, but simple enough so that it could be enjoyed by children. Papert used Logo to conduct Artificial Intelligence and Robotics research at the Massachusetts Institute of Technology. One of the robots that Logo controlled had a dome-shaped protective casing over its electronics that made it resemble a turtle. As personal computers became more affordable, the physical turtle was replaced by a virtual turtle on a computer screen. The virtual turtle was given a pen to help it fit into the familiar world of childhood learning. Drawing is already a natural part of childhood, but drawing with Logo is different than drawing with crayons. To draw with Logo, you must learn to think about drawing, enough so that you can teach a complete idiot (the turtle) how to draw.
Throughout the 1980s, as computers became more affordable, Logo was integrated into the curriculum of many schools. This led to a proliferation of different Logo software packages, each sharing the core spirit of Logo, but designed for specific computers.
In the early 1990s, a lecturer at UC Berkeley name Brian Harvey, wanted to write a computer science textbook for non-professional programmers. He selected Logo as the language for his textbook. At this time, there were many Logo environments, each with their own incompatibilities, some of which were no longer available for purchase. To overcome the incompatibilities between different versions of Logo, Harvey created a new version of Logo and ported it to every popular computer of the time. He named it UCBLogo and based his textbook on it. UCBLogo was written 1993 and given away free-of-charge.
Shortly thereafter, a like-minded Englishman named George Mills was inspired by UCBLogo. He ported UCBLogo to a C++ toolkit from Borland that ran on Microsoft Windows, thereby creating MSWLogo (short for 'Microsoft Windows Logo'). MSWLogo retained the UCBLogo base, but added new commands that took advantage of features unique to Microsoft Windows. This became the standard Logo for Windows.
To understand what an accomplishment UCBLogo and MSWLogo were, it's worth considering what the world of personal computing was like in 1993. If home users had any Internet connection at all, it was dial-up at 14.4 Kbps and they were charged by the minute. HTTP was not yet a standard. The fastest Intel CPU was the Pentium running at 66 Mhz. Manufacturers added a 'turbo mode' button that would slow down the Pentium so that software written for older CPUs would function properly. Windows 95 had not yet been released and the personal computer market was dominated by IBM clones that ran DOS or Windows 3.1. In the operating systems of the time, all memory was shared by all programs and a bug in one could crash your entire computer. Most video cards only supported a limited number of colors: some couldn't even show 256 colors. Programmers were accustomed to writing software for a specific computers and throwing it away when the computer became obsolete.
Mswlogo For Pc
>> I would also be nice if we could paste more than one line directly
>> into the Command window.
>
>Yes, that's been annoying for me, too. I'll look into that today.
Using the wxWidgets version would fix that.
On the other hand, I believe MSWLogo reads keyboard input differently from
UCBLogo; I think it's event-driven, the way Windows applications are
supposed to be. The wxWidgets UCBLogo has a separate (event-driven) thread
that handles I/O, and buffers characters for the Logo thread.
Seymour Papert (and others) designed the Logo language to be powerful enough for computer research, but simple enough so that it could be enjoyed by children. Papert used Logo to conduct Artificial Intelligence and Robotics research at the Massachusetts Institute of Technology. One of the robots that Logo controlled had a dome-shaped protective casing over its electronics that made it resemble a turtle. As personal computers became more affordable, the physical turtle was replaced by a virtual turtle on a computer screen. The virtual turtle was given a pen to help it fit into the familiar world of childhood learning. Drawing is already a natural part of childhood, but drawing with Logo is different than drawing with crayons. To draw with Logo, you must learn to think about drawing, enough so that you can teach a complete idiot (the turtle) how to draw.
Throughout the 1980s, as computers became more affordable, Logo was integrated into the curriculum of many schools. This led to a proliferation of different Logo software packages, each sharing the core spirit of Logo, but designed for specific computers.
In the early 1990s, a lecturer at UC Berkeley name Brian Harvey, wanted to write a computer science textbook for non-professional programmers. He selected Logo as the language for his textbook. At this time, there were many Logo environments, each with their own incompatibilities, some of which were no longer available for purchase. To overcome the incompatibilities between different versions of Logo, Harvey created a new version of Logo and ported it to every popular computer of the time. He named it UCBLogo and based his textbook on it. UCBLogo was written 1993 and given away free-of-charge.
Shortly thereafter, a like-minded Englishman named George Mills was inspired by UCBLogo. He ported UCBLogo to a C++ toolkit from Borland that ran on Microsoft Windows, thereby creating MSWLogo (short for 'Microsoft Windows Logo'). MSWLogo retained the UCBLogo base, but added new commands that took advantage of features unique to Microsoft Windows. This became the standard Logo for Windows.
To understand what an accomplishment UCBLogo and MSWLogo were, it's worth considering what the world of personal computing was like in 1993. If home users had any Internet connection at all, it was dial-up at 14.4 Kbps and they were charged by the minute. HTTP was not yet a standard. The fastest Intel CPU was the Pentium running at 66 Mhz. Manufacturers added a 'turbo mode' button that would slow down the Pentium so that software written for older CPUs would function properly. Windows 95 had not yet been released and the personal computer market was dominated by IBM clones that ran DOS or Windows 3.1. In the operating systems of the time, all memory was shared by all programs and a bug in one could crash your entire computer. Most video cards only supported a limited number of colors: some couldn't even show 256 colors. Programmers were accustomed to writing software for a specific computers and throwing it away when the computer became obsolete.
How To Mswlogo For Mac Windows 7
In 2004, I was looking to start a computer workshop with Jim Foster at the Boys and Girls Club in Bellevue, Washington. I picked Logo, which led to MSWLogo, since all of the machines in their computer lab ran Windows 98. I made a few small enhancements to MSWLogo to improve the workflow in my workshop and sent them to George Mills for integration into the next version of MSWLogo. By that time, he no longer had time to work on MSWLogo, so I created my own version. Soon afterward, I got a job at Microsoft and I asked the legal department if it was okay to continue working on MSWLogo. They said there was no conflict of interest, but I couldn't call it 'Microsoft Windows Logo', as that made it sound like it was created by Microsoft, which was trademark infringement. As I looked for a new name, George Mills, whose loved ones had recently contracted Multiple Sclerosis, said that he wanted to keep 'MS' in the name. So began the 'FMS' prefix, which stands for 'Fight Multiple Sclerosis'.