@database "TextWin.guide"
@date 12-7-94


@NODE main
@TITLE "Table of Contents"
@{fg highlight}

        TextWin: A new MUI requester from BOTH Software
        Freely distributable.  Copyright 1994. Freeware
@{fg text}

                     @{" Requirements  " link re}
                     @{" Installation  " link in}
                     @{" Using TextWin " link ad}
                     @{" Distribution  " link di}
                     @{"  MUI License  " system "execute demo.example.scp"}
                     @{"    Authors    " link bs}
                     @{" Beta Testers  " link be}
@{b}
              ______          __ _       ___     
             /_  __/__  _  __/ /| |     / (_)___ 
              / / / _ \| |/_/ __/ | /| / / / __ \
             / / /  __/>  </ /_ | |/ |/ / / / / /
            /_/  \___/_/|_|\__/ |__/|__/_/_/ /_/ 
            is a new tool for DOS script writers                                     
@{ub}








@ENDNODE

@NODE ad

 Usage : TextWin 

 TITLE/A,BODYTEXT=BODY/A

 Arguments:

 @{"TITLE      " link ti}  <text> - Title text for requester window.
 @{"BODY       " link bo}  <file> - Body text for requester window.

@{fg highlight}
 DESCRIPTION
@{fg text}
 @{b}TextWin@{ub} is a general purpose advisory requestor. It's function
 is to present the user with a scrollable MUI window that displays text. 
 It offers one Button to clear the requester.The text comes from a file
 or the command line.

 It is possible, if you are so inclined, to use TextWin as a filereader.
 
 Example:
@{fg fill}
     STACK 8000
     IF EXISTS MUI:
       TextWin TITLE "Info for you" BODY RAM:help.txt
     ENDIF
@{fg text}
     Click @{"Signs" system "execute demo.example1.scp"} to see it in action.

 TextWin is meant to be called from a DOS script. If you do not know if MUI is
 present, it is recommended you test for it's existance. See the example above
 for the syntax. 
@{b}
                Be sure to set a stack of 8000
                at the beginning of the script.
@{ub}
@endnode


@NODE TI
@TITLE "TITLE/A"
@{fg highlight}
     TITLE
@{fg text}

 TITLE is a Required argument and it is Positional.

 This information appears in the top bar of the window. It should 
 describe the kind of information the user is expected to provide.
@{fg fill} 
     TextWin TITLE "Installation Instructions" BODY dh3:instructions
@{fg text} 
 The word TITLE does not have to be used as long as the text is 
 presented as the first string following the name of the requester.
@{fg fill}
     "Installation Instructions" BODY dh3:instructions
@{fg text}
 There is no default value for TITLE. If you choose not to  present
 any information in the title bar, you must include a null string as
 the first string after the argument.
@{fg fill}
     TextWin "" BODY dh3:instructions
@{fg text}




@ENDNODE


@NODE BO
@TITLE "BODY/A"
@{fg highlight}
     BODY
@{fg text}

 BODY is required and positional.

 This is the text that appears inside the window. Use TextWin to give
 specific instructions to the user. 
@{fg fill}
  TextWin "Installation Instructions" @{b}BODY RAM:help.txt@{ub}
@{fg text}
 The word BODY does not have to be used as long as the text is pres-
 ented as the next string following TITLE.

 The text usually comes from a textfile. If a path is necessary, include
 it like this:
@{fg fill}
     BODY DH2:extrainfo.txt
@{fg text}
 If the filename has a space in it, enclose the entire path/filename
 in double quotes.
@{fg fill}
     BODY "DH2:Extra Info.txt"   
@{fg text}

 The text can also come from the command line.
@{fg fill}
     BODY "This text comes from the command line"
@{fg text}

 This is an inefficient way to display text. If you only need to display
 a small amount of text we recommend you use @{b}rtEZrequest@{ub}, found on
 Aminet as util/cli/DOSReqTools.lha. 



@ENDNODE
 
@NODE bs
@TITLE "Those guys? Again?"

 TextWin was written to compliment MUI Interface, (dev/gui) a package that
 generates and controls a MUI GUI from a DOS script.

 If you find any bugs or have any comments, please contact the Authors.
 Email messages will be answered immediately. Snail Mail letters will 
 take longer since we never learned to read or write too well.

