ftp.nice.ch/pub/next/unix/developer/oobr.2.8.6.tar.gz#/oobr/tree-nx

English.lproj/
 
History.rtf
[View History.rtf] 
Line.h
[View Line.h] 
Line.m
[View Line.m] 
Makefile
 
NamedTree.h
[View NamedTree.h] 
NamedTree.m
[View NamedTree.m] 
PB.gdbinit
 
PB.project
 
README.rtf
[View README.rtf] 
String.h
[View String.h] 
String.m
[View String.m] 
Test.tree
 
Tree.h
 
Tree.m
 
Tree.tiff
 
Tree2.tiff
 
TreeButton.h
[View TreeButton.h] 
TreeButton.m
[View TreeButton.m] 
TreeButtonCell.h
[View TreeButtonCell.h] 
TreeButtonCell.m
[View TreeButtonCell.m] 
TreeController.h
[View TreeController.h] 
TreeController.m
[View TreeController.m] 
TreeView.app/
 
TreeView.h
[View TreeView.h] 
TreeView.iconheader
 
TreeView.m
[View TreeView.m] 
TreeView_main.m
[View TreeView_main.m] 

README.rtf

This program is released under the terms of the GNU General Public License.  Do what you want with it.

See the History.rtf file to see what this program is all about.

To run, launch it from the Workspace and have it read in a .tree file (format is in ascii, as described in History.rtf).  The tree will be displayed graphically.  Click on a button to activate a node.  When a node gets sent an activation message, it prints it's contents to stdout, which means that you will see feedback in the WorkSpace Console.

And that's all there is.  This program mainly serves as a programming example and a way to make available a generic Tree class.  The Tree class is particularly useful for building parse trees, and subclasses could easily be made to create a recursive pretty-printer automatically.  (I have used the Tree class in an optimizing compiler which deals with a subset of Pascal, and the Tree did pretty printing and three-address code generation automatically by just sending the appropriate message to the root node.  It worked out quite nicely.  Each subclass corresponded to a different type of programming construct¼)  Also of note is the way I use a List as a display List for the line objects.  Any type of object that can render itself could be placed in that list, which is part of how my gamekit deals with multiple types of sprites...  and in the file parsing is an example of how a List object can be used as a stack.  (It could be used as a queue, too, if you think about it.  Quite a nifty object IMHO.)

If you have any questions, requests, whatever, feel free to contact me.


Don_Yacktman@byu.edu



}

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.