Return to README.rtf CVS log

Up to [NeXTSTEP 3.3 examples] / Examples / AppKit / Yap

Annotation of Examples/AppKit/Yap/README.rtf, revision 1.1.1.1

1.1       root        1: {\rtf0\ansi{\fonttbl\f1\fswiss Helvetica;\f2\fmodern Courier;\f0\fmodern Ohlfs;}
                      2: \paperw9560
                      3: \paperh9860
                      4: \margl120
                      5: \margr120
                      6: {\colortbl;\red0\green0\blue0;}
                      7: \pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f1\b\i0\ul0\fs36\fc0\cf0 Yap
                      8: \b0\fs24 \
                      9: \
                     10: Yap, 
                     11: \i Yet Another Previewer
                     12: \i0 , is a simple text-editor which provides the ability to interactively execute the documents as PostScript programs.  Yap demonstrates:\
                     13: \
                     14: 
                     15: \fi-140\li360 � Execution of random PostScript code in a separate window server context\
                     16: � Caching drawing for fast scrolling purposes\
                     17: � Multi-window documents loaded from nib files containing ScrollViews with subclass of  Text\
                     18: � Pasting PostScript as text\
                     19: � A simple Find panel\
                     20: 
                     21: \fi0\li0\fc1\cf1 \
                     22: 
                     23: \f2 YapOutput.m
                     24: \f1  and 
                     25: \f2 YapWrap.psw
                     26: \f1  contain the code which creates a separate context that is focused on a window belonging to the application's main context and send PostScript down to this second context for execution. This second context is kept around as long as no errors occur; however, in case of errors a new one is created.\
                     27: \
                     28: 
                     29: \f2 YapDocument.m
                     30: \f1  shows the YapDocument class which manages the documents. The source code for YapDocument demonstrates, among other things, how to read a 
                     31: \f2 .nib
                     32: \f1  file over and over again to create multiple document windows.\
                     33:  \
                     34: If your application needs to import EPS files, then its probably best to stick to the 
                     35: \f2 NXEPSImageRep
                     36: \f1  class (or 
                     37: \f2 NXImage
                     38: \f1 , which uses 
                     39: \f2 NXEPSImageRep
                     40: \f1  to manage its EPS representations) rather than using the code in 
                     41: \f2 YapOutput.m
                     42: \f1 . 
                     43: \f2 NXEPSImageRep
                     44: \f1  uses a separate context to execute EPS files in a manner similar to Yap.\
                     45: 
                     46: }

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.