================================================================== pub/Smalltalk/st80_r41/Controller-poll_BugFix.st ================================================================== '' NAME Controller-poll_BugFix.st AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION Fixes a race condition in Controller under R4.1 ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 1 VERSION DATE August 22nd, 1992 SUMMARY Date: Sat, 22 Aug 1992 13:55:07 -0500 From: Bill Voss To: support@parcplace.com Subject: BugReport (and fix) Under ParcRanger at the University of Illinois in Urbana/Champaign. Smalltalk version Objectworks\Smalltalk(R), Release 4.1 of 15 April 1992 ChangeSet patches OrderedCollection () Running on a SUN SparcStation 2 running SUNOS 4.1.2 under OW 3 using tvtwm. I found a race condition. My code invokes DialogView confirm:initialAnswer: in a process running at lowIOPriority. When I pressed-then-released the mouse button instead of rapidly clicking the mouse button I usually got the notifier. Unhandled exception: Message not understood: #isInTransition: copy stack UndefinedObject(Object)>>doesNotUnderstand: [] optimized WidgetController>>controlLoopBody WidgetController>>controlLoop WidgetController(Controller)>>startUp ActionButton(VisualPart)>>startUp DialogController(Controller)>>controlToNextLevel DialogController>>controlActivity DialogController(Controller)>>controlLoop The optimized [] is from WidgetController beTriggerOnUp. The problem there is that view is undefined. I eventually found that in WidgetController>>controlLoopBody ... [previousState := state. view isNil ifTrue:[self halt]. self poll. view isNil ifTrue:[self halt]. ''<--- halts here" state := self buttonPressed. ... My solution is From Objectworks\Smalltalk(R), Release 4.1 of 15 April 1992 on 22 August 1992 at 1:17:27 pm'! !Controller methodsFor: 'basic control sequence'! poll ''Announce that we are iterating through the polling loop. If there has been no input for a significant time, wait on a semaphore'' ScheduledControllers checkForEvents. self view == nil ''if the top view was closed" ifTrue: [ScheduledControllers class closedWindowSignal raiseRequest]. self sensor pollForActivity. ''pollForActivity may invoke 'Processor yield'" self view == nil ''check again because we may have lost a race." ifTrue: [ScheduledControllers class closedWindowSignal raiseRequest]! ! ================================================================== pub/Smalltalk/st80_r41/Instance-ClassR41.st ================================================================== '' NAME Instance-ClassR41 AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION Restore borders around >Instance >Class buttons. ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 1 VERSION DATE August 22, 1992 SUMMARY I find the lack of any seperation between the >Instance and >Class buttons in R4.1 annoying, so I put borders around them. From Objectworks\Smalltalk(R), Release 4.1 of 15 April 1992 on 22 August 1992 at 6:34:49 pm''! ================================================================== pub/Smalltalk/st80_r41/RDoItR41/CATALOG-CARD ================================================================== NAME RDoItR41 AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION UNIX command line DoIt, with X11 rootmenu Launcher example. ST-VERSIONS R4.1 PREREQUISITES utils/UnixSock.st Controller-poll_BugFix.st DISTRIBUTION world VERSION ID 41A VERSION DATE August 22, 1992 ================================================================== pub/Smalltalk/st80_r41/LabelTracker.st ================================================================== '' NAME LabelTracker AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION Browser labels show class and method being displayed. ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 1 VERSION DATE August 22, 1992 SUMMARY Before Release 4 the System Browser's label indicated what class and method the browser was displaying. This code restores that functionality to System and Hierarchy browsers. Change the new LookPreferences class method trackLabels to toggle this new behavior on and off. I also suggest that you consider getting OldstyleIcons.st from the archive. It gets rid of the bitmaps in R4 icons. Now if icons would just remember their location across snapshots, I'ld have Version 2.5 functionality back. -Bill Voss ''! ================================================================== pub/Smalltalk/st80_r41/chg/CATALOG-CARD ================================================================== '' NAME CHG AUTHOR Neil W. Van Dyke FUNCTION Class Hierarchy Graph Browser ST-VERSIONS R4.1 PREREQUISITES DISTRIBUTION world VERSION ID 0.3 VERSION DATE December 21, 1992 '' ================================================================== pub/Smalltalk/st80_r41/DebuggerInitialSizeFixR41.st ================================================================== '' NAME DebuggerInitialSizeFixR41 AUTHOR Bill Voss FUNCTION Tiny goodie fixes Debugger's tiny initial size. ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 2 (Version 1 is only for R4.0) VERSION DATE August 22, 1992 SUMMARY This quick fix changes the DEBUG window's initial size to something reasonable (dependent on the screen's size). It does this without changing the existing minimumSize, thus you can still make the window smaller.''! ================================================================== pub/Smalltalk/st80_r41/HierarchyInitialSizeFixR41.st ================================================================== '' NAME HierarchyInitialSizeFixR41 AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION Tiny goodie fixes the HierarchyBrowser's initial size. ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 1 VERSION DATE August 23, 1992 SUMMARY This quick fix changes the HierarchyBrowser's initial size to something I consider more reasonable (dependent on the screen's size). It does this without changing the existing minimumSize, thus you can still make the window smaller.''! ================================================================== pub/Smalltalk/st80_r41/OldstyleIcons.st ================================================================== '' NAME OldstyleIcons AUTHOR Bill Voss (voss@cs.uiuc.edu) FUNCTION Restore the old pre-R4 simple style of icon. ST-VERSIONS R4.1, R4.0 PREREQUISITES none DISTRIBUTION world VERSION ID 1 VERSION DATE August 22, 1992 SUMMARY When used with a good window manager (one that does not impose arbitrary limits on icon labels) this code restores the simple old style of icon by getting rid of the bitmaps. At the moment I am using tvtwm as my window manager. From Objectworks(r)\Smalltalk, Release 4 of 25 February 1991 on 26 November 1991 at 7:16:15 pm''! ================================================================== pub/Smalltalk/st80_r41/SpawnHierarchyR41.st ================================================================== '' NAME SpawnHierarchyR41 AUTHOR Bill Voss FUNCTION Tiny goodie adds a Spawn Hierarchy item to most browsers. ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 2 (This one is based on R4.1 instead of R4.0) VERSION DATE August 22, 1992 SUMMARY The menu options senders, implementors, and messages are very nice, but once I've found the particular Class-Method I'm interested in I usually want to see the entire class. This goodie adds the standard Spawn Hierarchy option to those browsers.''! ================================================================== pub/Smalltalk/st80_r41/ChangesOnMethod.st ================================================================== '' NAME ChangesOnMethod AUTHOR Bill Voss FUNCTION Opens a ChangeList for the currently selected method. ST-VERSIONS R4.1 PREREQUISITES DISTRIBUTION world VERSION ID 1 VERSION DATE September 5th, 1992 SUMMARY This goodie adds a new option 'changes...' to the selector menu. This creates a ChangeList (like the one from 'Launcher->Changes->open change list'). However, unlike the Launcher version, this ChangeList will come up initialized with the 'class' and 'selector' buttons 'ON' viewing the currently selected method. You may choose to open the ChangeList either on just the changes file, or on ALL source files the system knows about. This second option is understandably slow (time for a coffee break) but it will include the 'original' version of the method as well as any changes. This goodie also includes my previous goodie SpawnHierarchyR41 because of a method conflict. SpawnHierarchyR41's summary is: The menu options senders, implementors, and messages are very nice, but once I've found the particular Class-Method I'm interested in I usually want to see the entire class. This goodie adds the standard Spawn Hierarchy option to those browsers. Both of my goodies needed to change 'Browser' method 'selectorMenu'. You may have had previous conflicts as well. Therefore I suggest that after filing in this goodie you open a browser on 'Browser' method 'selectorMenu' and use the new 'changes...' menu item. Being able to see all versions of 'selectorMenu' you should have no problems reconciling any differences. enjoy, Bill Voss ''! ================================================================== pub/Smalltalk/st80_r41/usa.4.1.st ================================================================== '' NAME usa.4.1.st AUTHOR benson@siemens.siemens.com CONTRIBUTOR Dan Benson FUNCTION Map of 50 United States with Browser ST-VERSIONS R4.1 PREREQUISITES usa.data (from uiuc/st80_r4/usa) CONFLICTS DISTRIBUTION world VERSION 2 DATE September 11, 1992 SUMMARY This is a simple graphics application that displays a scrolling map of the 50 United States along with a scrolling list of their names. The user can click directly on a state to highlight it or can choose from the list of names. It is obviously very simple but with a little imagination it can be turned into something more sophisticated. It requires an ASCII data file (usa.data) to be read in. This file defines the boundaries of the 50 states as polygons. See the State class method called readStates to make sure the filename is correct. After filing in the usa.st file, you should initialize the class variables in the State class (readStates) and then you can open a browser (StateBrowser | open). I got the outlines for the states from a public domain MacDraw file. When printing a MacDraw file you can choose to print it to a file. This saves it as a PostScript file. I then edited the file to extract the polygons and manually entered each name. I then read the file in Smalltalk to create Smalltalk objects (flipping the x and y coordinates). To make a long story short, the polygons are now available as Smalltalk objects. NOTE: This filein defines the following category and classes: ('USA' #Boundary #State #StateBrowser #StateView #StateViewController) and adds the following instance methods: ExternalReadString | nextLine Point | quadrantContaining Enjoy. Dan Benson Siemens Corportate Research 755 College Road East Princeton, NJ 08540 benson@siemens.siemens.com ''! ================================================================== pub/Smalltalk/st80_r41/ISYSE/CATALOG-CARD ================================================================== NAME ISYSEnvironment AUTHOR Deeptendu Majumder FUNCTION Attempts to provide an extended work environment ST-VERSION R4.1 PREREQUISITES OrderedDictionary, Case, BrowseInstanceVariableAssignments CONFLICTS DISTRIBUTION world VERSION 2.0 DATE 13 Jul 1993 ================================================================== pub/Smalltalk/st80_r41/T-gen2.1/CATALOG-CARD ================================================================== NAME T-gen2.1 AUTHOR graver@comm.mot.com FUNCTION A Smalltalk-80 Scanner/Parser Generator Tool ST80-VERSIONS R4.0, R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 2.1 VERSION DATE 16 October 92 ================================================================== pub/Smalltalk/st80_r41/RestrictBrowsing.st ================================================================== '' NAME RestrictBrowsing AUTHOR Carl McConnell FUNCTION Allows implementors, senders, etc. to be restricted to a set of categories ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION ID 1.0 VERSION DATE October 23, 1992 This code adds a 'restrict to ...' item to the Launcher 'Browsers' menu that allows 'implementors', 'senders', etc. to consider only categories matching the set of patterns you provide. For example, giving the patterns Tools-* Magnitude-* will cause 'implementors of ...' and its relatives to only display methods in classes that are in categories whose names begin with 'Tools-' or 'Magnitude-'. You can change things back to normal by giving the pattern * The System Browser itself is unaffected: it displays all categories just as it always does. It is only 'implementors', 'senders', etc. that act differently. For example, the 'senders' menu item in the method pane of the browser will only find methods in categories matching the given patterns. This file-in automatically starts up a new Launcher. N.B.: before you decide a message is unused, you might want to change the browsing restriction back to '*' and re-check senders. ''! ================================================================== pub/Smalltalk/st80_r41/smallBrain/CATALOG-CARD ================================================================== '' NAME smallBrain AUTHOR Murali Krishnan, Karl Hess, Selvan Kulandaiswamy FUNCTION Neural network simulator ST-VERSIONS R4.1 PREREQUISITES DISTRIBUTION world VERSION ID 1 VERSION DATE December 11, 1992 '' ================================================================== pub/Smalltalk/st80_r41/NewsReader.st ================================================================== '' (no catalog card submitted for NewsReader.st) ''! ================================================================== pub/Smalltalk/st80_r41/ObjectDebugging.st ================================================================== '' NAME ObjectDebugging AUTHOR hinkle@primenet.com FUNCTION Adding LightweightClasses and Breakpoints ST-VERSIONS R4.1 PREREQUISITES None CONFLICTS None known DISTRIBUTION World VERSION 1.0 DATE 25 October 1994 SUMMARY ObjectDebugging Adds two new concepts to the ST-80 programming environment: lightweight classes and breakpoints. Lightweight classes are a new kind of Behavior that allow specific behavior on a per-instance basis. This is useful in many ways, and the main emphasis for this project is in using unique object behavior as an aid in debugging and system exploration. Breakpoints are an easy way of adding 'self halt'-like behavior at the beginning of methods without changing source files. The code in this file is described in the article 'Debugging Objects,' written by myself, Vicki Jones, and Ralph Johnson, which appeared in the July-August 1993 issue (Volume 2, Number 9) of The Smalltalk Report. -- Bob Hinkle ''! ================================================================== pub/Smalltalk/st80_r41/Refactory20.st ================================================================== 'From Objectworks\Smalltalk(R), Release 4.1 of 15 April 1992 on 16 June 1994 at 1:41:41 pm'! '' NAME Refactory20 AUTHOR droberts@cs.uiuc.edu FUNCTION Provides refactoring tools for Smalltalk Programming ST-VERSIONS R4.1 PREREQUISITES CONFLICTS DISTRIBUTION world VERSION 2.0 DATE 6/20/94 SUMMARY Refactory The refactory provides tools to manipulate programs while preserving behavior. These allow the programmer to alter a design without worrying about breaking existing code. For more information about refactoring and the user's guide, either look at the refactory WWW page at http://st-www.cs.uiuc.edu/users/droberts/Refactory.html, or send E-Mail to the author to request a text version. Don Roberts University of Illinois ''! ================================================================== pub/Smalltalk/st80_r41/Regions/CATALOG-CARD ================================================================== NAME Regions.st AUTHOR dbenson@siemens.com FUNCTION graphical browser for map regions ST-VERSIONS R4.1 PREREQUISITES THEN FILE IN CONFLICTS WITH DISTRIBUTION world VERSION ID 1.0 VERSION DATE 5 Mar 93 ================================================================== pub/Smalltalk/st80_r41/NewTool/CATALOG-CARD ================================================================== NAME NewTool AUTHOR walkowsk@cs.uiuc.edu FUNCTION An alternative Browser ST-VERSIONS R4.1 PREREQUISITES THEN FILE IN CONFLICTS WITH DISTRIBUTION world VERSION ID 1.1 VERSION DATE 4/1/93 ================================================================== pub/Smalltalk/st80_r41/latex.st ================================================================== '' NAME latex.st AUTHOR Carl McConnell FUNCTION print out Smalltalk source as LaTeX source ST-VERSIONS R4.1 PREREQUISITES none DISTRIBUTION world VERSION 1.0 DATE April 7, 1993 This code adds a 'print LaTeX on...' choice to the menus in the various browser panes. When selected, this menu choice produces a file containing a LaTeX version of the Smalltalk source for the selected item. LaTeXing categories and classes yields self-contained LaTeX documents; LaTeXing protocols and methods yields output meant for inclusion in a LaTeX document. In particular, LaTeXing a category yields a document with a table of contents showing what page the class definitions are on, and so the resulting file needs to be latex'd twice. Carl McConnell mcconnel@cs.uiuc.edu Department of Computer Science University of Illinois at Urbana-Champaign ''! ================================================================== pub/Smalltalk/st80_r41/notes2.st ================================================================== 'From VisualWorks(TM), Release 1.0 of 8 October 1992 on 2 July 1995 at 9:34:37 pm'! '' NAME notes2.st AUTHOR rutzmir.netvision.net.il ( Noam Cohen) FUNCTION general notes (keyword accessed) keeper. ST-VERSIONS R4.1 PREREQUISITES none CONFLICTS none DISTRIBUTION world VERSION 1.1b DATE 3 july 1995 SUMMARY notes2.st Writing notes when sitting in front of the screen is a common thing. So I wrote this utility that lets you add a note (free text) with keywords that enables you to retrieve it later. After you have your note(s), you FIND those you need by using keyword ( with widcards) or text matching. Printing and removing is also supported ( and there is even HELP). The Help workspace opened when you file this code will tell you anything you need to know. Future additions: augment the text note to include images. Use drag and drop. from the kitchen of... Noam Cohen ''! ================================================================== pub/Smalltalk/st80_r41/postscript.st ================================================================== '' NAME Postscript AUTHOR Luis Tavera & Thorr Einarsson, but send e-mail to johnson@cs.uiuc.edu FUNCTION A subclass of GraphicsContext that generates Postscript ST-VERSIONS R4.1 PREREQUISITES DISTRIBUTION world VERSION ID 0.2 VERSION DATE July 23, 1993 This code creates a subclass of GraphicsContext named PSGraphicsContext that generates Postscript on a stream instead of displaying on a window. It is a wonderful idea, because it means that you can print anything that you can display. This code has a few bugs that are described in the class comment for PSGraphicsContext. However, this code is useful in spite of these bugs, especially for drawing a single view. This file adds a 'print' menu item to the menu that allows you to print the current window to a file in Postscript. It consists of a little StandardSystemController code, followed by the code for the (new) category Graphics-Postscript. This category includes some PS font classes borrowed from the ParcPlace distribution. When you file this in, you will be prompted for the directory in which the Postscript font files reside, which is probably .../Objectworks4.1/utils/FontMets. ''! ================================================================== pub/Smalltalk/st80_r41/STones80.st ================================================================== '' NAME STones80 AUTHOR bruce@utafll.uta.edu (Bruce Samuelson) FUNCTION low and medium level benchmarks for ST80 and ST/V ST-VERSIONS pre R4.0, R4.0, R4.1, ST/V PREREQUISITES need floating point hardware or emulation CONFLICTS none DISTRIBUTION world VERSION 1.0 DATE April 16, 1993 SUMMARY The filein includes two classes: Slopstones (Smalltalk Low level OPeration Stones) and Smopstones (Smalltalk Medium level OPeration Stones). Each includes seven cpu intensive benchmarks. They work equally well with 16-bit and 32-bit implementations and are designed to be portable to all Smalltalk versions from ParcPlace and Digitalk. They are normalized to the author's 486/33 Windows 3.1 machine running ParcPlace VisualWorks 1.0. Results have been posted to the Usenet group comp.lang.smalltalk and form the basis of an article that is scheduled to be published in the June issue of The Smalltalk Report. The only difference between the ST80 (STones80) and ST/V (STonesV) filein is in the messages that define the classes in the first few lines of code. The ST80 messages specify the class category and message protocol, which are not used in ST/V. Bruce Samuelson''! ================================================================== pub/Smalltalk/st80_r41/imageToXWD.st ================================================================== '' NAME imageToXWD AUTHOR Brad Schoening FUNCTION Writes a Smalltalk image to an X11 xwd file ST-VERSION R4.0, R4.1 PREREQUISITES CONFLICTS DISTRIBUTION world VERSION 1.0 DATE July 1993 SUMMARY Exports a Smalltalk Image object to a file in X11 xwd format. The standard X11 utilities xpr and xwud can can then be used to print and view the file. For Unix users, this can be a convenient way to print ST80 images to a PostScript or PaintJet printer. ''! ================================================================== pub/Smalltalk/st80_r41/FileNavigator.st ================================================================== '' NAME FileNavigator AUTHOR Carl McConnell FUNCTION An easier-to-use alternative to the standard Smalltalk file browser ST-VERSIONS R4.1 PREREQUISITES none CONFLICTS none DISTRIBUTION world VERSION 1.0 DATE July 12, 1993 SUMMARY FileNavigator provides the same functionality as FileBrowser, but with an easier-to-use select-and-click interface reminiscent of a Macintosh file dialog box. It should be obvious how to use FileNavigator. If not, or if you have suggestions, find bugs, etc., please send e-mail to the author. I've only tested FileNavigator on the Macintosh, so although it's supposed to be portable, minor problems may crop up on other platforms. Filing in this file starts up a new Launcher in which the file utilities invoke FileNavigator. This file makes two alterations to existing code. First, it changes to FileNavigator all references to FileBrowser. This is done by editing the existing source rather than redefining it; thus, you need not worry about your Launcher menus changing, for example. Also, this file redoes MacFilename class>>localNameStringFrom:, since it seemed completely wrong. It was not used anywhere in the image, so unless you file in other code that does use it, there should be no problem. ''! ================================================================== pub/Smalltalk/st80_r41/TestMgr/CATALOG-CARD ================================================================== NAME TestMgr AUTHOR gordondavi@aol.com (Gordon Davis) FUNCTION A testing system for Smalltalk-80 ST-VERSIONS R4.1 PREREQUISITES st80_r41/hotdraw41/HotDraw-source THEN FILE IN testing.st, coverage.st CONFLICTS WITH DISTRIBUTION world VERSION ID 2.0 VERSION DATE 26 Nov 94 SUMMARY TestMgr This directory contains: 1) testing.st (Most of the testing system) 2) coverage.st (Additions/changes to ByteCodeStream, ClassDescription, Context, SmalltalkCompiler, and several classes in category System-Compiler-Program Objects) TestManager is a system for managing test cases for Smalltalk-80 code. It also measures execution time and produces an execution profile and coverage metrics. Test pass verification is done by evaluating a series of Smalltalk expressions (a doIt) and then comparing the printString of the value of the last expression with an expected (textual) result. The reason that the file-in is divided into two, is that coverage.st contains changes to some of the system classes. Actually, testing.st also changes system classes but it only adds methods, it doesn't change any of the ParcPlace methods. If you don't file-in coverage.st, you can still use every feature except for the coverage features (the Instrumentation Tool will still allow you to specify coverage instrumentation for a TestSuite but when you execute the TestSuite it will bomb). A usage guide is included in the author's Master's thesis. The thesis has not yet been completed but the first four chapters, which include the user's guide for TestManager are available on this server under /pub/papers/gdavis. These chapters are in Microsoft Word For Windows 6.0 format. If anyone can convert them to postscript I would be very grateful. The previous (and first) version was 0.9. Changes for version 2.0: Major: Much, much faster coverage instrumentation specification tool. Old test databases will no longer work. You will have to hack around in BOSS or wait until I can fix it. If you have a large test database in the old version, let me know and I will see if I can come up with a fix. Medium: Class name changes including the class used to launch TestManager. Now you use ''TestNavigator open'' or "TestNavigator openFromBinary". Minor: Maintenance, re-write of topological sort All comments are eagerly and gratefully accepted. Gordon Davis - 26 November 1994 ================================================================== pub/Smalltalk/st80_r41/HotDraw41.4/CATALOG-CARD ================================================================== NAME HotDraw41.4 AUTHOR brant@cs.uiuc.edu FUNCTION Framework for stuctured drawing editors KEYWORDS widget graphics ST-VERSIONS R4.1, VisualWorks 1.0 PREREQUISITES none THEN FILE IN (1) HotDraw.st, (2) any of the sample applications CONFLICTS WITH DISTRIBUTION world VERSION ID 4 VERSION DATE 18 Jul 94 SUMMARY This directory contains HotDraw, a framework for structured, 2D drawing editors. It can/has been used to create many different editors from case tools to object inspectors. The HotDraw.st file contains the graphics framework and the other files are sample applications that have been built using HotDraw. These are the same sample applications that were built with the older version of HotDraw (minus the HyperCard clone) except that they have been converted to run with this version. They do not need to be filed-in, although they are useful to see how HotDraw applications are built. DrawingInspector.st -- nice visual object inspector that can be used by selecting the draw menu option from an inspector. This is a nice tool to have even if you don't use HotDraw. HotPaint.st -- a painting program MovingDrawing.st -- simple program that uses animation NetworkEditor.st -- use animation to solve a graph layout problem; place nodes and assign communication amounts between them ObjectWorld.st -- create figures and give commands to move them around the drawing PERTChart.st -- a pert chart program; edit the duration or ending date and have its dependents updated automatically General questions about HotDraw can be directed to the HotDraw mailing list hotdraw@cs.uiuc.edu. John Brant - 20 Jul 94 ================================================================== pub/Smalltalk/st80_r41/HBFullBrowser1.01.st ================================================================== '' NAME HBFullBrowser AUTHOR Bruno.Bienfait@EROS.CCC.Uni-Erlangen.de FUNCTION Extend the full protocol class browser with history and buffered text ST-VERSIONS R4.1 PREREQUISITES FullBrowser of APOK. CONFLICTS none. DISTRIBUTION world VERSION 1.01 DATE 7-25-1995. SUMMARY : History &Text- Buffered & Full Protocol Browser The two new buttons ''Methods History" and "Class History" allow you to jump quickly to a previously visited method or class definition. The whole state of the browser is saved in history, i.e., not only the selected method but also the status of the subs, supers and names buttons, the show inherited duplicate option and the included and excluded classes in the hierarchy view. -The HBFullBrowser contains a text buffer. If you modify a method and go to another, you don't have to accept/cancel it. When you go back to the modified method, the browser retrieves your changes. The button ''Show Instance" opens an inspector on an instance of the selected class, or on an array if they are more than one instance. HBFullBrowser changes dynamically its behaviour with the help of #changeClassToThatOf: . It 's an example of the ''state" pattern. See help for more information. The version 1.01 fix a few bugs. ------------------------------------------------ Bruno.Bienfait@EROS.CCC.Uni-Erlangen.de http://schiele.organik.uni-erlangen.de/Bruno_Bienfait/home.html ------------------------------------------------ ''! ================================================================== pub/Smalltalk/st80_r41/SmallWalker1.0/CATALOG-CARD ================================================================== NAME SmallWalker AUTHOR Kazuki Yasumatsu FUNCTION A World-Wide Web browser ST-VERSIONS R4.1 PREREQUISITES utils/{ExtIPC.st,UnixIPC.st,UnixSock.st,Printing.st} CONFLICTS WITH DISTRIBUTION world VERSION ID 1.0 VERSION DATE September 1, 1995 SUMMARY SmallWalker, a World-Wide Web browser for Smalltalk, offers the following features: o Supports HTML 3.0 + some Netscape extensions o Supports Image Formats: GIF, XBM, XPM, PBM, PGM, PPM and JPEG (needs djpeg v5) o Supports Internet Ptrotocols: http, ftp(FTP), news(NNTP), mailto(SMTP) The code of SmallWalker contains the following re-usable class libraries: o HyperText o SGML Parser o Image Format Reader/Writer o Network (HTTP, FTP, NNTP, SMTP, POP) & RFC822 Message Parser o External (Persistent) Dictionary SmallWalker is provided at no charge under the terms of the GNU General Public License Version 2, June 1991. The text of that license is included in the distribution (see the file ''COPYING".) It is provided in source-code form. To install the SmallWalker WWW browser, first, you must fileIn the following files (these files are included in the Objectworks\Smalltalk, Release 4.1 distribution): ExtIPC.st UnixIPC.st UnixSock.st Printing.st Then, you fileIn 'Install.st' in the SmallWalker distribution. Kazuki Yasumatsu