source: WorldVistAEHR/trunk/r/VICTORY_PROGRAMMING_ENVIRONMENT-ZVEM/ZVEMSH5.m@ 1604

Last change on this file since 1604 was 613, checked in by George Lilly, 15 years ago

initial load of WorldVistAEHR

File size: 3.1 KB
Line 
1ZVEMSH5 ;DJB,VSHL**BOXES [07/14/94]
2 ;;12;VPE;;COPYRIGHT David Bolduc @1993
3 ;
4BOXES ;;;
5 ;;; B O X E S
6 ;;;
7 ;;; To help you organize the User QWIK commands you develop, the VShell allows you
8 ;;; to store them in boxes. A box can be any whole number.
9 ;;;
10 ;;; Let's look at the UCI QWIK which we set up earlier. We had you assign it to
11 ;;; box 1. You can display the QWIKs stored in box 1 by typing one dot and the
12 ;;; box number. Type '.1' and you will see your UCI QWIK along with any other
13 ;;; QWIKs that have been assigned to box 1.
14 ;;;
15 ;;; If you recall, you may display your User QWIKs by hitting <PF1> or <PF2>. You
16 ;;; will find however, as you develop more and more User QWIKs, it becomes easier
17 ;;; and clearer if you group them into boxes and display the boxes.
18 ;;;
19 ;;; System QWIKs also use boxes. To display the System QWIKs assigned to a box,
20 ;;; type two dots and the box number. For example: '..1' will display all System
21 ;;; QWIKs assigned to box 1. The System QWIKs have been grouped as follows:
22 ;;;
23 ;;; Box 1..... All QWIK related System QWIKs
24 ;;; Box 2..... All VShell related System QWIKs
25 ;;; Box 3..... Programmers' Tools
26 ;;; Box 4..... Fileman/VA Kernel related System QWIKs
27 ;;; Box 5..... Vendor Generic Utilities
28 ;;;
29 ;;; Typing one or two dots and the box number will display QWIKs and their
30 ;;; descriptions. If you wish to see the code they will execute, type a letter
31 ;;; 'C' after the box number. So, '.1C' will display User QWIKs assigned to box 1
32 ;;; and the code those QWIKs will execute.
33 ;;;***
34VENDOR ;;;
35 ;;; V E N D O R S P E C I F I C C O N F I G U R A T I O N S
36 ;;;
37 ;;; The VShell will allow you to set up an environment that will work the same
38 ;;; regardless of which Mumps system you are running.
39 ;;;
40 ;;; Using the QV System QWIK, you can make User QWIKs that execute different code
41 ;;; depending on your Mumps implementation. To illustrate, let's take the QWIK
42 ;;; called UCI you set up earlier, and make it so this QWIK will work in both
43 ;;; Micronetics and DataTree Mumps.
44 ;;;
45 ;;; In Micronetics Mumps you switch UCIs with 'DO ^%LOGON'. In DataTree you use
46 ;;; 'd ^%nspace'. We've already set up a UCI QWIK. Now type '..QV'. You will be
47 ;;; prompted for a QWIK name. Enter 'UCI'. Next, the VShell will display a list
48 ;;; of vendors and you will be asked to select one. Then it will ask for the
49 ;;; vendor specific code you want this QWIK to execute. You first select
50 ;;; Micronetics and enter 'DO ^%LOGON'. Next, you select DataTree and enter
51 ;;; 'd ^%nspace'. That's all there is to it.
52 ;;;
53 ;;; When you first enter the VShell, it identifies what Mumps vendor you are
54 ;;; using. Whenever it executes a User QWIK, it first checks to see if there
55 ;;; is a vendor specific version. If there is, it executes it. If there isn't,
56 ;;; it executes the non-vendor specific version.
57 ;;;
58 ;;; There are a number of Vendor Generic System QWIKs located in box 5. These
59 ;;; QWIKs have been set up using the principles described above. They will work
60 ;;; the same for DSM, VAX DSM, DataTree, and Micronetics Mumps.
61 ;;;***
Note: See TracBrowser for help on using the repository browser.