<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Stories of Apple &#187; mpw</title>
	<atom:link href="http://www.storiesofapple.net/tag/mpw/feed" rel="self" type="application/rss+xml" />
	<link>http://www.storiesofapple.net</link>
	<description>Old and new tales from Cupertino&#039;s Infinite Loop</description>
	<lastBuildDate>Tue, 07 Sep 2010 13:54:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>CLImax: yet another shell before Mac OS X</title>
		<link>http://www.storiesofapple.net/climax.html</link>
		<comments>http://www.storiesofapple.net/climax.html#comments</comments>
		<pubDate>Fri, 19 Dec 2008 10:18:57 +0000</pubDate>
		<dc:creator>Nicola D'Agostino</dc:creator>
				<category><![CDATA[Did you know that...]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[applescript]]></category>
		<category><![CDATA[mpw]]></category>
		<category><![CDATA[system7]]></category>

		<guid isPermaLink="false">http://www.storiesofapple.net/?p=112</guid>
		<description><![CDATA[<p>There are many misconceptions about the Macintosh before the arrival of Mac OS X. One of them is <strong>the absence of a shell</strong>, a command line interface. </p>
<p><a href="http://www.flickr.com/photos/nda/3120347054/" title="about CLImax by nicoladagostino, on Flickr"><img src="http://farm4.static.flickr.com/3290/3120347054_792d70d90c_m.jpg" width="240" height="153" align="right"  hspace="8" vspace="4" alt="about CLImax" /></a>Although it is true that until 2001 Apple never provided one out of the box, there have been <strong>many ways to obtain such an interface</strong>, including Apple&#8217;s own MPW package for developers and a plethora of third parts applications and utilities. Among these was an <strong>AppleScript command interface for the System 7 called <a href="http://homepage.mac.com/drewthaler/sw/CLImax1.5d2.sit">CLImax</a></strong> that was <strong>developed around 1996 by Drew Thaler</strong>.</p>
<p>Since we <a href="http://www.storiesofapple.net/discs-filesystems-and-macs-interview-with-drew-thaler.html">interviewed Drew</a> a while ago about his work for Apple we also <strong>asked him to tell us the background story</strong> about this peculiar shell for the so-called &#8220;Classic&#8221; Mac OS.<br />
<strong>Drew Thaler:</strong> I was in university at the time, and everyone in the engineering department spent a lot of time using the command-line interfaces on Unix systems. (SunOS, HP-UX, Apollo, etc.) The Mac had a few types of command-lines — MPW, MacPerl, and so on &#8211; but there was no reason to use most of them, because really the way you interacted with the Mac was through GUI apps and that&#8217;s where your data was kept.</p>
<p>But there was a text-based way to talk to the GUI applications on your Mac: AppleScript.<br />
<span id="more-112"></span></p>
<p>I wrote the AppleScript support for some of our internal applications at the university, and I also wrote AppleScripts to test them. As I did that I kept getting frustrated at how hard it was to write scripts. The syntax was English-like, but it wasn&#8217;t really English. It was easy to read and hard to write. You&#8217;d try a command and it wouldn&#8217;t quite do what you expected. Or it would fail because the application didn&#8217;t support the particular syntax you were trying. Or you&#8217;d try something that seemed natural only to find that the data you wanted wasn&#8217;t accessible via AppleScript at all. It was frustrating.</p>
<p>CLImax let you enter short, one-line script commands and see the result immediately. You didn&#8217;t need to type something long like &#8216;tell application &#8220;Finder&#8221; to get windows&#8217;. Instead you&#8217;d just tab over to the Finder as your target and type &#8220;get windows&#8221;. Hit return and it would run immediately, and you&#8217;d get the result in the right-hand side. </p>
<p><a href="http://www.flickr.com/photos/nda/3119514931/" title="CLImax window by nicoladagostino, on Flickr"><img src="http://farm4.static.flickr.com/3240/3119514931_bef4384fde.jpg" width="406" height="84" vspace="7" alt="CLImax window" /></a></p>
<p>You could also chain commands together — &#8220;count result&#8221; would count the number of windows that were returned by the previous command — and define variables and functions to use later. This made it incredibly easy to try different commands from the application&#8217;s dictionary until you found a method that worked. And because it was driven by a hotkey you could pop it up and use it at any time.</p>
<p>CLImax didn&#8217;t make AppleScript any simpler, but it made it friendlier and put it right at your fingertips. I never sold many copies, but I never really promoted it either. (At the time, shareware was distributed primarily via FTP servers like Info-Mac.)<br />
Lately I&#8217;ve been hearing from a lot of very smart people that they used and liked CLImax, which is very nice to hear! So, Stories of Apple gets a scoop here: because of all the nice feedback I&#8217;ve gotten lately, I&#8217;ve started work on a Mac OS X update of CLImax which will support many other programming languages besides AppleScript.</p>
]]></description>
			<content:encoded><![CDATA[<p>There are many misconceptions about the Macintosh before the arrival of Mac OS X. One of them is <strong>the absence of a shell</strong>, a command line interface. </p>
<p><a href="http://www.flickr.com/photos/nda/3120347054/" title="about CLImax by nicoladagostino, on Flickr"><img src="http://farm4.static.flickr.com/3290/3120347054_792d70d90c_m.jpg" width="240" height="153" align="right"  hspace="8" vspace="4" alt="about CLImax" /></a>Although it is true that until 2001 Apple never provided one out of the box, there have been <strong>many ways to obtain such an interface</strong>, including Apple&#8217;s own MPW package for developers and a plethora of third parts applications and utilities. Among these was an <strong>AppleScript command interface for the System 7 called <a href="http://homepage.mac.com/drewthaler/sw/CLImax1.5d2.sit">CLImax</a></strong> that was <strong>developed around 1996 by Drew Thaler</strong>.</p>
<p>Since we <a href="http://www.storiesofapple.net/discs-filesystems-and-macs-interview-with-drew-thaler.html">interviewed Drew</a> a while ago about his work for Apple we also <strong>asked him to tell us the background story</strong> about this peculiar shell for the so-called &#8220;Classic&#8221; Mac OS.<br />
<strong>Drew Thaler:</strong> I was in university at the time, and everyone in the engineering department spent a lot of time using the command-line interfaces on Unix systems. (SunOS, HP-UX, Apollo, etc.) The Mac had a few types of command-lines — MPW, MacPerl, and so on &#8211; but there was no reason to use most of them, because really the way you interacted with the Mac was through GUI apps and that&#8217;s where your data was kept.</p>
<p>But there was a text-based way to talk to the GUI applications on your Mac: AppleScript.<br />
<span id="more-112"></span></p>
<p>I wrote the AppleScript support for some of our internal applications at the university, and I also wrote AppleScripts to test them. As I did that I kept getting frustrated at how hard it was to write scripts. The syntax was English-like, but it wasn&#8217;t really English. It was easy to read and hard to write. You&#8217;d try a command and it wouldn&#8217;t quite do what you expected. Or it would fail because the application didn&#8217;t support the particular syntax you were trying. Or you&#8217;d try something that seemed natural only to find that the data you wanted wasn&#8217;t accessible via AppleScript at all. It was frustrating.</p>
<p>CLImax let you enter short, one-line script commands and see the result immediately. You didn&#8217;t need to type something long like &#8216;tell application &#8220;Finder&#8221; to get windows&#8217;. Instead you&#8217;d just tab over to the Finder as your target and type &#8220;get windows&#8221;. Hit return and it would run immediately, and you&#8217;d get the result in the right-hand side. </p>
<p><a href="http://www.flickr.com/photos/nda/3119514931/" title="CLImax window by nicoladagostino, on Flickr"><img src="http://farm4.static.flickr.com/3240/3119514931_bef4384fde.jpg" width="406" height="84" vspace="7" alt="CLImax window" /></a></p>
<p>You could also chain commands together — &#8220;count result&#8221; would count the number of windows that were returned by the previous command — and define variables and functions to use later. This made it incredibly easy to try different commands from the application&#8217;s dictionary until you found a method that worked. And because it was driven by a hotkey you could pop it up and use it at any time.</p>
<p>CLImax didn&#8217;t make AppleScript any simpler, but it made it friendlier and put it right at your fingertips. I never sold many copies, but I never really promoted it either. (At the time, shareware was distributed primarily via FTP servers like Info-Mac.)<br />
Lately I&#8217;ve been hearing from a lot of very smart people that they used and liked CLImax, which is very nice to hear! So, Stories of Apple gets a scoop here: because of all the nice feedback I&#8217;ve gotten lately, I&#8217;ve started work on a Mac OS X update of CLImax which will support many other programming languages besides AppleScript.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.storiesofapple.net/climax.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
