home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-11-21 | 2.3 KB | 51 lines | [TEXT/R*ch] |
- /*
- ** Newton Developer Technical Support Sample Code
- **
- ** Custom Route, a Newton 2.0 routing example
- **
- ** by J. Christopher Bell, Newton Developer Technical Support
- **
- ** Copyright © 1994-5 by Apple Computer, Inc. All rights reserved.
- **
- ** You may incorporate this sample code into your applications without
- ** restriction. This sample code has been provided "AS IS" and the
- ** responsibility for its operation is 100% yours. You are not
- ** permitted to modify and redistribute the source as "DTS Sample Code."
- ** If you are going to re-distribute the source, we require that you
- ** make it clear in the source that the code was descended from
- ** Apple-provided sample code, but that you've made changes.
- */
-
- This example shows how to set up your routing formats and routeScripts
- for Newton 2.0.
-
- In the Newton 2.0 world, applications do not enable a specific transport
- but rather transports supporting compatible paradigms like "view stuff",
- "frame stuff".
-
- Unlike Newton 1.x Routing, the action button is context sensitive, which
- means that the action button uses its location in the view hierarchy to
- figure how to display/route an item. It does not require your base view
- to handle everything or for your application to have a single global
- routing frame which applies to your application.
-
- CustomRoute takes advantage of context sensitive routing by displaying
- a subview an the application, to attempt to illustrate which messages
- are context sensitive and which messages MUST be implemented in your
- base view.
-
- In the top subview, there is data which corresponds to a format which
- can display "view stuff" and "text"... which means that the dataTypes slot
- value is ['view, 'text].
-
- This sample also handles put away for beam, mail, or any third party
- 'frame transport that comes along. Note that your putawayscript should
- check to see whether it can handle the data before trying to put it away!
-
- In order handle print and fax, you must register at least one protoPrintFormat.
- In order handle beam and mail, you must register at least protoFrameFormat.
-
- If you want to handle just frame or just text, use a protoFrameFormat and
- override the dataTypes slot to be ['frame] or ['text] and be sure to set the
- text in the format's textScript if necessary.
-