*[ PowerPager Documentation ]************************************************

            PowerPager V0.9 [Beta] For AmiExpress/SigmaExpress
                Updated for v0.12 [Beta] 27/12/95 [at TP5]
 Code: MeNaCe/Indenpendent ÷ Additional Ideas: Flozzy ÷ Beta: Flozzy & Enzo

*[ Program Description ]*****************************************************

Powerpager is a quite powerfull pager with features FULL GUI Configuration,
Chat-Request  Window,  Macros, Accept Chat, and Quiet ( Disables the Beep's
without letting user know it.  )

*[ Installation ]************************************************************

Install  this  door  as  every  other  XIM-Door.   The  door  is  tested on
AmiExpress  and  Sigma  Express  so  there  should  be  no problem.  If you
encounter some, please report this to me asap - so I can fix the problem.

*[ Program Logic ]***********************************************************

If a user wants to chat, the door will:

- Check if a log is wanted.  If so, the file will be opened.

- Check if intuition.library, gadtool.library, reqtools.library
  utility.library and the memory allocation for the configuration went ok.
  If one or more of these thing fails it will display a error, and exits.

- Everything ok: If SysopIsInChat-Action is set to REFUSE and the
  the sysop is in chat the door will display: 
  BBS:BBSTexts/PowerPager/ChatRefuse(access).txt(.gr) and exit.  If the
  user got clearance to override the CF the door will continue without
  showing any file.

- At this point the doors checks if the user is blacklisted, if so
  the   displays  BBS:BBSTexts/PowerPager/BlackListed(access).txt(.gr)  and
  exits.

- If the chat flag is off and the user tries to page - the file
  BBS:BBSTexts/PowerPager/SysopNotAvail(access).txt(.gr) is displayed,
  but the user got CF Override access - the door will continue as if
  the chatflag was set to on.

- The paging process: The file 
  BBS:BBSTexts/PowerPager/Paging(access).txt(.gr)
  is displayed. And if the SysopIsInChat-Action is set to NOTIFY
  an additional line is display, informing the user that sysop
  is already in a chat with another user.

- A reason is prompted. If the input is valid the door continues..

- At this point PowerPager sets the env-variable (STATS@) to
  Requesting Chat, and sets up the window with gadgets.  The window
  is opened on the default public screen, and this screen is moved
  to front if it isn't the current screen.  PowerPager pages for
  about 17 sec, and if it receives no response it'll just exit, closing
  the window.  At every half second a DisplayBeep is made.
  The  process  is aborted by pressing any key.  If the sysop presses "Send
  Text"  the  text/macro  displayed in the cyclegadget is send to the user,
  and the door exits.  If the text startes with an '<' the rest should be a
  filename.  eg:  "<BBS:Comming" cause the door to display a file named
  BBS:Comming(access).txt(.gr).
  To change macro/text press the cyclegadget - or use f1 through f10
  to select text.  If the sysop presses the "Enter string.." a ReqTools
  string request pops up ( but also freezes the paging process :( ).
  Anything entered in this request is displayed to the user, and
  afterwards the door exits.  The two last buttons are probaly the most
  important of them all.  "Accept" accepts the chat-request, and goes
  into chat after pressing this on.  "Quiet" Stops the door from using
  DisplayBeep - and thereby stops the beep'ing.  Nice if you don't wanna
  talk to the user without beeing "nasty" ( Nothing happens from the user
  point of view ).

- If the chatrequest was unsuccessfull the door exits.

*[ Configuration ]***********************************************************

To  setup  Powerpager  start  the  door  from  the  shell,  and  a nice gui
configuration  window appears.  The first 10 gadgets ( 2*5 ) is the macros.
Here you can setup your own macros.

The next gadget is the so-called SysopInChat Action gadget.  This tells the
door  how  to  react  if a user tries to page while the sysop is in a chat.
NOTE:  If this is set to "REFUSE TO PAGE..." and the user got "Override CF"
status ( and this is enabled ) - it will bypass SysopInChat Action.

The  next  two gadget is used to specify where a possible logfile should be
placed.

The  following  gadget  is named "Use BlackList" which tells the door if it
should enable the blacklist feature.

The  same  goes  for the "Allow CF Override", this is just for the Override
feature.

"Make LogFile" is shouldn't be too hard to figure out.

"Allow Empty Reason" - if this is enabled, and the user enters nothing as a
chat-reason,  the  door  will  continue the paging process - if this is not
set, and the user enters nothing, the door will exit.

The next gadget is a cycle gadget, and is used to set the method of paging:
DisplayBeep(),  Execute  Command  or  Be  Quiet.   If  Execute  Command  is
selected, the command should be written in the below string-gadget.

"About"  shows  some vital information, you don't wanna miss this one.  :),
and "Save" just saves the configuration.  To cancel the changes, just close
the window.
    

*[ BlackList ]***************************************************************

If  you  got  some users you won't wanna chat with, just his/hers name into
the  blacklist.   The Blacklist is a file named "PowerPager.BLU" (BLU=Black
Listed  Users)  -  and  the  format  is:  
<name><CR>
..  No more no less.  Remember to enable the BlackList in the configuration
menu, if you need this feature.

*[ ChatFlag Override List ]**************************************************

Is   just  as  easy  as  with  the  blacklist.   The  file  is  just  named
"PowerPager.CFO"  (Chat  Flag  Override)  and  the  format  is  the same as
descriped above.

*[ Last words ]**************************************************************

 I want to send special greeting to Flozzy, for ideas and betatestning,
 and to Enzo for betatesting. Normal greetings to my friends in the scene.

 If you got any ideas/bug reports for PowerPager please don't hesitate to
 contact me at Sky Tower, BattleField or Warez Unlimited.

 And here at last a small tip to the avanced PowerPager user from Flozzy:
 If you want an easy'n'quick way to access the configuration window
 of PowerPager; Setup the aCP to have PowerPager as a button, so whenever
 you want to change the configuration, you just press the button in ACP.

 If you are using Sigma Express, add the following line to S:ACP.STARTUP:
 BUTTON01: PPager Config |Run >NIL: Doors:PowerPager/PowerPager >NIL:

 If you are using AmiExpress, add the following tooltypes to your ACP.info
 BUTTON_NAME.1=PPager Config
 BUTTON_COMMAND.1=Doors:PowerPager/PowerPager

*[ Version Changes ]*********************************************************

v0.12 951231 First Public Beta Release.

*[ The End ]*****************************************************************