@{fg highlight}
      C & UNIX Code                  Program Design, GUIs, Docs@{fg text}
      --------------------------     --------------------------
      Will Bow                       Colin Thompson
      1531 Corinth Unit 1            9606 Carroll Cyn. Rd. H9
      West Los Angeles, CA 90025     San Diego, CA 92126
      (310) 478-4913                 (619) 695-2181
      InterNet:wbow@crl.com          InterNet: colin@cts.com

 ------------------------------------------------------------------
@{fg highlight}
@ENDNODE
@NODE BE
@{b}
                    BETA TESTERS NEEDED
@{ub}

 We have several projects underway that require extensive beta testing.
 If you are AmigaDOS-literate and have the time to wring out some new
 programs please contact us via email. The only requirements we place on
 beta-testers is that they have access to the Internet and have MUI 
 and MUIBuider installed on their system.   


@{b}
                    COMALITES UNITE !!!!
@{ub}
                   BETA TESTERS NEEDED FOR
                  A COMAL PORT TO THE AMIGA
@{fg text}

 25 November 1994

 We are writing a replacement for the Amiga Shell, based on COMAL.2.  
 The COMAL Shell will be DOS compliant with COMAL structures. It is 
 based on the COMAL '85 standard, with @{b}several@{ub} extensions added.

 If you were a COMAL programmer on the C64, and would like to see 
 COMAL ported to the Amiga, please contact us. Len Lindsay has 
 closed the COMAL Users Group, so he won't be able to help us much on 
 this project. We have the BNF notation for the language and have 
 just finished writing the parsor. We need your input on how the
 language should be implimented. As we see it, COMAL will be used as 
 a replacement for the Shell. We will include all of COMAL.20 except 
 turtle graphics, PEEK and POKE. The effect of this will be to give 
 you access to all of the looping structures, string handling, file 
 handling, and other wonderful features COMAL has, but DOS doesn't.
 
 Our implementation will incorporate a script driven version of MUI.
 This will give COMAL an infinate variety of requesters and GUIs. It
 will also give COMAL access to intuition. Try THAT from DOS!

 COMAL on the Amiga would be interpretive, including the LOAD and RUN
 commands. We have looked at EVERY shell ever written for the Amiga 
 and, frankly they are mostly UNIX creatures, not intended for 
 amateur programmers. We hope to put a structured, high level 
 language back in the hands of those who haven't learned C. COMAL was
 invented by Borg Christiansen in 1976. He did it because Pascal was
 simply too difficult to teach to most people.

      A COMAL compiler is also planned.  This would give
      registered developers the ability to write commercial
      programs in COMAL and compile them for distribution.

 We believe the resurrection of COMAL would be a boon to the Amiga
 Community.  If an easy-to-learn language was available, perhaps we
 would see a new generation of programmers showing off their skills. 
 Maybe Amiga User Groups would flourish again.  Maybe pigs will fly. 
 Who knows. No one will ever know unless we try.
 
 If you don't remember COMAL, but are skilled in high level languages,
 we want to hear from you. We've never written a language before. 

      Will Bow 
      Colin Thompson


@ENDNODE


@NODE DI
@TITLE "Distribution and Copyright Notice"

 TextWin is copyright 1994 by BOTH Software. It is @{b}GIFTWARE@{ub}.
 That means if you like it and use it, you may send us a Gift. 
 A birthday card or email would be nice. We would really like
 to hear about how you've used the requester. 

 If you feel the requester could be made more useful, please contact 
 @{"BOTH Software." link bs} 

 TextWin is free to use and copy as you see fit. The Authors retain
 all rights to the Program. The Authors are not responsible for any
 damage the Program may cause. If you distribute the Program, you
 MUST distribute the entire package with the documentation and copy-
 right notices.

 The exception to this requirement would be if you wrote a script that
 used the requester.  TextWin may be distributed with your script(s).

 TextWin may be included in any archive collection. 

 Tested on a 3000, 2000, 1000, 600, and a 1200 without problems.

@ENDNODE


@NODE re
@title "System Requirements for TextWin"

 You must have MagicUserInterface installed.
 WorkBench 2.x and up is required.
 Script usage only
@endnode

