<div id="popup_box_thanks" style="display:none" onClick="close_popup_thanks('popup_box_thanks', 'ts')"><br>Thanks for submitting your tip! All submissions are moderated by an editor before appearing online. We've reset the form so you can enter another tip. Or you can close the tip submission box. <div class="x_close" id="thanks_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('popup_box_thanks', 'ts'); return true;">Close</a></div></div>
<div class="tbf_row"><div class="tbf_wide_extra_top not_bold">Please submit only technical tips that will help other TidBITS readers better use their Macs, iPhones, and related software and hardware. All product announcements should be sent to <a href="mailto:releases@tidbits.com">releases@tidbits.com</a>.</div></div>
<div class="tbf_left">URL</div><div class="tbf_right"><input type="text" value="" name="tip_link_url" tabindex="3"><span class="tip_description"><br>Enter the URL to a Web page that supports your tip.</span></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_left">Linked text</div><div class="tbf_right"><input type="text" value="" name="tip_link_label" tabindex="4"><span class="tip_description"><br>Enter the name of the page linked above.</span></div>
<div class="tbf_wide"><input type="submit" value="Preview Your Tip" name="preview_tip" onClick="fill_preview('tipbits_enclosure_preview', 'ts', this.form); return false;" tabindex="7"> <input type="submit" value="Send Us Your Tip!" name="submit_this_tip" onClick="handle_tip_submission('ts', '', this.form, 'tip'); return false;" tabindex="8"></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_wide"><span class="fine_print">When you submit a tip, you give us permission to use it. Read <a href="javascript:void(0)" onClick="generic_show_hide('tip_terms')">our terms</a> for more details. All submissions are reviewed before publication.</span></div>
<div class="tbf_wide"><span class="fine_print">Our terms: By submitting a tip, you agree to assign TidBITS Publishing Inc., a non-exclusive, worldwide, perpetual license to reproduce, publish, and distribute your tip in connection with the TidBITS Web site and associated products in any media. You agree that you created the content you submitted, and that you have the right to assign us this license. You give us permission to use your name, but your email address won't be publicly displayed or shared. We review all submissions before publication, and reserve the right to select which submissions we feel are appropriate for our readers and to edit those we publish.</span></div>
<div id="comment_thanks" style="display:none" onClick="close_popup_thanks('comment_thanks', 'comm')"><br>Thanks for submitting a comment! Please check your email for a link that, when clicked, will verify that you're a real person and cause your comment to appear immediately. <div class="x_close" id="comment_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('comment_thanks', 'comm'); return true;">Close</a></div></div>
<div class="tbf_wide"><span class="fine_print">Our terms: We reserve the right to edit or delete any comment, so please post thoughtfully. We use your email address <i>only</i> to send you a one-time verification message confirming that you posted this comment. We also store your address to allow you to verify using other Web browsers in the future. For more info, see our <a href="http://db.tidbits.com/privacy.html">privacy policy</a>.</span></div>
<li><a href="/feeds/tidbits.rss" title="Subscribe via RSS" class="gettb">RSS <img src="/images/feed-icon-12x12.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe via RSS"></a></li>
<li><a href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=276986548" title="Subscribe to the podcast" class="gettb">Podcast <img src="/images/feed-icon-12x12_podcast.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe to the postcast"></a></li>
<li><a href="http://www.twitter.com/TidBITS" title="Get Article Updates via Twitter" class="gettb">Twitter <img src="/images/feed_icon_12x12_twitter.png" width="12" height="12" border="0" class="nav_img" alt="Get Article Updates via Twitter"></a></li>
<li><a href="http://www.facebook.com/pages/TidBITS/195314925519" title="Go to the TidBITS Page at Facebook" class="gettb">Facebook <img src="/images/feed_icon_12x12_facebook.gif" width="12" height="12" border="0" class="nav_img" alt="Go to the TidBITS Page at Facebook"></a></li>
<li><a href="javascript:void(0)" title="Sections" class="tabhead" onClick="return showhide('articleslist')">Sections <span id="articleslist_triangle"><img src="/images/nav_triangle_open.gif" width="9" height="9" border="0" class="navtriangle" id="articleslist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('stafflist')" title="Staff" class="tabhead">Staff <span id="stafflist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="stafflist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" title="Issues" class="tabhead" onClick="return showhide('issuelist')">Weekly Issues <span id="issuelist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="issuelist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('abouttidbits')" title="About TidBITS" class="tabhead">About TidBITS <span id="abouttidbits_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="abouttidbits_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<div class="center_top">Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling <a href="http://www.takecontrolbooks.com/?pt=TB-TAGLINE" style="color:yellow">Take Control</a> ebooks.</div>
<!-- begin centercolumn -->
<div id="centercolumn">
<!-- begin rightcolumn_container -->
<div id="rightcolumn_container">
<!-- begin rightcolumn -->
<!-- rightcolumn is embedded within centercolumn so featured text wraps around it -->
</div><!-- end tearoffbox_wide_container for watchlist items -->
<!-- begin tearoff box wide -->
<div class="tearoffbox_wide_container">
<div class="tearoffbox_wide_tips">
<div class="tip_display">
<div class="tips_sponsor_logo">
</div>
<h6>Find Text Leading from Acrobat PDF</h6>
<p><p>Ever have to recreate a document from an Acrobat PDF? You can find out most everything about the text by using the Object Inspector, except the leading. Well, here's a cheesy way to figure it out. Open the PDF in Illustrator (you just need one page). Release any and all clipping masks. Draw a guide at the baseline of the first line of text, and one on the line below. Now, Option-drag the first line to make a copy, and position it exactly next to the original first line at baseline. Then put a return anywhere in the copied line. Now adjust leading of the copied lines, so that the second line of copy rests on the baseline of the second line of the original. Now you know your leading.</p><p>Or you could buy expensive software to find the leading. Your choice.</p></p>
<p>Visit <a href="http://macproductionartist.wordpress.com">Mac Production Artist Tips and Scripts</a></p>
</div>
<div class="tearoffbox_wide_bottom_tips">
<div style="padding-bottom:35px"><div class="tip_display" style="float:left"><p><br><a href="/tipbits/172">Link to this tip</a></p></div><div class="tip_display" style="float:right; width:150px">
<div class="tbf_wide_80" id="hc_rc_3887">To help us avoid automated posts and misuse of our site, please enter the words below.</div><div class="x_close_row" id="hc_upper_right2_3887"><a href="javascript:void(0)" onmousedown="HidePopupContent('hc_3887', 'hc', '3887'); return true;">Close</a></div>
<div class="featured_meta"><div class="meta_article">14 Dec 1998 | <a href="/article/5210?print_version=1">Print <span class="shift_up"><img src="/images/printer_icon.gif" alt="Printer-Friendly Version of This Article" border="0" width="9" height="10"></span></a></div></div>
<H2>Douglas Engelbart: More Thoughts from Cassandra</H2>
<div id="article_box_3887"><P>While at the 1998 Association for Computing Machinery (ACM) Conference on Computer Supported Cooperative Work a few weeks ago here in Seattle, I had the opportunity to attend Douglas Engelbart's Turing Award Lecture. I was struck by how closely our computing today mirrors Engelbart's demonstrations in the late 1960s and at how seriously we have missed the major thrust of his goals.</P><P><<A HREF="http://www.acm.org/sigchi/cscw98/">http://www.acm.org/sigchi/cscw98/</A>></P><P><STRONG>Who Is Douglas Engelbart?</STRONG> Douglas Engelbart is best known for inventing the mouse, but he's done much more than that. We tend to credit Apple for the graphical interface popularized by the Macintosh, although many also spread the credit to Xerox PARC for inspiring Steve Jobs and others from Apple. Fewer people realize that much of what Xerox showed Apple - a mouse-driven, graphical windowing system - was part of Engelbart's pioneering work from more than ten years before. In the late 1960s, while working at SRI (now a non-profit research organization, then the Stanford Research Institute), Engelbart and his lab came up with NLS (oNLine System), which was first demonstrated at the 1968 Fall Joint Computer Conference. After Engelbart left SRI, many of the people on his team went to Xerox PARC to carry on the work they'd started with Engelbart.</P><P><<A HREF="http://www.bootstrap.org/dce-bio.htm">http://www.bootstrap.org/dce-bio.htm</A>></P><P>The presenter who introduced Engelbart's lecture played 6 minutes of the original 90-minute NLS presentation, showing such firsts as the mouse, multiple windows, 2-dimensional display editing, hypertext, shared-screen collaboration, videoconferencing, and integrated hypermedia email. Other firsts for Engelbart include in-file object addressing and linking, outline processing, cross-file editing, hypermedia publishing, and context-sensitive help.</P><P>Engelbart saw his many ideas and inventions as technical ends to a goal that also required progress in media, language, customs, knowledge, skills, and procedures. Back in the 1950s, Engelbart realized that the rate of change in the world was increasing radically, and the complexity and urgency of the world's problems were increasing along the same lines. On a purely elemental level, he felt that the survival of the human race hinged on our ability to improve - to evolve if you will - at a rate sufficient to keep up. Since biological evolution works on a long time frame, the evolution in question would have to come with the tools we invent and use, the customs and communities we form, and the ways in which we work together.</P><P>The man doesn't think small, and neither should we.</P><P><STRONG>What Are We Missing?</STRONG> There's no question that the technical ideas Douglas Englebart showed back in 1968 are finally becoming commonplace. Watching that 1968 demonstration was a bit depressing, since I couldn't help but wonder why it took the industry 30 years to achieve on a large scale what Englebart had shown on a small scale. There's no question that technology had some catching up to do - for instance, his lab had to build its own CRT display to support NLS, at a cost of $80,000 in 1968 dollars.</P><P>It's easy to think that Engelbart's work led directly to the development of easy-to-use, single-user systems like the Macintosh. But, at least as the Macintosh existed in the early days, it was almost antithetical to some of Engelbart's core ideas. First, single-user, isolated systems did not lend themselves to collaboration. Engelbart's lab was the second site on the ARPANET, and he was thrilled with the idea of using networked computers to foster cooperation and collaboration. Second, the mantra of the Macintosh was ease-of-use, and although no one, including Engelbart, would argue that systems should be unnecessarily hard, I don't believe he's a fan of simplicity for simplicity's sake.</P><P>The thrust of Englebart's work is directed toward augmenting the human intellect, not popularizing computer technology. He feared that as technology improved at a rate far surpassing improvements in non-technical fields, we would use it to <EM>automate</EM> intellect, rather than <EM>augment</EM> it. In short, merely automating simple tasks, though useful, doesn't lend itself to collaboration and solving the big problems.</P><P>Engelbart suggested that we think for a moment about bicycles - they're truly odd devices, requiring incredible balancing and coordination skills to ride. No one is born knowing how to ride a bicycle. We start with tricycles that let us practice some of the necessary skills without worrying about balance. Then we graduate to normal bikes with training wheels, and finally to real bicycles. Millions of people rely on bicycles for transportation, and bicycle racers perform astonishing feats on them.</P><P>But learning to ride a bike is hard, and even after we've learned, it's a dicey business fraught with potholes, dogs, cars, and even mere inattention, any of which can cause a loss of balance. Wouldn't it seem to be easier to stick with tricycles? Sure, a few tricycles are made for adults, but for most of us a two-wheeled bicycle is enough better, faster, and smaller that it's worth the learning curve.</P><P>We put an incredible amount of effort and mental energy into making software and hardware easier to use, and that's a worthwhile goal. But, just as a vast amount of development goes into making bicycles faster and more capable (think clipless pedals, shocks on mountain bikes, and aerodynamic handlebars that make bikes more efficient, if harder to ride), shouldn't we also concentrate on augmenting the capabilities of sophisticated computer users? And, shouldn't we attempt to create a learning situation where users can graduate from a simple system to a more complex one, rather than trying to serve everyone's needs in a single system? Microsoft tried that with Word 4.0's short menus (which hid more advanced features until you switched to full menus). Short menus flopped because users hated being told they were too dumb to handle full menus, it was too hard to figure out how to switch into full menus, and commands for some basic tasks were available only on the full menus. Microsoft abandoned short menus quickly, and in so doing, perhaps threw the baby out with the virtual bath water.</P><P>One interesting gap in the realization of Engelbart's research is the chord keyboard. He never meant the mouse to be used with a normal keyboard, for the obvious reason that you can't type and mouse at the same time, thus limiting your ability to enter and manipulate different types of information. His intention was that you'd use a chord keyboard with one hand and a mouse with the other. I suspect that heavy text entry environments would be more likely to have a pair of chord keyboards so you could double your speed when typing, then push one out of the way for access to the mouse for editing. Chord keyboards never caught on, despite their utility because they require learning. It's not hard, but it's a lot harder than the less-efficient keyboard most of us use. You can still buy chord keyboards from Infogrip - I know a few people who use them, mostly because of hand problems.</P><P><<A HREF="http://www.infogrip.com/">http://www.infogrip.com/</A>></P><P><STRONG>Human/Organizational Aspects</STRONG> -- We've not only missed a few of the technical aspects of Douglas Engelbart's vision, we've also missed many of the non-technical aspects. Engelbart believes our tools and non-technical features such as language, customs, skills, and so on evolve together slowly over time. For instance, consider the skills required to drive on a crowded freeway, a situation that didn't exist 100 years ago. As our technology has improved, so have our coordination and awareness skills. But, technologies can improve much faster than our skills (many can drive cars, but few can fly helicopters), and we often experience social conflict when cultural customs run counter to technological advances, such as birth control pills and nuclear weapons.</P><P>Engelbart's solution for this conundrum is concentration on so-called "improvement activities." In his view, organizations and groups of all kinds have (or should have) three basic activities, as follows:</P><UL><LI>A activities which serve the customer or end user<LI>B activities which improve the product cycle and A activities in general<LI>C activities which improve quality and reduce the time of the B improvement cycle</UL><P>In essence, A serves the customer, B tries to help A do an increasingly better job, and C in turn attempts to improve the work done by B.</P><P>Unfortunately, the marketplace is a lousy environment to foster exploration into improvement. Most companies focus almost all their attention on A, with a little on B, and almost none on C. The most interesting example of this that I've seen is that companies that produce productivity tools seldom use them any more efficiently or productively than the general public. At Microsoft, for instance, the description - indeed, the philosophy - of being forced to use specific Microsoft products is "eating our own dog food." It's not a pretty image.</P><P>Wouldn't you think a large software company would try to knock off two birds with one stone by creating products that radically improve the productivity of its own employees, with the understanding that doing so would result in products that would better meet the needs of other customers? Yet it seems uncommon for large companies to consider the needs or desires of their employees as in any way typical of the needs and desires of their customers. As a result, these companies tend to ignore the feedback that is both closest and easiest to collect.</P><P>The other obvious obstacle for Engelbart's organizational solution in a capitalistic society is that companies see no reason to work together, even when collaboration would benefit both. People engaged in C-level activities must instead form their own communities to share ideas for improving the improvement process, without direct responsibility to a company's competitive situation (because competition inherently stands in the way of cooperation). Frankly, getting past financial navel-gazing is difficult for many companies, though a number of large and well-known organizations have joined Engelbart's Bootstrap Alliance, which is dedicated to exploring the development of organizations that can maneuver successfully into the increasingly complex future. Members include the likes of Sun Microsystems, ETS (Educational Testing Service), NTT, U.S. General Services Administration, the CIA, IBM, Hewlett-Packard, and the National Science Foundation.</P><P><<A HREF="http://www.bootstrap.org/alliance/">http://www.bootstrap.org/alliance/</A>></P><P><STRONG>Will Douglas Englebart Succeed?</STRONG> Listening to Engelbart in person is persuasive, undoubtedly much more so than my retelling. He's one of those speakers whom you listen to, thinking, "He's right. He's completely right." But history is full of people who have been right. In fact, my final question to Engelbart after his talk was, "Do you feel like Cassandra?" to which he replied with a small laugh and a soft "Sometimes." (In Greek legend, Apollo cursed Cassandra with the ability to foretell the future, but nobody would believe her.)</P><P>Look at it this way: Engelbart's statement of the problem we face, that the rate of change in the world is constantly increasing, is hard to dispute. It's something I've worried about for some years now as well, mostly because I fear that our individual abilities to deal with this constant change are breaking down. Despite my side interests in communities and a long history of observing and working with Internet groups, I never made the conceptual leap Engelbart did, that the only solution is to develop systems for continually improving our collective ability to handle change.</P><P>Put another way, the cascade reaction of change travels with the electronic winds. A change anywhere in the world can encourage some other change elsewhere in the world. Although we're agents of change, we're already losing the capacity to deal with changes we've fostered. Just look at the calls to return to "traditional values" and the popularity of nostalgia movements. Whatever your opinion of these movements, their mere existence shows our discomfort with the ways we have changed society. But you can neither force nor coax the genie back into the bottle.</P><P>So, let's agree with Engelbart's statement of the problem. There's also no denying that his technical vision was on target. Perhaps we never ended up using those chord keyboards, but Engelbart's track record is unsurpassed. It may have taken 30 years, but he's been proven right in the technical field.</P><P>We're left then with his ideas about fostering improvement activities. They may be difficult to accept, especially for competitive companies that can't see beyond the next quarterly report. Without trying these ideas though, will we be able to keep up with the changes we've set in motion? It's as though we keep walking further out into the ocean only to be knocked down by ever-larger waves of change, knowing full well the waters will soon close over our heads. Perhaps we should instead focus on building a boat, even if that means going back to shore for a little while. We must learn to ride on top of the waves.</P><P>Almost exactly five years ago, I attended another conference in Seattle - Hypertext '93 - where I heard an address by Ted Nelson, the father of hypertext. I noted with some sadness in "Xanadu Light" in <A HREF="http://www.tidbits.com/tb-issues/TidBITS-204.html">TidBITS-204</A> that Nelson was treated with "a complicated mix of awe and devotion combined with an almost cruel pity and ridicule" because of failing to ship a product.</P><P><<A HREF="http://db.tidbits.com/article/02326">http://db.tidbits.com/article/02326</A>></P><P>Well, Douglas Engelbart has not only shipped a product, he shipped an entire computing paradigm, so I say we give his non-technical ideas a chance. I just hope we have another 30 years for them to catch on. In the meantime, you can read more about Douglas Engelbart and his ideas at the Bootstrap Institute Web site.</P><P><<A HREF="http://www.bootstrap.org/">http://www.bootstrap.org/</A>></P><!-- Douglas Engelbart: More Thoughts from Cassandra Adam C. Engst --></div>
<!-- end article text -->
<!-- PayBITS -->
<p> </p><div class="sponsorbox">
<div class="sponsortext"><A HREF="http://nuance.com/dragon/mac"><IMG SRC="http://db.tidbits.com/images/badges/dragondictatelockup_vertical_onlight.png" ALT="" HEIGHT="50" WIDTH="50" BORDER="0" ALIGN="left"></A>Dragon speech recognition software for Macintosh, iPhone, and iPad!<br />Get the all-new Dragon Dictate for Mac from Nuance Communications<br />and experience Simply Smarter Speech Recognition.<br />Learn more about Dragon Dictate: <<a href="http://nuance.com/dragon/mac">http://nuance.com/dragon/mac</a>></div>