SuperSlurp 1.0 by Jim Schram & Todd Courtois

This is SuperSlurp, which bears only a minor resemblance to the earlier Slurp
sample code by Scott "ZZ" Zimmerman.

SuperSlurp receives standard tab-delimited data from a PC over MNP serial
communications, and slams the data into a soup.

Currently SuperSlurp is designed so that you can create new soups on the fly
from data you send from the Mac.  So for instance if you wish to create
or add application soups, you can do this with Slurp.  You may need to add
some code of your own if you want to add an index or whatever to your soup.


I've enclosed a sample file which dumps entries into the Names soup.  This
particular file is rather small, but it gives you an ide of how fast
SuperSlurp can suck data into the soup.

Here's the setup for using SuperSlurp as is:

1. Need a mac with the Apple Modem CTB Tool in your extensions folder.  This
   is the CTB tool which comes with NTK. 
2. Use the "macterminal setup" file to set up MacTerminal appropriately.
   The basic settings are: Newton Serial Connection, 57600 bps, Software
   error correction.  You can use MacTerminal, ClarisWorks, or some other
   terminal emulator of your choice, or even your own Mac or PC code if it
   supports MNP level 5. 
3. On the macterminal side, choose "Wait for Connection" 
4. On the Newton side, open SuperSlurp and hit the "Receive" button 
5. On the macterminal side, send the "Names Data" file using the TEXT
   tool, CR at line endings 
6. The Newton will automatically suck down the data, using MNP to regulate
   the data flow (you can watch this process easily with the progress bar
   in MacTerminal or ClarisWorks). 
7. When finished, the Newton will automatically close the connection
   and the Mac side will notify you that the connection has been closed.

Check the Names soup -- the entries are there!

You can abort the connection at any time from the Newton side.

I've also included an "inspector test" file so that you can test the
slurpBaseView:StuffNewEntry() method from the inspector without going through
the endpoint code.  This may help you debug your modified version.  Notice
that the strings in the inspector test file explicitly give the tab and
double quote characters.