@database April.hyper @node Main "April User Manual" @{" About this document " link AboutTheseDocs } @{" Copyright Notice " link CopyRightNotice } @{" Acknowledgements " link Acknowledgements} @{" Credits " link Credits } @{" Bugs & Suggestions " link Bugs } @{" Introduction " link Introduction } Version 0.992 PublicBeta @{" How to use April " link Usage } _____ _____ @{" Requirements " link Requirements } /| | | | | | | @{" Hard and software " link hardensoft } / | | | | | | | @{" Installation " link Installation } / | |_____| |_____| | | @{" Menus " link Menus } /---| | | \ | | @{" Write/Reply/Edit Msg " link WRE } / | | | \ | | @{" Groups/Languages " link GroupsAndLan } / | | | \ | |_____ @{" Openings & Closings " link OpenAndClose } USER MANUAL @{" Areamenu " link areamenu } @{" Namesmenu " link namesmenu } Second Manual Beta Release @{" Showmsgmenu " link showmsg } @{" Extra " link Extra } @{" Registration " link Registration } @{" Disclaimer " link Disclaimer } @{" Glossary " link glossary } @{" Index " link Index } @endnode @node AboutTheseDocs April V0.992 Copyright (c) 1992 by Nick de Jong FidoNet 2:282/309.3 All rights reserved This manual written and modified by Harry Westerman FidoNet 2:282/309 and Mark de.Jong FidoNet 2:282/309.6 All rights reserved Last changed: 16-Dec-92, 19:17:25 Read this manual thoroughly; this way you can avoid a lot of annoyance. If you have any questions about April or this document, please feel free to contact one of the authors. @endnode @node CopyrightNotice Copyright Notice THERE IS NO WARRANTY FOR THE PROGRAMS, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAMS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAMS IS WITH YOU. SHOULD THE PROGRAMS PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY REDISTRIBUTE THE PROGRAMS AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAMS (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAMS TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @endnode @node Disclaimer Disclaimer Nick de Jong, the author of April, cannot give you any warranty, either express or implied to, with respect to the fitness or merchantability of April. Nick de Jong reserves the right to not develope new versions of April in the future. Nick de Jong distributes this program, knowing of no damaging errors. He also will not be held liable for damages, inability or data loss whatsoever, by April. The user of April uses her at his/her own risk. @endnode @node Acknowledgements Acknowledgements The following names are either trademarks or the efforts of the person and/or company listed: Amiga and AmigaDOS are trademarks of Commodore-Amiga, Inc. April by Nick de Jong. ARexx by William S. Hawes. Chameleon Editor and CList by Jürgen Hermann. ConfMail by Bob Hartman, Spark Software Inc. CygnusEdPro by CygnusSoft Software. EchoMail by Jeff Rush. Fido and FidoNet are trademarks of Tom Jennings, Fido Software. MS-DOS is a trademark of Microsoft Corporation. TrapDoor by Maximilian Hantsch and Martin Laubach. Welmat by Michael C. Richardson. Amiga, AmigaDOS Commodore-Amiga Inc. ARC Raymond S. Brand, SEA Inc. ARCmail Thom Henderson, SEA Inc. ARP Scott Ballantyne, C. Heath & others BinkleyTerm Vince Perriello, Bob Hartman ConfMail Bob Hartman, Spark Software Inc. CygnusEdPro CygnusSoft Software Fido, FidoNet Tom Jennings, Fido Software Find Rodney Lewis Foozle Peer Hasselmeyer Freq Roy van der Woning GCCHost Davide Masserenti LHA Stefan Boberg LZ Jonathan Forbes ZOO Rahul Dhesi, J. Brian Waters @endnode @node Credits Credits April couldn't have got where she now is without the use of some very capable beta-testers (in random order): Harry Westerman (2:282/309.0) Pepijn van.Caspel (2:282/309.2) Mark de.Jong (2:282/309.6) Ivo Meijer (2:282/309.12) Roy van der Woning (2:283/385.7) Eric de.Jong (2:285/404.0) Raimond Verwei (2:285/404.2) Michael Visser (2:285/404.3) Jan Marten Eric Elzinga (2:282/307.0) Bard de Boer (2:282/357.17) These guys are now some walking docs of April, so if you have questions you can also write to them, when Nicks replies are getting slower ;^) @endnode @node Bugs Bugs and suggestions April has been in betatest for quite a long time and a lot of bugs have been removed. However, it is possible there are still some left. If you think you found one, please describe the bug and the things you did as exact as possible. April has been released after 2,5 years of programming, testing, bugfixing and a lot of discussions about how to create and improve a point-only programm which has everything that we missed in other point programms. It is, however, still possible that you miss something in April. If you have any suggestions, comments or bugs, feel free to write them to: Nick de.Jong at (2:282/309.3) or at his normal mail address: Aggemastate 109 8926 PB Leeuwarden The Netherlands The newest version of April is always available under the magic name APRIL for filerequest, and also for downloading at the following bbs's: Epsilon BBS 2:282/309 05109-5156 V22Bis (V32Bis RSN!) Enigma BBS 2:282/307 05107-1403 V32Bis Digital Desert 2:285/404 01184-63843 HST/V32 01184-72217 V32Bis @endnode @node Introduction INTRODUCTION April is a new FidoNet-compatible tosser and editor for the Commodore Amiga line of personal computers, specifically aimed at points. Alot of time was used to make April as user-friendly as possible, without making her too slow or too inflexible. Together with a mailer like Trapdoor or Welmat it's now simple to set up a good working pointsystem... Some of the features of April are a new format of the messagebase, a well thought-out userinterface, the speed and the enormous amount of options to configure April the way YOU want. There are quite some alternatives for April at the moment like GCCHost, Pointmanager, Foozle and Chameleon combined with TrapToss, Confmail or another tosser. But April beats them all in speed, features and ease of use. You can use the newest FidoNet-technology like 4d addressing, multibossing, linking of messages based on the MSGID en REPLY kludges. 4D-filenames like those that are supported by TrapDoor can be used, and the configuration can be done completely with a very comprehensive GUI. There is a very complete and easy to use random system available. The memory that April is allowed to use and the diskspace the messagebase is allowed to use is fully configurable, and April works in all kinds of displayformats like Interlace, Pal, NTSC, Overscan and 4 or 8 colors. @endnode @node Usage HOW TO USE APRIL In FidoNet, and other networks based on FidoNet-technology, there are several message-areas divided by subject. By calling a Bulletin Board Service (bbs) with a modem, it's possible to read those 'echomail'-areas and leave messages in them. You have to be online all the time while writing and reading your messages, so your telephonebills can get very high doing this... There is a much more convenient and cheap way to read echomail: become a point ! With a pointprogram it is possible to enter and pack electronic mail, so you can send the messages with a so called mailer to your boss. This packing is done with programs like LhA or Zip, and your mail can be shrunk most of the time to about 40% percent of it's original size, saving you a lot of time online. Messages that come back from your boss will be unpacked and moved to the right messagebases. They will be sorted, double messages will be deleted, and messages can be linked together. Afterwards, you can read and reply the new messages in a highly comfortable way, and eventually be answered. Also, private messages in the form of Netmail or Matrixmail can be written and read, and send in a couple of different ways. How does a point work, and what software is needed ? The first thing you have to do is apply for a pointnumber at a (FidoNet)node. The owner of that node will become your boss, and you will receive a number based on the nodenumber of your boss. Becoming a point will most of the time cost you some small amount of money to cover the costs of your boss, but sometimes it is free. The cycle of things you have to go through is rather simple: 1) Export the messages that have been written by you. The messages will be moved into the .PKT format, and ARCed into your outbound, ready to be sent to your boss 2) Call your boss with your mailer. Your messages will be sent, and you receive new messages. 3) Import the new messages with your tosser into the messagebase. This means unpacking, moving to the right areas, check for dupes, and place everything save on disk. 4) Now you can read your mail, and reply on messages with the maileditor. You can automate the first three points completely, certainly if you have a harddrive attached to your Amiga. With some utilities like CyberCron, or with an ordinary time-clock, you can have your mailer poll your boss automatically at certain times, and with ARexx you can let April import and export automatically too ! That way, you can start reading at once, without having to wait for the polling, importing and exporting. @endnode @node Requirements REQUIREMENTS To get a working pointsystem, you need the following programs: Program Example 1) Tosser April, GCCHost, PM, FastPoint, Foozle 2) Editor April, GCCHost, PM, Chameleon, Foozle 3) Mailer Trapdoor, Welmat 4) Arcer LZ, Zoo, Lharc, ARJ, ARC, Zip, LHA 5) Texteditor DME, Qed, CygnusEDPro, TurboText Ofcourse there are hundreds of other utilities available that can come in handy if you are a point, but you only need one of each of the above and you can be a full-blown point. To install the mailer and texteditor, just try to read the docs, and spent some time with the programs. When you really don't get it to work, ask your boss first, or try to find someone else that has been a point for a while. Why try to reinvent the wheel ? Also, the different echomailareas that are available can be a good help if you really have a problem. As you can see, April is a combined tosser AND a maileditor. How to install April on your Amiga can be read in the following chapters. First a small introduction, followed by an explanation of the basics of the program. @endnode @node hardensoft HARD & SOFTWARE: Hardware April runs on all members of the Commodore-Amiga family, independant of the Kickstart version they use. She supports PAL as well NTSC and has been tested on all processors, from 68000 to 68040. She works as well in interlace as in non-interlace. 1MB is necessary, more is recommended to make proper use of April. 1 diskdrive is enough, but to give you the comfort April can provide, you have to use a second diskdrive. A harddisk will make April run as she should, because it's much faster and has a much shorter accesstime. If you have a lot of memory available, the import of April will become much faster, because of the buffersystem she uses. Software April runs on all versions of Amigados (1.2, 1.3 and 2.0...). With version 1.2 and 1.3 the commands Endcli and Failat should be present in the C: directory. These commands are with version 2.0 already in ROM. Further, your stack should be at a minimum of 8K. A lot of crashes in version 0.99PublicBeta were caused by this ! Just type Stack 10000 in the CLI you start April from, just to be sure. @endnode @node Installation INSTALLATION: The installation of April is very simple. Extract the archive with April and copy the files 'April' and 'April.info' to your boot-disk (or better: somewhere in your path). If you still use AmigaDos version 1.2 or 1.3, you have to check if the commands 'EndCLI', 'FailAt' and 'Run' are present in your C: directory. That's all! April can be configured completly mouse-driven, so it's not needed to create or modify your configuration in a texteditor. This way it's much easier to instal April completly to your own taste. Take care that your ARCer, texteditor and mailer are somewhere in your path, and your point is ready to use. April can be started with the supported icon, or by typing 'run April' in a shell. Because April is not self-detachable you should start her with RunBack, ARun, Run or an equivalent if you want to close the Shell afterwards. As soon as you started April for the first time, she will try to load the configfile 'April.preferences' out of your current directory. she cannot find it there, she will look in the S: dir. If this configfile cannot be found, April will start with a default configuration. By changing all the configurations (at the Config-menu), you can create an environment to your own taste. @endnode @node AreaMenu AreaMenu If everything is alright, you start in the AreaMenu. Here you can find all the MessageBase-areas which are available, together with some information about these areas. Available means that you manually have created a new area in the @{"Toss configs" link TossConfig}, or that April did this herself while @{"importing" link Import}. During this action, April adds this area automaticly to the @{"AreaList" link GAreaList} and copies the settings from the fake-area @{"April_General" link GApril_General}. Each line represents an area. When there are too many areas to display, you can use the up and down cursor keys or the slider at left/right (configurable) side of the screen to scroll up and down. The screen is divided in different columns: AREA - The name of the message-area. Total - The total number of messages which are currently in an area. Unread - The total number of unread messages in an area. UnYou - Number of unread messages written to the user of an area. LastIn - The total number of messages which were imported during the last import. ToYou - The number of messages which are written to the user of an area. Rate - The average number of messages written per day in an area, calculated by the date of each message in area. @{"Flags" link Flags} - The flags of an area. If you want to know something about the screentitle in the Areamenu see: @{"Screentitles" link Screentitle} * How do I get to the @{"NamesMenu" link NamesMenu}? From the areamenu you can jump to all areas which contain messages. This can be done by double clicking on the desired area or by placing the cursor before the area and double pressing the return key (or crsr right. The third way to get there is to select an area and press the F2 key. * How do I get immediately to the @{"ShowMsgMenu" link ShowMsg}? By pressing the mouse-button combination LMB->RMB (right mousebutton pressed while pressing the leftbutton) on the desired area. Depending on the settings in the @{"AreaMenu Configs" link AreaListConfigs} you will jump to the ShowMsgMenu on the specified messagekind. Another way is to place the cursor before an area and pressing the key-combination SHIFT-RETURN (this has the same result as pressing LMB->RMB). Just like you can jump to the namesmenu you can select an area and press the F3 key to go to the ShowMsgMenu of that area. See also: @{"Project" link Project} => @{"AreaMenu" link GotoAreaMenu} @endnode @node NamesMenu NamesMenu If you want to know something about the screentitle in Namesmenu see: @{"Screentitles" link Screentitle} This is the place where you can find an overview of all the messages in an area. The columns are sorted on date and build up like this: Date - The date when the message has been written. Size - The size of a message in bytes. Flags - The flags of a messages. These can be divided in: D - Message will be deleted. P - Message is proteced from deletion and will not be thrown out of the MsgBase while importing. R - Message has been read. M - Message has been marked. E - Message will be exported during the next export. S - Message has been exported (send) From - The name of the writer of a message. To - The name of the addressed person of a message. Subject - The subject of a message. Most of the time, the subjects will be truncated because they are too long to fit on the screen. This depends on the number of columns that are used. Of course you get more space when you enlarge the overscan of the screen. If you want to see a subject which has been cut off, you'll only have to press the left-mousebutton on the subject. The date will have the same format as the list command in AmigaDos. This means that if you have a message which has been written within a week of today, they will carry the name of that day (also with "Yesterday", "Today" etc.) Without looking at the number of columns you have chosen, there is the possibility to show messages by kind. Examples of this area: only Marked, LastImport, UnRead etc... or another combination. For more info about this, we refer you to the @{"NamesMenuConfig" link NamesMenuConfig}. Note: the dates area chronically sorted, so you will first read the reply and further on the replied messages. See also: @{"Project" link Project} => @{"NamesMenu" link GotoNamesMenu} @endnode @node ShowMSG ShowMsg In this screen the message can be read. At the upper side of the screen you'll see the person who wrote the message, the person for whom the message is meant and the subject of the message. Above the from-field are the date and time the message has been written. * Scrolling of the message When you want to scroll the message (only when a message has too many lines to fit into the screen) you can use the cursor-keys. Of course you can also use the mouse. You can do this by pressing the right-button below half the screen to scroll down. If you want to scroll up, just press above half the screen. A third possibility is pressing the left/right button above the slider. You will find there some free space where you can click. This possibility has been added for quick reading, so you don't have to move you mouse pointer all the way down the screen. Finally you can use the space bar or the return key (both have the same function). If you press one of these keys, the next page of a message will be shown. If the message is at it's end, the next message (as you configed) will be read. In the second box from the left side you'll see a Tree-box. In this box you'll find for example: 9 | 1 (a) o / \ (b) O o ID (c) a) At the left- and right-top there are the messages which exist respectively back and forward in the subject-chain. It makes in this case no difference where (c) is set to. b) The tree-box itself. The thicker point is the message you have currently on screen. You can move through the tree if you have (c) set to ID and press the right or left mousbutton. Note that the tree is only an ID-chain. c) This says if the chain is on ID or on subject. You can change this by pressing the '\' key or if you have a mouse with 3 buttons, press the middle mousebutton inside the chainbox. In the third box from the left (which is also the first box from the right:^) you'll find the Browse-box. This can be divided in two arrows and the number of messages which are available on the current browse-settings forwards and backwards. If you have activated @{"AutoLoadHeader" link AutoLoadHeader} and you are in the last message of an area, then there will be no number under the arrow. Without AutoLoadHeader the arrow will be left out. This works also if you jump backwards. In the second and the third box from the left, the mousebuttons work like this: Right mousebutton - Jump to next message Left mousebutton - Jumpt to previous message Beside this the (Tear, Origin, kludges and SEEN-BYE's) can be left out of the message. If you want to configure this to your personal preferences, please take a look at the @{"ShowMsgConfig" link ShowMsgConfig}. If you want to know something about the screentitle in ShowMsg see: @{"Screentitles" link Screentitle} See also: @{"Project" link Project} => @{"ShowMsg" link GotoShowMsg} @endnode @node ScreenTitle Screentitles The titlebar in the AreaMenu displays for example the following: April Vx.xBeta -- 2199 messages in 14 areas. (a) (b) (c) a) The versionnumber of April. b) The total number of messages in all available areas in the MessageBase. c) The number of areas which are available in your MessageBase at this moment. And an example of a titlebar in the NamesMenu: AMIGA -- 392 of 392 Messages. 12 unread; 5 lastin Sat 20:49:50 (a) (b) (c) (d) (e) a) The areaname of the area you are currently in. b) The number of messages against the number of messages which are showed at this moment. In this case all messages are shown. c) The number of unread messages in this area. d) The number of LastImport messages. e) The clock which is optional. Finally an example of a titlebar in the ShowMsgMenu AMIGA -- 392 MSG 1354 bytes 47 lines ---R--S Sat 20:49:50 (a) (b) (c) (d) (e) (f) a) The areaname of the area you area currently in. b) The number of messages in this area. c) The size of the message you have currently on screen (in bytes) d) The number of lines this messages has. e) The flags of this message. f) The clock which is optional. See also @{"AreaMenu" link AreaMenu}, @{"NamesMenu" link NamesMenu} or @{"ShowMsgMenu" link ShowMsg}. @endnode @node Menus The menus in April can be seperated in: @{"Project " link Project} - From this place you can activate the most important functions in April, like @{"import" link Import} and @{"export" link Export}. @{"Config " link Config} - This is the place where April can be completely configured. @{"Message " link Message} - In this menu are several possibilities to @{"write" link WriteMSG}, @{"reply" link ReplyMSG} and @{"EditMsg" link EditMSG} a message. @{"Browse " link Browse} - In here you can jump to many places in the area. (eg. first-msg and last-msg) @{"External" link External} - This menu can be completely configured by yourself. You can add/edit your own menu-items. (eg to poll for your mail) @endnode @node Project Project @TOC Menus The Project Menu consists of 9 items: @{"AreaMenu " link AreaMenu } - Go to the AreaMenu. @{"NamesMenu " link NamesMenu} - Go to the NamesMenu of an area. @{"ShowMsg " link ShowMsg } - Go to the ShowMsgMenu of an area. @{"Import " link Import } - Give April the command to start importing. @{"Export " link Export } - Same as Import, but now for exporting messages. @{"Rescan Areas" link Rescan } - Update the info of an area (or areas) About - Some info about the program and author. Register - Register yourself for the complete April-package. You can create a message or print that message on paper. Quit - Goodbye -> Exit! See also the menus @{"Config" link Config}, @{"Message" link Message}, @{"Browse" link Browse} and @{"External" link External}. @endnode @node GotoAreaMenu @{"Project" link Project} => AreaMenu @TOC Project If you want to go to the AreaMenu, you will have to choose this menu-item. This item works of course when you are in ShowMsgMenu or NamesMenu. If you choose this menuitem when you already are in the AreaMenu, the screen will be refreshed. See also: @{"AreaMenu" link AreaMenu} @endnode @node GotoNamesMenu @{"Project" link Project} => NamesMenu @TOC Project If you choose the menuitem @{"NamesMenu" link NamesMenu}, April will go to the NamesMenu of the area you are currently in. If you wish however to go to the NamesMenu when you are the AreaMenu, you'll first have to select the area you want to go to. Then you have to select this menu-item. When you choose the NamesMenu-item when you are already in this NamesMenu, the screen will be refreshed. @endnode @node GotoShowMsg @{"Project" link Project} => ShowMsg @TOC Project This menu-item can be chosen when you are in the NamesMenu or AreaMenu environment. Just as if you wanted to go from AreaMenu -> NamesMenu you just have to select an area and active this menu-item. And to keep it simple you'll have to do the same from NamesMenu to ShowMsgMenu. See for more info : @{"ShowMsg" link ShowMsg} @endnode @node Import @{"Project" link Project} => Import @TOC Project In the inbound you can find mail or other files. We can find the following files: The packets - The unpacked mail (extension *.PKT) The archives - The packed mail (extension like *.we or *.mo1 etc.). Frequests - Files which have been freqqed from a BBS (extension normally *.LHA, *.LZH, *.ZIP or *.ARC) Files other than mail are moved to the directory configured in the @{"configs" link TossConfig}. If the flag 'backup' is set, the first thing April does is copy the packets and mail-archives to a configured backup-directory. Is also the flag 'AreaList Backup' set, then the arealist will also be backed up in case it gets munged somehow. April will automatically use the April.arealist.backup if the April.arealist seems to be broken. If 'Unpack all at once' in the @{"Tosser Config" link TossConfig} is activated, all archives will first be unpacked in the temporary-directory before April starts importing them. If not, all archives will be unpacked and imported in the order that April finds them in the @{"Inbound" link GHolddirInbound} directory. If April finds a packet in the inbound or temp-dir, April tries to read as many messages it can load. This can be configured in the @{"Tosser Config" link TossConfig} with the name 'MaxSegMem'. If April has loaded it's buffer full, it starts importing. The messages stay in memory but will be put in another part of the memory, which is known under the name 'MaxScanMem'. Everytime this memory-part is full, all messages will be saved to the their areas. So, if you make this memory-part very small...then April has to write a lot of times, which decreases speed. If MaxScanMem is full, April starts with sorting the messages of the first area which is at the upper-side of your screen. If this has been done, April will check the following things: - check for duplicate messages - is the number of new messages + the number of the old messages larger than the maximum number of messages allowed in this area? - is the size of new messages + the size of old messages larger than the maximum size allowed for this area? (The MaxMBNr and MaxMBSize, which are respectively the maximum number of messages and the maximum size of those messages, can be configured in the @{"AreaList Config" link AreaListConfigs}) If one of the above checks is true, then April will remove as many messages from this area until they are both false. If we have 'old messages' of an earlier session of this import, then they will be moved to the @{"BadMsg-area" link GBad_Msg}, where they will be imported. This last method is also configurable, which means that you can also remove these messages at once... (so they won't be imported). If April finds messages which are for an area that currently doesn't exist, she will create this new area and imports the messages in that new area. The settings of this new area will be copied from the fake-area @{"April_General" link GApril_General}. April will place an '*' before each area where messages are imported or were imported. Note: It is possible to abort the import-session. This can be done by pressing the ESC-key. @endnode @node Export @{"Project" link Project} => Export @TOC Project When you activate the export, April will look at all areas. When the export-flag is set, then April will look inside the @{"header" link GHeader-file} of this area for export-messages. While exporting, a window will be shown on screen with some information about the messages which are exported. The @{"mailer" link GMailer} looks while his mailevent into the @{"outbound" link GOutDirOutbound} directory for files with the right format which he can send. We can seperate the normal mail in the following files: *.PKT - Not packed mail (@{"netmail" link GNetmail}) *.we0...- Packed mail (can also be @{"netmail" link GNetmail}) And of course the files, which point to the above files (for example: *.FLO, *.CLO etc...) For information about these formats we refer to the Trapdoor manual. Note: Because the export flags of all messages are not influenced by an import, you may also use import before you export. @endnode @node Config Config Menu In the Config menu april can be completely configured to the wishes of the user. The Config Menu can be devided into the following 14 items: @{"AreaList " link AreaListConfigs } - The complete configuration of each areas. @{"Tosser " link TossConfig } - This is the configuration for the @{"import" link Import}. @{"General " link GeneralConfig } - Here you'll find the general dirs and options. @{"Screen " link ScreenConfig } - Configuration of palette and screensize. @{"External Prg" link ExternalConfig } - ConfigWindow where you can add/edit extern programs to the 'External Menu'. @{"PrivUser " link PrivUser } - ConfigWindow where new people can be added with their point address; for quick reference while writing a message. @{"AreaGroups " link GroupEdit } - Add/Edit/Delete Groups @{"Languages " link GroupLan } - Add/Edit/Delete Languages @{"Origins " link OriginEdit } - Configurations of the origins. @{"Openings " link OpeningsEdit } - Configurations of opening sentences in messages. @{"Closings " link ClosingsEdit } - Same as Openings, but now for closing sentences. @{"AreaMenu " link AreaMenuConfig } - ConfigWindow for the AreaMenu. @{"NamesMenu " link NamesMenuConfig } - ConfigWindow for the NamesMenu. @{"ShowMsg " link ShowMsgConfig } - ConfigWindow for the ShowMsgMenu. @{"Save Configs" link SaveConfigs} - Saves config of April. See also the menus @{"Project" link Project}, @{"Message" link Message}, @{"Browse" link Browse} and @{"External" link External}. @endnode @node AreaListConfigs @{"Config" link Config} => AreaList @TOC Config In this ConfigWindow you can change the data of all areas. This can be done by add, edit, copy, sort, move, etc. On the right side you'll find the areas with next to them their nodenumbers. If you enter here for the first time, only 3 areas are active. These areas area: April_General, NetMail and BadMsg. Note: April_General cannot store any messages. It is a fake area for your preferences only. By double pressing the return key or double clicking the left mousebutton on an area (or right cursor), you can edit the selected area. If you wish to use the functions at the left side of the window, you'll first have to select the area and after that the function you want to use. The function are: @{"Add " link Add } - Add an area. @{"Edit " link Edit } - Change an existing area. @{"Delete " link Delete } - Delete an area. @{"Move " link Move } - Move an area. @{"Copy " link Copy } - Copy all data of an area. @{"PCopy " link PCopy } - Copy only parts of data of area. @{"All " link All } - Select all. @{"None " link None } - Unselect all. @{"Pattern" link Pattern} - Select on specified pattern. @{"Sort " link Sort } - Sor the areas. @{"Make " link Make } - Make an empty message-file @{"No use " link } - Currently not in use (future) @{"BBSInfo" link BBSInfo} - BBSInfo of an area. If you wish to leave this config-window, click on the Close-gadget or with the right mousebutton outside the window. See for more info about the use of areas : @{"Import" link Import} @endnode @node Add @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Add @TOC AreaList When this gadget is chosen, a window with stringgadgets and a few options will appear. The data, except the AreaName, of this new area is all copied from @{"April_General" link GApril_General}. We have 6 stringgadgets, which are: AreaName - Name of the area. Domain - The name of the Net of this area. (eg FidoNet) UserName - The name of the user (Multi-user) Directory - The directory where the mail for this area will be placed. Font - The font which should be used for this area (in ShowMsg) BBSNode - NodeNumber of the BBS where this area comes from (your Boss) (eg 2:282/309) Next of these stringgadgets are the following options: NetMail - If this one is set, it should be a @{"Netmail" link GNetmail} area. Bad_Msg - If this one is set, this area should be a @{"Bad_Msg" link GBad_Msg} area. Int. Area - Is set if this is an international area. Currently not supported. Read_Only - Set this option, if you want to make this area read_only (so no writing will be allowed) Reflow Quotes- Reflow quotes per paragraph. Use Privat Node - Set this option, if you want to use this area for @{"Privat Node" link }. At the bottom of this window you will find two stringgadgets: MaxMBNr - Maximum number of messages allowed in this area. MaxMBSize - Maximum size of the messagefiles of this area. (Given in KiloBytes) It's only possible to change these figures while creating an area. At the right side of this window, a gadget @{"Edit Group" link GroupEdit} and a list are visible. If you haven't changed any Groups-config, the list will only contain the Group 'General'. This list has been included into this window to give you the opportunity to say which Group should be linked to what area. Just select that Group and April will link it to this area. If you want to change the groups press the @{"Edit Group" link GroupEdit} gadget. For more information about the terms mentioned earlier, we refer to the explanation of the @{"Import" link Import}. The Gadets which remain are @{"Origins" link OriginEdit}, @{"Openings" link OpeningsEdit}, @{"ClosingsEdit" link Closings} and @{"BBSInfo" link BBSInfo}. They have the same function as these gadgets in the AreaList-window. @endnode @node Edit @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Edit @TOC AreaList To let this window appear, you first have to select an area once and then choose 'Edit'. You can also double click on an area or if you use the cursor, double RETURN. Multi-edit is also possible. If want to do that, choose more than one area and choose the 'Edit' function. The Edit Window differs almost nothing from the Add Window. Except the stringgadget with the name of the area doesn't appear and it's not possible to change @{"MaxMBNr" link GMaxMBnr} and @{"MaxMBSize" link GMaxMBsize}. This has been done for practical reasons, you can specify the size of an area only when ADDing one ! If you really want to change these sizes, you have to use the program Jean which is available with the registered April package. For more detailed info see @{"AreaList" link AreaListConfigs} => @{"Add" link Add} @endnode @node Delete @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Delete @TOC AreaList Do you want to remove one or more areas, then select these area(s) and press the 'Delete' gadget. Note: You can't get deleted areas back, like with normal deleted messages. @endnode @node Move @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Move @TOC AreaList Move is a function which can be used to change the order of areas to your personal feeling. This is handy if you want to place all areas of their kind to eachother (eg with all AMIGA-areas) or for all areas which should go to the same floppy, so you get minimal disk-changing while importing. The function works as follows: You have currently the areas: April_General AMIGA AMY_POINT OUR_LOCAL_AREA If you want to get the areas AMY_POINT and OUR_LOCAL_AREA before the area AMIGA, you have to select these two areas and press the 'Move' gadget. April removes these areas from the arealist and keeps them in the move-buffer. You will get a requester with the message that you have to double-click on the area where you want to put these areas in front. In this case you have to double click the 'area' @{"April_General" link GApril_General} because that is the area where you want to put the two areas behind. As a result of this you get the list: April_General AMY_POINT OUR_LOCAL_AREA AMIGA Another way to change the arealist is to use the @{"Sort" link Sort} function. Note: another way to get an area into the movebuffer is by pressing the mousecombination LMB->RMB. This has the same effect as selecting an area and selecting the 'Move' gadget See also: @{"Move" link ExtMove} in the @{"ExternalConfig" link ExternalConfig} @endnode @node Copy @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Copy @TOC AreaList Do you want to copy all the data of an area to one or more areas, then you will have to choose this function. The first thing you'll have to do is select the area(s) where you want to copy the data to. Then you have to press the 'Copy' gadget. April will give a requester which says that you now have to double click the area where the data should come from. See also: @{"PartCopy" link PCopy} @endnode @node PCopy @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => PCopy @TOC AreaList If you don't want to copy all the data to one or more areas, you need this function. Just as the copy function you first need to choose the area(s) where the data should go to. Then select the 'PCopy' function. A window will appear with 5 gadgets, which stand for the data of the Domain, UserName, Directory, Font and BBSNode. You can select the gadget of the data you only want to copy. You can do this with the function-keys or with your mouse. If you have selected your desired gadget(s), you need to close the window by pressing the close-window gadget or by pressing the rightmousebutton outside the window. Finally select the area from which you want to copy your data. That's all... See also: @{"Copy" link Copy} @endnode @node All @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => All @TOC AreaList If you select this function, all areas will be selected. @endnode @node None @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => None @TOC AreaList If you select this function, all areas will be unselected. @endnode @node Pattern @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Pattern @TOC AreaList With Pattern you can select areas on a pattern. A few examples are: *amiga* - Select all areas which have the string 'amiga' in their name. Upper or lower case doesn't matter. *am???.028* - Selects all areas which names look like 'am???.028', where '???' stands for 3 characters. Next to these two basic-terms, there is the boolean function OR: *.028*|*.30* - This pattern will select all areas which end on '.028' or '.30'. You can see that the '|' character is used for the OR function. Note: Pattern works on comoete lines so '*2:282/*' can also be used. If you want to select areas, put an '*' behind them to ignore the address. If we sum up all these function we know the following characters stand for: '*' - Everything will be selected '?' - 1 character will be selected '|' - The OR-function @endnode @node Sort @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Sort @TOC AreaList With this function you can sort several areas. You can sort the whole list or only a few. The only thing you have to do is select the areas you want to sort, and press the 'Sort' gadget. @endnode @node Make @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => Make @TOC AreaList By selecting one or more areas and choose this function, April will create a @{"message-file" link GMessage-file}. This file has the size of the MaxMBSize for the area. If this number is 400, then a file will be generated of 400 Kb filled with nulls. This function is added to April so you won't get a scattered HardDisk or floppy. Normally an area will get larger while importing, with the result that the @{"message-file" link GMessage-file} enlarges also, but fragments your disk at the same time. @endnode @node BBSInfo @{"Config" link Config} => @{"AreaList" link AreaListConfigs} => BBSInfo @TOC AreaList If you wanted to @{"add" link Add} a new area with a nodenummer which is unknown to April, a BBSInfo Window will popup. This window will also popup if you selected this function from the AreaList Window. This BBSInfo Window has been created to support the use of Multi-bossing. This way every area will be linked with a BBSInfo. For those areas with the same BBSInfo, all data will be general. So if you change something, it changes for all linked BBS' If we look into the window, we can see that the @{"nodenumber" link GNodenumber} and @{"domain" link GDomain} of this new area appear at the top of the window. Then we can see 7 stringgadgets: BBSName - Name of the @{"BBS" link GBBS} where this area comes from. Boss Name - Name of the Boss of the BBS named above. @{"AreaFix " link GAreaFix} - Name of the area-linkprogram of this BBS. @{"PointNet" link GFakeNet} - PointNet number of this BBS @{"PointNr " link GPointNr} - Your pointnumber which your Boss gave you. Pack - General call which April will use to pack mail. UnPack - General call of the unpacker which April will use to unpack the mail. This happens before @{"importing" link Import}. (currently UnPack of April_General only is used!) Next to these stringgadgets, there are three options: 2D Adressing - Send your mail in a packetformat according to FTS-0001. Otherwise it will be sent in FSC-00039 format... then your seenby and path won't contain any references to your pointnet either. Pack NetMail - Set this option, if you want to send your @{"NetMail" link GNetmail} packed. 4D FileNames - All archives, flo-filenames etc. will get the 4D filename format as described in the manual of TrapDoor. (eg. 2.282.309.mo0) See also : @{"Add" link Add} and @{"Edit" link Edit} @endnode @node TossConfig @{"Config" link Config} => TossConfig @TOC Config This Config Window, where you can configure everything which has to do with the Import and Export, can be devided in 3 parts: @{"BeforeImport " link BeforeImport} - Options which get active before April starts importing @{"Import " link TossImport } - Options for the (Import). @{"StringGadgets" link TossStrings } - The stringgadgets of this window. @endnode @node BeforeImport @{"TossConfig" link TossConfig} => BeforeImport @TOC TossConfig Under the title "Before import:" we find: Backup - If you set this option, then April will copy the inbound to your backup dir. Only packets and archives will be copied. Files will be moved to the filedir. AreaList Backup - Each time you activate import, the Arealist.april will be backupped. So if you lose this file, then April will use this backup-arealist and makes a new Arealist.april. Kill BadMsgArea - If you want that April should clear all messages of Bad_Msg area before import, set this option. Unpack all at once - April will unpack all archives before she starts importing. See also: @{"Import" link Import} Show Import - If you haven't set this flag, you won't see the import-session. For more practical information about these options: @{"Import" link Import} @endnode @node TossImport @{"TossConfig" link TossConfig} => Import @TOC TossConfig Three options for the import itself: Strip RE: - The "RE:" at the beginning of each subject will get cleared, if you set this option. Note: This option is also used in the FromTo Window Protect ToYou - If you set this option then April will set the protected flag of each message written to the user of an area. Kill Dups - If this option is set, dups are killed in stead of moved to the BadMail area. @{"duplicate msgs" link GDups} Kill too old - Messages which have to be transferred to a BadMsg area (because there are to many messages which are imported once) will be deleted (killed). Force 1.3 (un)pack - CON: windows will be openened on your WorkBench (only for extracting & packing while import/export). Test EchoAddr In - Will test your incomming mail with the node given in your AreaConfig. (Does not work properly yet!) Show Export Window - The small window in the center of your screen while exporting will not appear if this option is set. @endnode @node TossStrings @{"TossConfig" link TossConfig} => StringGadgets @TOC TossConfig The Tosser Window has 7 stringgagets, of which there are 2 for numbers: MaxScanMem - The size of a piece of memory (in Kb) which will be used for storing messages while importing. If you make this size small, the import would take more sessions than if you made this size large. MaxSegMem - This is the size of a piece of memory where April stores the packets. For more practical information about the above options see : @{"Import" link Import} The other stringgadgets are: HoldDir - This is a directory where the unimported mail stays. April will look in this directory for mail to import. (eg. 'Mail:Inbound/') OutDir - This is a directory where your outgoing mail will be placed. (eg. 'Mail:Outbound/') BackupDir - A directory where your mail (archives and .pkt-files) is backupped before importing. See also @{"Backup directory" link GBackupDirectory} FileDir - This is the directory where the frequests or other files will be moved to during the backup-session. TempDir - This is a directory where the *.PKTs of an archive will be placed while unpacking and importing. @endnode @node GeneralConfig General Config The GeneralConfig is also build with stringgadgets and options for the general use of April: @{"StringGadgets" link GeneralStrings} - descriptions of the stringgadgets @{"Opties " link GeneralOptions} - same as above, but now for the options See also: @{"TossConfig" link TossConfig} @endnode @node GeneralStrings @{"GeneralConfig" link GeneralConfig} => StringGadgets @TOC GeneralConfig Editor - Name of the editor where you want to write your messages. EditFile - Name of the file of your written message (including path) Suffix - Argument which will be placed behind the Editor and EditFile. An example: < Editor > < EditFile > < Suffix > Command: Ced RAM:April.MSG -sticky Some editors don't support a suffix. If so, leave the suffix empty. Priority - This is the priority April is running on. Needs no change under normal circumstances. ConfigDir - This is the directory where all the config-files of April will be placed. (like April.arealist, April.PrivUser, etc.) Note: April.prefs should be in current dir or s: LogDir - This is the name of the directory where April places her log-file. ArchiveDir - The directory for archived messages. See also : @{"Archive" link Archive} Font - The general font, which April uses for the screens. (Note: the font can also be set for each area) =0.994> Nodelist - The directory where April can find a Nodelist (Traplist.library required) See also: @{"GeneralConfig" link GeneralConfig} - @{"Options" link GeneralOptions} @endnode @node GeneralOptions @{"GeneralConfig" link GeneralConfig} => Options @TOC GeneralConfig Next to the stringgadgets in the GeneralConfig Window we find some options, which area: -WorkBench to front before edit If your editor doesn't have its own custom screen and it wants to open its window on the WorkBench Screen, then you have to choose this option. Everytime you will write/edit/reply a message, the WorkBench Screen will come to front. - April to front after edit If your editor has its own custom screen or if you have set the 'WorkBench to front before edit' option, you have to set this option. If this option is set and your editor has closed its window or screen, the April screen will come to front. The other options area: Skip NamesMenu - If this option is set, April will skip the NamesMenu. The only way to go the NamesMenu then, is by pressing F2 or selecting the 'NamesMenu'-item in the 'Project Menu' or LMB->RMB in AreaMenu. NOTE: LMB->RMB and 2 * LMB are switched if this option is set. Flash - When April wants to warn you, she will give a screen-flash. Request on Quit - April will now ask if you want to quit. LogLevel - This level tells April how many comments to show in the log file (April.log). The loglevel can be set from 0 - 10; Level 0 - All comments will be in the log. Level 10 - Only the comments of opening April and closing April will be in the log. (use log only to debug, levels are not yet very well implemented) Archive FlowLines - Archive messages will be provided with @{"FlowLines", GFlowLines} (like paths/seenby's etc.) Sliders on left - All sliders in April will appear on the left side. No Prefs. Save on Quit - April will not save the preferences when it quits. The only way do save them, is by activating this function manually. NOTE: If you press the shortcut: CTRL-Q, April will quit instantaniously without saving any config or preferences file. Check name without pnt - Imagine your name contains a '.' and someone writes a message to you, April won't see that message as a message written to you. With this option set, April will see your name without points also as a message written to you. (this is functional if you f.e. want to color messages written to you in NamesMenu. This way Nick de.Jong and Nick de Jong are the same for April. See also: @{"NamesMenuConfig" link NamesMenuConfig} Don't ask - If this option is set, April won't ask you, for example, if you're sure you want to delete x number of messages. This counts also for some other questions. And then we have some options specially for Aprils clock: Clock - If this is set, the clock will appear in your titlebar Clock: seconds - The seconds will be shown. day - The day will be shown. memory - Now April will show all your memory (CHIP + FAST mem) See also: @{"GeneralConfig" link GeneralConfig} => @{"StringGadgets" link GeneralStrings} @endnode @node ScreenConfig @{"Config" link Config} => ScreenConfig @TOC Config In this Config Window you can change the colors and size of April her screen. In the middle of the window are 4 boxes with stand for the colors used for the screen. Left of these boxes you find 3 sliders with which you can adjust each color. Each slider stands for a color, respectively red, green and blue. On the left side of this configuration window area 6 gadgets. Each gadget has an 8 color buffer and will be saved in the configs. All gadgets contain a color-pattern which can be overwritten by your own color-pattern. At the right side of the window we find 5 gadgets: Interlace - Change to an interlaced screen. Max ScreenSize - When you choose this option and you choose ReOpen, the April screen will have the same size as the WorkBench Screen (overscan). 8 colors - April will open a screen with 8 colors. If your Amiga has no real fast-ram, the output will be slowed down. Swap Colors - Change color 1 to color 0. Great for using a dark background, and still have '3d'windows and gadgets. Warm Colors - Some parts (like the titlebar and slider) will get another color. This color is taken from the current color-pattern. At the bottem of this window are 3 gadgets which area: ResetPalette - Choose this gadget if you want to reset your palette to an earlier palette. SavePalette - This one is for saving your current palette to one of the 6 gadgets at the left side of the window. First select this gadget, then one of those 6 permanent palette gadget. ReOpen - Closes the screen of April and reopens it. The ConfigWindow will appear again always again after a reopen. If you close the window after changing some options or sizes, then April will automaticly activate reopen. @endnode @node ExternalConfig @{"Config" link Config} => External Config @TOC Config This configurationwindow is directly linked with the @{"External Menu" link External}. All parts of that menu can be changed in this ConfigWindow. The operation of this window is about the same as that of the @{"AreaListConfig" link AreaListConfigs}. You have to select here also the menu-item before you choose one of the functions at the left side of the window. When double-click on a menu-item then the Edit function is activated for that selected area. The function which are known for this configuration area: @{"Add " link ExtAdd } - Add a new menu-item. @{"Edit " link ExtEdit } - Edit an old menu-item. @{"Delete " link ExtDelete } - Delete a menu-item. @{"Move " link ExtMove } - Move one or more menu-items. @{"SortMv " link ExtSortMv } - Move and Sort one or more items @{"Sort " link ExtSort } - Sort all or only the selected areas. @{"All " link ExtAll } - Select all. @{"None " link ExtNone } - Unselect all. @{"Pattern" link ExtPattern} - Select by pattern. The externalConfig-file has a normal ASCII format. So it is possible to edit in an editor. @endnode @node ExtAdd @{"ExternalConfig" link ExternalConfig} => Add @TOC ExternalConfig When you choose this function, a small window will appear with at the top a few stringgadgets an below some options. The stringgadgets area: MenuName - This is the name as it will appear in the @{"External Menu" link External}. ShortCut - The character which will be pressed in combination with the ALT-key to call this menu-item. Command - The command which will be executed when this menu-item is chosen. An example for these stringgadgets are: MenuName @{"TopChart " link } ShortCut @{"t " link} Command @{"Mail:TopChart " link} Next to these stringgadgets we find the following options: Program uses Worbench screen - The Workbench Screen will popup to front if this flag has been set. Program uses Custom screen - After using this program, the April Screen will come to front. Program uses CLI window - This option means that your window needs a CLI/Shell for its output. Background run - The program will be detached from the April-task. If set, April will work simultaneous with the executed program. (You'll still have to use Run though!) I think it's clear to you all, that you cannot set the first two options at the same time. @endnode @node ExtEdit @{"ExternalConfig" link ExternalConfig} => Edit @TOC ExternalConfig When you have double selected a menuitem or if you have chosen this function while you had selected a menuitem, a window will appear (as with @{"Add" link ExtAdd}) The difference between the Add-window and this window is that the stringgadgets are already filled. For the meaning of the stringgadgets, see the @{"Add" link ExtAdd}-function. @endnode @node ExtDelete @{"ExternalConfig" link ExternalConfig} => Delete @TOC ExternalConfig If you wish to delete one or more menuitems, you first have to select the menuitem(s). The selected areas will be deleted when you press the 'Delete' gadget. Note: Deleted menuitems cannot be undeleted as with messages! @endnode @node ExtMove @{"ExternalConfig" link ExternalConfig} => Move @TOC ExternalConfig With this function you can change the order of the menuitems. You first have to select the menuitems you want to move before you select the function 'Move'. April will ask you if you want to double-click the menuitem where the selected menuitems have to get after. Another way to move areas is to use the left-right combination with your mouse. When you do this combination above an area, this area will be moved to the move-buffer. The 'Move' gadgets will light. You may repeat the above for several areas. Just double-click the menuitem where the menuitems have to get after and the 'Move' function will be deactivated. The move-function can also be aborted by pressing the ESC key. The areas which are in the move-buffer will be placed in the list again. See also: @{"Move" link Move} in the @{"AreaListConfig" link AreaListConfigs} @endnode @node ExtSort @{"ExternalConfig" link ExternalConfig} => Sort @TOC External With this function, you can sort the all menuitems or only the selected menuitems. Zie for more info: @{"AreaListConfig" link AreaListConfigs} => @{"Sort" link Sort} @endnode @node ExtSortMv @{"ExternalConfig" link ExternalConfig} => SortMove @TOC ExternalConfig When you want to sort the move-buffer (see @{"Move" link ExtMove}) while moving, you only have to activate this function. These areas will be sorted when you place them back in the list. See also: @{"Move" link ExtMove}(Move) @endnode @node ExtAll @{"ExternalConfig" link ExternalConfig} => All @TOC ExternalConfig If you activate this function, all menuitems will be selected. See also: @{"None" link ExtNone} @endnode @node ExtNone @{"ExternalConfig" link ExternalConfig} => None @TOC ExternalConfig If this function has been selected, all menuitems will be unselected. See also: @{"All" link ExtAll} @endnode @node ExtPattern @{"ExternalConfig" link ExternalConfig} => Pattern @TOC ExternalConfig With this, you can select on a given pattern. See for more detailed info: @{"AreaListConfig" link AreaListConfigs} => @{"Pattern" link Pattern} @endnode @node PrivUser @{"Config" link Config} => PrivUser @TOC Config The PrivUser is a list with the names of the people you write often. In this case it's usefull to remember their name and @{"nodenumber" link GNodeNumber}, so they can easily be redrawn from this list while writing a msg. You can get the info of the specified user in the From-To Window (see @{"WriteMsg" link WriteMsg}) while pressing the SHIFT-RETURN combination. The PrivUser Window has the same environment as the @{"ExternalConfig" link ExternalConfig} Window. The division of this window is as follows: @{"Add " link PrivAdd } - Add a new name. @{"Edit " link PrivEdit } - Change a an already existing name. @{"Delete " link PrivDelete } - Delete a name. @{"Move " link PrivMove } - Move 1 or more names. @{"ShortMv" link PrivSortMv } - Move and sort. @{"Sort " link PrivSort } - Sort the names. @{"All " link PrivAll } - Select all. @{"None " link PrivNone } - Unselect all. @{"Pattern" link PrivPattern} - Select with a pattern. See also: @{"ExternalConfig" link ExternalConfig} @endnode @node PrivAdd @{"PrivUserConfig" link PrivUser} => Add @TOC PrivUser When you select the 'Add' gadget, a window with 7 string gadgets will appear: FirstName - This is the firstname of the added person. LastName - And the lastname of this person. Address - The @{"nodenumber" link GNodeNumber} of this person. NickName - The NickName... When someone has a large name and his normal firstname is difficult to be retrieved from that name, a nickname is handy. This name will then also retrieve the real name of this user, so it can be placed in the From-To Window. (See also: @{"WriteMsg" link WriteMsg}) Example : James Micheal Smith NickName: JMS YoName - This is the name you call this person. This is also the name which will be placed above the msg when you reply on his letter. (like "Hello Micheal") YoName: Micheal (otherwise it would be James) Group - The name of people who are in a group. This is very handy if you want to write a @{"CarbonCopy" link CarbonCopy} only to these person. eg only the members of your club. Group: YourClub Domain - This is the @{"Domain" link GDomain} where the added name is active. (like FidoNet) See also: @{"ExternalConfig" link ExternalConfig} => @{"Add" link ExtAdd} @endnode @node PrivEdit @{"PrivUserConfig" link PrivUser} => Edit @TOC PrivUser Just as with the @{"ExternalConfig" link ExternalConfig}, a window will appear with the same contents as the @{"Add" link PrivAdd} window of this Config. Only now everything has been filled in, according to the selected name. See also: @{"Add" link PrivAdd} @endnode @node PrivDelete @{"PrivUserConfig" link PrivUser} => Delete @TOC PrivUser With this function, you can delete PrivUser names. Select a name and press the 'Delete' gadget. Note: Deleted names cannot be undeleted! See also: @{"AreaListConfig" link AreaListConfigs} => @{"Delete" link Delete} @endnode @node PrivMove @{"PrivUserConfig" link PrivUser} => Move @TOC PrivUser With this function you can change the order of the names in the list. See for detailed info: @{"ExternalConfig" link ExternalConfig} => @{"Move" link ExtMove} @endnode @node PrivSortMv @{"PrivUserConfig" link PrivUser} => SortMove @TOC PrivUser When you want to sort the move-buffer while moving, press this gadget. The names will then be sorted when they area placed back. See also: @{"ExternalConfig" link ExternalConfig} => @{"SortMove" link ExtSortMv} @endnode @node PrivSort @{"PrivUserConfig" link PrivUser} => Sort @TOC PrivUser With this function you can sort all or several names. First select the areas you want to sort, then press the 'Sort' gadget. See also: @{"AreaListConfig" link AreaListConfigs} => @{"Sort" link Sort} @endnode @node PrivAll @{"PrivUserConfig" link PrivUser} => All @TOC PrivUser If you activate this function, all names in the PrivUser list will be selected. See also: @{"None" link PrivNone} @endnode @node PrivNone @{"PrivUserConfig" link PrivUser} => None @TOC PrivUser All names in the PrivUser list will be unselected when smashing this gadget. See also: @{"All" link PrivAll} @endnode @node PrivPattern @{"PrivUserConfig" link PrivUser} => Pattern @TOC PrivUser You can select names with a given pattern. See for detailed info: @{"AreaListConfig" link AreaListConfigs} => @{"Pattern" link Pattern} @endnode @node AreaMenuConfig @{"Config" link Config} => AreaMenuConfig @TOC Config In this window we find 6 options. Each option stands for a message-kind where April jumps to when you select the LMB->RMB combination. (leftmousebutton->rightmousebutton) or by double clicking, depends on your config. From the AreaMenu we can jump with the LMB->RMB to the following combinations: First unread MSG - First unread message. First unread MSG ToYou - First unread message to you. First LastImport - First @{"LastImport" link GLastImport} message. First unread LastImport - First unread @{"LastImport" link GLastImport} message. Lastread - The last message you read. Lastread +1 - 1 message further as the above message. The other options which can be set are: Bold LastImport - Makes lines bold of areas with an LastImport-flag. Bold UnRead - Makes lines Unread of areas which contain UnRead msgs. Bold UnRead ToYou - Same as 'Bold Unread' but now for UnRead msgs to you. No leading nills - Data in AreaMenu will only show the numbers. (eg. ' 10' in stead of '0010') See also: @{"NamesMenuConfig" link NamesMenuConfig} and @{"ShowMsgConfig" link ShowMsgConfig} @endnode @node NamesMenuConfig @{"Config" link Config} => NamesMenuConfig @TOC Config This Configuration Window contains, just as the @{"AreaMenuConfig window" link AreaMenuConfig} only options. These options can be devided in: Show Date - Show the date column. Show Flag - Show the @{"flags" link NamesMenu} of all messages. Show Size - Show the size (in bytes) of each message. * Unread - With this you have the possibility to place a '*' * LastImport for each message with is UnRead/LastImport/ToYou * ToYou C Unread - With these 3 options you can color the messages-lines C LastImport of the messages which are UnRead/LastImport/ToYou. C ToYou Show All - Show in the NamesMenu only the messages of which Show Marked the selected options has been set. For more info about this see: @{"NamesMenu" link NamesMenu} @endnode @node ShowMsgConfig @{"Config" link Config} => ShowMsgConfig @TOC Config The ShowMsgConfig contains a lot of options. Not all options are related to how messages are showed. Jump to a next/previous message-kind, the way each message has to be quoted and other things like buffered msg-reading, for example, relate to those options. All options are: Show Kludge - The @{"Kludge" link GKludge} will be visible. Show seenby - The @{"seen-by" link GSeenBy} will be visible. Show tear - The @{"tearline" link GTearline} will be visible. Show origin - The @{"origin" link GOrigin} will be visible. Kludge color - In combination with "Show Kludge", the kludge will get another color. Quote color - Now the quotes will be colored Font extras - The underline/bold/italic etc...will be made visible. @{"Collapse Quotes" link CollapseQuotes} - The quotes in a message will be collapsed. No columns - Don't test for column wordwrap. No Reflow - Don't reflow your messages (only for exported messages) The following options are very handy for those who want to jump to next/previous messages on message-kind: AND not OR - If this option is set, the messages have to comply with the options set below. Otherwise, April will look for another message which complies with these options, before it will be showed. So if it is set, and you select Unread and ToYou, then you will read all messages that are BOTH. When you unselect the gagdet, you will read every message that is Unread or that is already Read but is addressed to you. Normal - Option for normal messages. Selected - Option for selected messages Marked - Option for Marked messages Showed - Option for messages which are showed in the NamesMenu LastImport - Option for messages which were imported last. Unread - Option for unread messages. To You - Option for messages which are written to you. Next to these options, which indicate where you want to jump to, there are the Quote-options. These options say what you want to quote in a message. We find: RQuote kludge - The replied message will contain kludges. RQuote seenby - The above message will also contain seenby's RQuote tear - The tearline will be quoted. RQuote origin - And finally the origin, which will be placed in the message. Finally there are those last options: Chain Subject - Previous/Next message will be done on subject. (NOT on ID) NoErrorReq - Don't show error requesters. Slider - If you set this option, the slider will be placed in the ShowMsg. ExtraTitle - @{"AutoLoad HDR " link AutoLoadHeader} - Gives you the possibility to jump to the next/previous area while you are in ShowMsg. If you press Next Msg at the end of an area, you will go to the next area. April uses the way you are reading at the moment, if you are reading only Unread messages, April will send you to the next area with Unread messages left ! Show NamesMenu - @{"MsgBuffer" link MsgBuffer} - This option makes buffered message loading possible. A second program is started at a low priority that continuously keeps filling a buffer in memory with the next messages in the messagebase and starts to restyle them also. When you hit Next Msg, you will see the msg on screen almost instantaniously ! April doesn't have to look it up on the (hard)drive. The first stringgadget is connected to the MsgBuffer option and has only then a function. The size should be given in KiloBytes, and specifies the maximum amount of memory your buffer is allowed to be. 30K is enough for normal use. See also: @{"AreaMenuConfig" link AreaMenuConfig} and @{"NamesMenuConfig" link NamesMenuConfig} @endnode @node CollapseQuotes @{"ShowMsgConfig" link ShowMsgConfig} => CollapseQuotes @TOC Config If this function is activated, the quotes of all messages will be brought back to a minimum. This way large masses of quotes are avoided and a message with minimal quotes will be shown. To give you an example of Collapse Quotes...first look at the normal quotes in a message: PdB> HJ> That document is nothing compared with this guide. PdB> PdB> Well, that is just what i mean. After a few replies it will look like: PdB> HJ> PdB> HJ> PdB> Nice Quote this is... PdB> HJ> PdB> HJ> PdB> HJ> PdB> HJ> It's not that long... PdB> HJ> PdB> PdB> HJ> PdB> I don't agree with you. PdB> HJ> PdB> HJ> You can say what you want, but it's getting shorter PdB> HJ> all the way. PdB> PdB> What i can't imagine is why they still use long-quotes. If you have selected the Collapse Quotes option, the above message would look like: PdB>> Nice Quote this is... HJ>> It's not that long... PdB>> I don't agree with you. HJ>> You can say what you want, but it's getting shorter HJ>> all the way. PdB> What i can't imagine is why they still use long-quotes. It's for the user to decide wether he's going to use this option or not. @endnode @node AutoLoadHeader @{"ShowMsgConfig" link ShowMsgConfig} => AutoLoadHeader @TOC ShowMsgConfig If you set this option and you are at the end of an area while you are in ShowMsg, you can go automaticly to the next area. April will, just as with each message, check the @{"Browse-options" link Browse} with the flags of the message. If you, for example, in area read unread message and you get at the end (or beginning) of an area, April will automaticly go to the next/previous area and load the first/last unread message. This doesn't have to be an area which is next to the current one, April will show a brief "Skipping x areas" and jumps to the next one with Unread messages. @endnode @node MsgBuffer @{"ShowMsgConfig" link ShowMsgConfig} => MsgBuffer @TOC ShowMsgConfig If this option for buffered loading is set, every time you go to the ShowMsgMenu, a few messages will be already loaded and restyled. This way you don't have to wait for loading and restyling the next or previous messages. Connected to this option is the stringgadget "Buffersize". This is the size of the memory April may use for loading and restyle messages. gadget. The size is given in Kilobytes. When you switch back to the NamesMenu, April will stop the MsgBuffer- task from loading and restyling messages. @endnode @node SaveConfigs @{"Config" link Config} => Save Configs @TOC Config This function will only be activated when you quit April or if you choose this menu-item. A window will appear with all the configuration-files. If any changes have been made to a configuration, they will be saved. This way, no configuration will be needlessly saved. If an error occurd while loading or saving, "ERROR" string will stay for a few seconds, so if you have a fast harddisk it will attract your attention. @endnode @node Message @{"Menus" link Menus} => Message @TOC Menus The Message Menu can be devided in the following 15 items: @{"Write MSG " link WriteMSG } - Write a message @{"Reply MSG " link ReplyMSG } - Reply a message @{"Edit MSG " link EditMSG } - Edit/change a your message @{"Edit Header " link EditHeader } - Edit/chage the header of your message @{"Forward " link Forward } - Forward a message to another area @{"Reply & Forward" link ReplyForward } - Reply and forward a message @{"Archive >" link Archive } - Archive a message @{"Delete MSG " link DeleteMSG } - Delete a message @{"Set MSG Flags " link SetMSGFlags } - Change the flags of a message @{"Catch up " link CatchUp } - Changes the flags of all messages @{"Select pattern " link SelectPattern} - Search for patterns in text/subject etc... @{"Select MSG " link SelectMSG } - Select a message @{"Select Marked " link SelectMarked } - Select the marked message @{"Select All " link SelectAll } - Select all messages @{"Select None " link UnselectAll } - Unselect all messages @{"Rip Origin " link RipOrigin } - Rip the origin of someones message @{"Add to PrivUser" link AddtoPrivUser} - Add a new name to your PrivUser. @{"MSG info " link MSGInfo } - Get some info about a message. @endnode @node MSGInfo @{"MessageMenu" link Message} => MSGInfo If you're in ShowMsg and you select this function from Message-Menu or by pressing "?", a window will popup, with some information about the message currently on screen. If you have a Nodelist, give in the @{"GeneralConfigs" link GeneralConfig} the name of the directory where April should find this list. (Traplist.library required) If April finds a Nodelist, she will say where the message originaly came from (like BBSName, Boss etc) @endnode @node RipOrigin @{"MessageMenu" link Message} => Rip Origin Rip Origin is a small but usefull function. Suppose you find someones origin very nice/great/havoc and you don't want to type the whole origin into the Origin-List (lazy? 8), you should use this function. Rip Origin will rip the origin of someones message and places it in your Origin list. @endnode @node CatchUp @{"MessageMenu" link Message} => Catch up This function will set all READ flags of all the messages in the area you have activate. This means that if you haven't read a lot of messages in area, April will update that area with this function by setting all the READ flags. And it looks as if you have read all messages. That's all... @endnode @node WriteMSG @{"MessageMenu" link Message} => Write a MSG @TOC Message With this function it's possible to generate a new message. You can write a new message in each of the three parts of the program (AreaMenu, NamesMenu, ShowMsg) If this function has been activated, the editor (which has been configured in the GeneralConfigs) will be loaded. In this editor you can write your new message, save it to disk and leave again. When you have quited your editor, 2 windows will appear on the April Screen: @{"The FromTo Window " link FromToWindow} - This is the place where you can give in the data of the new message. @{"The PrivUser Window" link PrivUser } - This is the window with your PrivUser, where you can choose the destination. See also: @{"Reply Msg" link ReplyMSG} and @{"Edit MSG" link EditMSG} @endnode @node FromToWindow @{"MessageMenu" link Message} => The FromTo Window @TOC Message In this window you can give in the data about the person where your message should be sent to, and some extra info about your message. We should make a division between @{"NetMail" link GNetmail} en @{"EchoMail" link GEchomail}. (eg. Netmail needs a nodenumber and echomail not) The window looks with echomail like: 4 stringgadgets: From - The sender of this message (you). Will be automaticly filled in. To - The name of the person for whome this message is ment. Subject - The subject of this message. Origin - May be filled in to your own feeling. If you have an origin-list, April will take a random origin from that list. If this list is empty, April will fill in her own origin. Note: if you press SHIFT-RETURN while your cursor is in the Origin stringgadget, April will place another origin in the stringgadget. If you press SHIFT-RETURN in the 'To' filed, April will look in the PrivUser and complete the name and ev. fill in the address. If 'To' Holds your 'AreaFix' Name (see BBSInfo) of the BBSInfo of this area, April will fill in all fields (using password etc.) Then there is the option: Privat - Says that this is private message. NEVER use this in normal echomail ! Use it only with permission in eg. a local area. The devision of the Netmail Window differs not much from that of the EchoMail Window. The differences are: - 2 extra stringgadgets for the From and To addresses. - 4 extra options for a messages, which are: Crash - If set, the message will be exported and stored in a separte packet, so you can send your message(s) directly with your mailer. Crash to Boss - Your message will now be crashed via your Boss. This way, you don't have to make contact yourself, but your Boss' BBS will make contact for you. Please notify your Boss when you're going to use this option ! File Attach - Opens a file-requester, with which you can say what file you want to attach to message. Is only allowed with Crashmail. @{"Carbon Copy" link CarbonCopy} - With this option, you can send a message to several persons. You should use the PrivUser when you use this option. Finally, we have the gadgets: Edit - with which you can change your just-written message. PrivUser - The PrivUser window will appear or disappear. Use the shortcut AMIGA-Space for switching between the PrivUser window and the FromToWindow. If you think the that the windows don't have the right position or size, just change them to your own taste. April will remember the positions and sizes of each window for the next time you're going to call the windows and place them in the preferences file. April will then save the preferences file while leaving or if you choose the menu-item 'Save Configs'. @endnode @node CarbonCopy @{"FromTo Window" link FromToWindow} => CarbonCopy @TOC FromToWindow If this option is set, you can send a message/file-attach to several persons. The only condition is that those persons to which the message have to be sent should be in the PrivUser-list. How does CarbonCopy work? Just set this option and choose the persons to which the message should be sent. It doesn't matter what the 'To' or 'Address' stringgadgets say, because April won't do anything with them if this options is set. When desired, you may change some other options. Finally, just press the OK gadget and April will take care of the rest... @endnode @node ReplyMSG @{"MessageMenu" link Message} => ReplyMSG @TOC Message With this function you can reply a message. Basicly the same as WriteMsg, but now the message which you want to reply to, will be quoted. The initials of the original writer will be added before each quoted line, to indicate which parts of your new message have been quoted. The name of the addressee and the subject will be filled in also. See also: @{"Write MSG" link WriteMSG} @endnode @node EditMsg @{"MessageMenu" link Message} => EditMsg @TOC Message When you have written a message earlier on, you can change that message with this function. The date and time will also be changed to the current date and time. April will set the export flag of each message which was edited, except if the message was generated by you. See also: @{"EditHeader" link EditHeader} @endnode @node EditHeader @{"MessageMenu" link Message} => EditHeader @TOC Message This function is basicly the same as EditMsg, but now you can't edit the message. With this function it's only possible to change the data of the @{"FromToWindow" link FromToWindow} (except if you choose the 'Edit' option). See also: @{"EditMsg" link EditMSG} @endnode @node Forward @{"MessageMenu" link Message} => Forward @TOC Message This function copies a message to another area, along with some info about that message (such as original writer etc...) See also: @{"Reply & Forward" link ReplyForward} @endnode @node ReplyForward @{"MessageMenu" link Message} => Reply & Forward @TOC Message Basicly the same as the forward function, but now you're abled to reply on the message, before it's going to be forwarded. This way, it's possible to reply an echomail message in the netmail for example. See also: @{"Reply" link ReplyMSG} and @{"Forward" link Forward} @endnode @node Archive @{"MessageMenu" link Message} => Archiveren @TOC Message The menu-item 'Archive' can be devided in a submenu with the following items: Archive - If you choose this item, the message(s) which has been selected, or, if you're in ShowMsg, the message currently on screen, will be archived. Each area has it's own archive-file (eg. Archive_AMIGA) If you don't want any @{"flowlines" link GFlowLines} in your archive, just unset the "Archive FlowLines" flag in the @{"GeneralConfig" link GeneralConfig}. Archive as... - A file-requester will appear on screen. Fill in the directory and filename where the archived message(s) should be saved. Arc Archive - This function archives your message and packs it also. (by eg. Lha or Arc) Print MSG - Your message will be send to the printer. @endnode @node DeleteMSG @{"MessageMenu" link Message} => Delete MSG @TOC Message With this function you can delete messages in the @{"NamesMenu" link NamesMenu} and @{"ShowMsg" link ShowMsg}. In the @{"NamesMenu" link NamesMenu} you have to select the message and then this menu-item. In @{"ShowMsg" link ShowMsg} you can delete a message by pressing the DEL-key or, like in the NameMenu, by choosing this menu-item. In the NamesMenu April will give a warning if you're sure you want to delete the message(s). However, if you're in ShowMsg, April will just set the DEL-flag of the message. If you have accidentally set the DEL-flag, it's possible to get the message back by selecting that message and calling the SetMsgFlags routine and RESET the Delete-flag. If you have deleted 1 of more messages, they won't be visible with the normal settings. Do you want however to see these messages, set the Delete-flag in the @{"NamesMenuConfig" link NamesMenuConfig}. The 'All' flag in the @{"NamesMenuConfig" link NamesMenuConfig} does NOT mean that the deleted messages are visible! The messages of which the delete-flag is set, will really be deleted when you are importing new messages in the regarding area. This means that you have activated the import function or that you have written/edited a message in that area. See also: @{"SetMsgFlags" link SetMsgFlags} @endnode @node SetMSGFlags @{"MessageMenu" link Message} => Set MSG flags @TOC Message The window of this function can be called by selecting one or more names. In ShowMsg it will always appear. Other ways to let this window appear in ShowMsg is by pressing the '*' on your keypad or by clicking with the middle mousebutton on the flags in the title of ShowMsg. 2 kinds of SetMsgFlags windows do exist. The window in ShowMsg speaks for itself, but the window in the @{"NamesMenu" link NamesMenu} needs some more explanation. This window has 2 rows of gadgets: Above the first row you find an R which stands for RESET; And above the second row an S which stands for SET; If you choose SET, the message of which the flag hasn't been set will be set. With RESET the opposite. Both SET and RESET will swap the chosen flags This way it's possible to swap flags of the selected messages: e.g. all marked messages will be 'unmarked' and 'unmarked' messages will be marked. See also: @{"Delete MSG" link DeleteMSG} @endnode @node SelectPattern @{"MessageMenu" link Message} => Select Pattern / Search With this function you can select on a pattern. The pattern checked can be flags, strings (e.g. from) or date. *Flags At left side of the Search window you find all flags which can be checked. Next to these flags there are two rows of options. For example: (Un)Set/X Delete [] [] etc... The first (left) option says if a checked message must be Set or Unset. The second gadget is a kind of "Don't care" gadget. If this gadget is set, it doesn't matter if the first gadget has been set. An example: (Un)Set/X Delete [V] [] This means that the message must have set the deleted flag. (Un)Set/X Delete [] [V] This way the search routine won't check this flag. Even if the first option has been set. *Strings There are 4 stringgadgets: From, To, Subject and String. These first 3 stringsgadgets are patterns for the From, To and subject. The fourth (stringgadget 'String') is a pattern for the message itself. *Date If you just opened the Search window, all date-gadgets will look like: Date [ ALL ] [**] [*********] [****] a b c d a) Says how should be checked (ALL/SINCE/UPTO/ON eg. 12 September 1992) b) The day c) The month d) The year You can change the months and condition by using: Left mousebutton - go forward (eg months: January, february etc..) Right mousebutton - go backwards (eg monts: January, December etc..) So it could look like: Date [ ON ] [12] [September ] [1992] If you have set the date-gadgets like this, and you haven't touched the other patterns (like flags and strings), April will select all messages which were written on 12 September 1992. Well, we have discussed all kinds of patterns in this window, but how to start searching? At the bottom of the screen are 3 gadgets: Search gadget - April will check all patterns with the messages. Because this includes 'String' also, April will have to load the message itself. This means that it takes a little while, before she got finished. Select gadget - April will check all patterns except the 'String'- pattern. This is the quick version of this routine, because April won't check each message. Both routines will result in selecting the messages which comply with the patterns in the Search-window. Abort gadget - If you press this gadget while searching, April will abort the Search function. There are different ways of selecting a message. Default is always: First unselect all, Select if found. Here are all options, which can be found at the right-bottom of the Search-window: First unselect all - April will first unselect all messages. This means no message will be selected while starting. Select if found - April will Select (Highlight) the message which complies with the patterns. Unselect if found - All message which compy with the patterns will be unselected. This option cannot be used with "First unselect all" or "Select if found". Search selected only - April will only check the messages which are selected (highlighted) Mark found entries - All message which comply with the patterns will be marked. @endnode @node SelectMSG @{"MessageMenu" link Message} => (Un)Select MSG @TOC Message With this function you can select a message, or by using this function repeatedly, unselecting one. @endnode @node SelectMarked @{"MessageMenu" link Message} => Select Marked @TOC Message Needs not much explanation: All marked message will be selected. See also: @{"Select All" link SelectAll} @endnode @node SelectAll @{"MessageMenu" link Message} => Select All @TOC Message With this function you can select all messages an area. Independent if you're in ShowMsg or in the NamesMenu. See also: @{"Unselect All" link UnselectAll} @endnode @node UnselectAll @{"MessageMenu" link Message} => Select None @TOC Message Does the opposite of the SelectAll function: unselect all messages, indepentent if you're in ShowMsg or in the NamesMenu. See also: @{"Select All" link SelectAll} @endnode @node AddToPrivUser @{"MessageMenu" link Message} => Add To PrivUser @TOC Message This function copies the names of the writer of a messages to your PrivUser list. Activate AddToPrivUser by: - selecting one or more messages in the @{"NamesMenu" link NamesMenu} - pressing the shortcut in the @{"NamesMenu" link NamesMenu} or @{"ShowMsg" link ShowMsg} - choosing this menu-item See also: @{"PrivUser" link PrivUser} @endnode @node Browse @{"Menus" link Menus} => Browse @TOC Menus This menu gives you the possibility to jump to several places in an area. We can devide this menu in: First msg - Jump to first message in an area; Last msg - Jump to last message in an area. First in chain - If you want to read a whole @{"chain" link GChain}, this function brings you to the first message in a chain. Last in chain - Same as "First in chain", but now for last message in a @{"chain" link GChain}. First selected - If you have selected several messages, this function jumps to the first selected message. Last selected - Same as "First selected", but now for last message. First marked - This function brings you to the first message of which the mark flags has been set. Last marked - Same as "First Marked", but now for last message. Swap Page forward - April will jump one page (screen) further into a message. Or, if this isn't possible: next message Swap Page back - Same as above, but now backwards. ID/Subject chain - Choose this function if you want to switch between ID and Subject in a chain. How you're currently chaining can be seen in the Browse box (2nd box from the right) Previous Area - Jumps to NamesMenu or ShowMsgMenu of a previous area. Next Area - Same as "Previous Area", but now for a next area. Menu back - This way, you will force April to go a Menu back. (ShowMsgMenu->NamesMenu->AreaMenu->Quit) @endnode @node External @{"Menus" link Menus} => External @TOC Menus This Menu has been specially added for external programms, like mailers and request-tools. The shortcut for each added menu-item is the ALT-key and not, like other menus, the AMIGA-key. For configuration of the External Menu i refer to the explanation of the @{"ExternalConfig" link ExternalConfig}. @endnode @node WRE Write, Reply and Edit a message The three basic functions for taking part in a discussion are: @{"Write Msg" link WriteMsg} - Add a new message to an area. @{"Reply Msg" link ReplyMsg} - Reply to an already written message. @{"Edit Msg " link EditMsg } - Change/Edit a message written by yourself. See also: @{"Message Menu" link Message} @endnode @node GroupsAndLan Groups & Languages Each area is part of a group of areas. You can have a 'fun' group, a 'test' group, a 'general', 'local' group, etc. Each group has its own origins, openings, closings and a language field. The 'General' group and 'English' language are defaults. @{"Languages:" link GroupLan} Each language can have it's own names for days, months etc. These days and months are visible in the area in which they are used. @{"Groups:" link GroupEdit} Each new Group which is added has the standard language 'English'. It's possible to change this to another language with @{"GroupEdit" link GroupEdit}. Each area must be linked to a group. The language which will be used in that area, depents on the language of the Group of that area. See also: See further: @{"GroupEdit" link GroupEdit}, @{"AreaListConfig" link AreaListConfigs} @endnode @node OpenAndClose Openings & Closings With these terms, we mean the sentences at the beginning and at the end of each message. How to create the sentences see: @{"Openings" link OpeningsEdit} - Add/Edit Openings @{"Closings" link ClosingsEdit} - Add/Edit Closings See also: @{"Origins" link OriginEdit} @endnode @node GroupEdit @{"Config" link Config} => GroupEdit You find yourself in the editor for Groups. The currently available groups are displayed in the list. With the slider, which is at the right side of the list, you can scroll (if not every group can be displayed). At the left side of the window are 3 gadget: @{" Add " link GroupAdd } - Add a new Group to the current list; @{" Edit " link GroupEdit2 } - Edit an already existing group; @{" Delete " link GroupDel } - Delete a group from the list; If you want to @{"Edit" link GroupEdit} or @{"Delete" link GroupDel} a group, first select a group followed by the desired gadget (or cursor-right to Edit). @endnode @node GroupAdd @{"Config" link Config} => @{"GroupEdit" link GroupEdit} => Add If you've selected the Add gadget, a window will appear in the middle of your screen. The window has been divided in three parts: GroupName - The name of the group which has to be added. Language list - List of all languages currently available. Gadgets: @{"Origins " link OriginEdit } - Add/Edit/Delete origins; @{"Openings" link OpeningsEdit} - Add/Edit... your opening sentences in your messages; @{"Closings" link ClosingsEdit} - Add/Edit... your closing sentences; @{"Language" link GroupLan } - Add/Edit/Delete languages; Each Language has it's own origins, Openings and Closings. Before you want to change one of these, select from the list a language. Then press the desired gadget (Origings, Openings or Closings) If you want to add a new @{"Language" link GroupsAndLan} you only have to press that gadget and the Language window will popup. However, if you want to edit a language, first select the gadget you want to change and then the Language gadget. With the GroupName stringgadget you have the ability to add a new Group. Just fill in a new name for that group, select a language from the list, edit one of the first 3 gadgets an exit. If everything is alright, your new group is visible in the @{"GroupEdit" link GroupEdit} window. See also: @{"GroupEdit" link GroupEdit} => @{"Edit" link GroupEdit2} @endnode @node GroupEdit2 @{"Config" link Config} => @{"GroupEdit" link GroupEdit} => Edit Well, not much to tell about this window. It's basicly the same as the @{"Add" link GroupAdd} Window, with the exception that the GroupName has been filled in and the language which is linked with this group has been selected already. For more info: @{"GroupEdit" link GroupEdit} => @{"Add" link GroupAdd} @endnode @node GroupDel @{"Config" link Config} => @{"GroupEdit" link GroupEdit} => Delete With this function you can delete a group from the Group-list. First select the group you want to delete, followed by the Delete gadget. Origins, openings and closings will disappear, the language will remain until deleted. WARNING: A deleted group cannot be undeleted! @endnode @node OriginEdit @{"Config" link Config} => @{"GroupAdd" link GroupAdd} => OriginEdit If you have configured the rest of April, this window will look familiar to you. It has the same interface as the @{"PrivUserConfig" link PrivUser}, @{"ExternalConfig" link ExternalConfig}, etc. If you press cursor-right, you can add/edit an origin. It's possible to walk through the origins with the cursor keys. The cursor will disappear if you press cursor-left at the first character of the origin. See also: @{"OpeningsEdit" link OpeningsEdit} and @{"ClosingsEdit" link ClosingsEdit} @endnode @node OpeningsEdit @{"Config" link Config} => @{"GroupAdd" link GroupAdd} => OpeningsEdit What do we mean with Openings? With Openings we mean the opening sentences your editor normally writes for you while replying a message. (eg. "On 5 October you wrote to me:") Now it's possible to add several opening sentences, so April will randomly take one Opening sentence from the list while replying a message. The interface for changing the Openings list is the same as @{"PrivUserConfig" link PrivUser}, @{"ExternalConfig" link ExternalConfig} etc. If you press the cursor-right key (or the Add/Edit gadget) a window will appear. Here you can add/edit your opening sentences. If you're done, press the right mousebutton outside the window or press the close gadget. Your changed opening will be visible in the list. Each return is represented by a square-character. Different from the OriginEdit is that you have the ability to use codes in your Openings-sentences. A little example: You add a new Opening like: --- New Opening --- Hi %tof ! On %day %date at %time you wrote to %to about '%subject', the following lines: ------------------- When you reply to a message, the above lines will be converted to: --- Replied MSG --- Hi John ! On Saturday 3 October '92 at 20:35:41 you wrote to me about 'Nice proggy!', the following lines: JM> JM>...etc ------------------- For the other supported codes, see: @{"Codes" link Codes} See also: @{"ClosingsEdit" link ClosingsEdit} @endnode @node Codes @{"Config" link Config} =>@{"GroupEdit" link GroupEdit} => Codes The full supported code-list is as followes: Code Which means... Example ============--=======================--================================= %from => from name => Nick de.Jong %fromf => from firstname => Nick %froml => from lastname => de.Jong %to => to name => John McCall (me) %tof => to firstname => John (me) %tol => to lastname => McCall (me) %me => your name => Peter Dillenger %mef => your firstname => Peter %mel => your lastname => Dillenger %subject => subject %subj => subject %date => complete date => 23 june '92 / june 23rd %dates => date short => 23-oct-92 / Oct-23-92 %dateday => day if last week else equals date => wednesday / %date %year => year => 1992 %yy => year => 92 %month => month name => october %mm => month nr => 10 %day => day name => wednesday %dd => day nr => 23 %time => time => 18:45:25 %Mtime => time => 6:45:25 PM %hour => hour => 18 %min => minutes => 45 %sec => seconds => 25 %area => AreaName => Amy_Point %msgfile => TextFile of msg => T:April.MSGfile %Naddr => Addr of user => 2:282/309.3 %FromAddr => Addr of user => 2:282/309.3 (same as above) %ToAddr => Addr of To-user => 2:282/307.5 suffix  nr => max nr chars => (eg %subj15): subject will be cut at 15 characters. ============--=======================--================================= The '%to' code changes to the "me"-string if you reply to a message written to you. This string is unlike daynames and months, currently not linked with the language of a group. (will be fixed in newer versions) All the codes used in April can also be used in the commands of the External Menu, but they will be the codes work only when you're in ShowMsg. See also: @{"OpeningsEdit" link OpeningsEdit} and @{"ClosingsEdit" link ClosingsEdit} @endnode @node ClosingsEdit @{"Config" link Config} => @{"GroupAdd" link GroupAdd} => ClosingsEdit What do we mean with Closings? Closings are sentences which will be placed at the end of each message. These sentences allow you to say goodbye to the person you wrote to. An example of a closing is: --- New Closing --- Goodbye! %me ------------------- which will be converted to: --- Replied MSG --- Goodbye! Peter ------------------- For the other supported codes, see: @{"Codes" link Codes} For the userinterface and codes see: @{"OpeningsEdit" link OpeningsEdit} @endnode @node GroupLan @{"Config" link Config} => @{"GroupAdd" link GroupAdd} => Languages If have pressed this gadget, a window will appear. This window is about the same as the @{"GroupEdit" link GroupEdit} window. The only difference is the kind of list (here languages). I only discuss the @{"Add" link LanguageEdit} function. The Edit function is almost exact the same. The Delete function can be used by first selecting a language an then pressing the Delete gadget. See also: @{"Language Add/Edit" link LanguageEdit} @endnode @node LanguageEdit @{"Config" link Config} => @{"GroupAdd" link GroupAdd} => @{"Languages" link GroupLan} => Edit If you've pressed the Add or Edit gadget, a large window with a lot of stringgadget will appear. At the top of the window you'll find the name of the language you're editing. The division of this window is as follows: - At the left side of the window, 4 count stringgadgets. cnt#1 can be for example 'st' which will be printed behind the '1'. Like:'The 1st of May' - In the center of the window, 7 stringgadgets. Each stringgadget represents a weekday (Day #1 is 'Sunday' or an equivalent) - At the right side of the window, 12 stringgadgets. 12 gadgets which represent 12 monts (Month #1 is 'January' or an equivalent) Finally 2 options: American dates - Standard date like : 23-oct-92 With this option set, date like: Oct-23-92 Use Counts - Use the 'st', 'nd', 'rd' Am. dates (see above): Standard (example) : Oct 23 92 With this option set: Oct 23rd 92 See: @{"Languages" link GroupLan} @endnode @node Flags Flags The flags of a message are: D - Message will be deleted. P - Message is proteced from deletion and will not be thrown out of the MsgBase. R - Message has been read. M - Message has been marked. E - Message will be exported while an export-session. S - Messages has been exported (send) The flags of each message can be changed with @{"SetMsgFlags" link SetMsgFlags} See also: @{"NamesMenu" link NamesMenu} The flags of an area are: N - Area is for Netmail messages. B - Area is for Badmail messages (corrupted messages) W - This is an international area (WorldWide). Currently only an indicator. R - This is a read-only area. Q - Area uses Reflow Quotes P - Area is used for Privat node. E - Area has exported messages. I - Area has last import messages. L - This is the LastRead Area. See also: @{"AreaMenu" link AreaMenu} @endnode @node Rescan @{"Project" link Project} => Rescan Areas Rescan has been added to April to simply update the info of an area. This info can be found in your AreaMenu. Another reason to add this routine was that it was annoying to add all the areas by hand again in your AreaList config if you lost the @{"April.arealist" link Garealist.april}. Now you do a simple Rescan, and April will look on disk for all *_msg and *_hdr files and makes a new April.Arealist for you with updated information on the number of messages, etc. Really handy if you had a crash for example. Well, if you take a look at the Rescan window you'll find 4 gadgets and 4 options. Each gadget will activate a different kind of rescan. Here are the first 2 gadgets (functions): Rescan - Rescan will only read the top the @{"header file" link GHeader-file}. In that part of the header file, some counted data has been stored already. This function is faster, but less profound as DeepRescan. DeepRescan - DeepRescan reads the whole @{"header file" link GHeader-file} and counts all necessary data. These functions scan only the areas which are currently active. This means that areas which are not in the Arealist, will not be rescanned. The other 2 gadgets, will not only read the active areas, but also the areas which will be found in a given directory: DirRescan - Scannes 1 or more directories; found areas will be scanned with the Rescan function (see above). DeepDirRescan - Same as DirRescan except that found areas will be scanned with the DeepRescan function (see above). How does the Rescan routine know what directory (or directories) to scan? At the right side of the Rescan-window are 3 options. These options are: from all areas - April will scan the directories of all areas. from April_General - April will scan only the directory given in the fake-area 'April_General' from [ ] - April will scan only the directory given in the stringgadget. Only one of these options can be set. Finally there is 1 option left: 'No Requesters' If you set this option, the Rescan routine won't give any error messages(/requesters) while scanning. @endnode @node ARexx @TOC Extra ARexx April has a small but very usefull ARexx port. This port can be called with the name "APRILREXX". April regocnizes 4 commands: Import, Export, Quit and Version. An example of an AmigaDos script: ---ADos-script----------------- run April waitforport "APRILREXX" rx rexx:April.rexx ------------------------------- And April.rexx: ---April.rexx------------------ /* Small April Rexx script */ address APRILREXX import address APRILREXX quit exit ------------------------------- @endnode @node ExtraFonts @TOC Extra ExtraFonts Well, you've certainly seen them: the *GREAT* kind of words. No, the word "GREAT" is just an example for one of the extrafonts which April supports. If you have set the flag "ExtraFonts" in your @{"ShowMsgConfigs" link ShowMsgConfig}, April will show this word in Bold. The '*' at both sides of the word will be stripped. To give you a brief example of the ExtraFonts April supports, here are: *GREAT* - The word "GREAT" will be showed in Bold _GREAT_ - The word "GREAT" will be showed Underlined /GREAT/ - The word "GREAT" will be showed Italic #GREAT# - The word "GREAT" will be showed in Complement. The above methods are only used for single words. If you want to show whole lines in for example bold, you have to use the following method: $*This is a line in bold$* The '$' before the '*' character says that Bold should continue until we find another '$*'. Another example: $/This line is in italic$/ Italic stays on until we find the characters '$/'. If you actived for example italic and you won't turn it off, April will automaticly stop the italic when it bumps onto an empty line, or if the line changes from quote: -An example------------------ $/Here is italic on, and will stay on until it bumps into an empty line. Here is italic off, because there was an empty line. ----------------------------- -Another example------------- JM> $/Here is italic on, and will stay on until it bumps into a JM> different quote. DH> Yep, here is italic off again, because this is a different quote. ----------------------------- Finally there is a method which may NOT be used in normal @{"EchoMail" link GEchoMail}: you can also make a complement character (block) by using the extended ascii code 186 (ALT-B). @endnode @node Extra Extra information Some info cannot be placed under an existing part of this manual. All these extra info or features can be found here: @{"ARexx " link ARexx } - Communicate with April via an ARexx port. @{"ExtraFonts" link ExtraFonts} - Use Italic, Bold..etc.. in your messages. @endnode @node Registration * Registration for the complete April Pointpackage * April has been released after 2,5 years of programming, testing, bugfixing and a lot of discussions about how to create and improve a point-only programm which has everything that we missed in other point programms. This means that we think it's reasonable to ask a registration fee in the amount of one of the following currencies: 30 Dutch Guilders April Development 30 Deutsch Marks Aggemastate 109 20 US $ to 8926 PB Leeuwarden 25 Swiss Francs The Netherlands 15 English Pounds POSTBANK Giro account: 5581224 With your registration you help to ensure further development of April, you will receive support and some nice tools specially made for April. Please allow 2 to 6 weeks for delivery. ********************************************** If you want to register, please fill in the whole registration-form. Don't forget to set the option how you want to pay your registration fee. This window has 3 gadgets: Create Msg - April will create a message in your netmail-directory. Print Msg - The whole registration form will be printed. Exit - With this gadget you can exit the registration-form. April won't make a message nor will it print the form. @endnode @node G2D4D "Glossary" @TOC glossary 2D/4D Adressing 2D and 4D are addressing formats of messages. In the beginning of EchoMail there were no points. Later when points were added, 2D addressing wasn't enough, and need arose for 4d addressing. April implements the FSC-00039 document, which is used by most of the current tossers in FidoNet. The format describes how the *.PKT file is built technically. @endnode @node GApril_General "Glossary" @TOC glossary April_General This is a fake area. The area April_General is only used for data transfer to new areas. This occurs while importing. This 'area' cannot contain any messages. @endnode @node GApril.arealist "Glossary" @TOC glossary April.arealist This is a file that contains all the information of all areas you are connected to with April. The file is used by april to get a quick overview of all the areas, and contains also the information about the size an area can get, where April can find the area on disk and where messages have to be send when you enter a message in a certain area. April makes this arealist itself in the config dir (that you can specify, proposed is s:) and makes (optional) a backup of this important file before each import. @endnode @node GApril.prefs "Glossary" @TOC glossary April.prefs This is a file that will be put in your s: directory, and contains all your preferences of April. Also, it contains the place where to look for the April.arealist @endnode @node GArchive "Glossary" @TOC glossary Archive A function that can archive messages to a textfile or print them on the printer that is attached to your Amiga. Each area has it's own archive-file called Archive_Areaname. @endnode @node GArea "Glossary" @TOC glossary Area An area contains echomailmessages or netmailmessages about one subject. The subject of such a conference is most of the time obvious from the name of the area, but the moderator wil finally decide the subject of the area. An echomailarea has a fixed tagname that all nodes carrying that area have to use. @endnode @node GAreaFix "Glossary" @TOC glossary AreaFix A general name for a program which the BBS of your Boss runs to give you the ability to connect and disconnect areas. It could, however, also have another name. @endnode @node GAreamenu "Glossary" @TOC glossary AreaMenu This is one of the three 'menus' in April, this one gives you an overview of all connected message-areas in a list. That way, you can choose the area you want to read in. Also some extra information like the number of unread messages, or the total amount of messages that one area contains is available here. @endnode @node GBackupDirectory "Glossary" @TOC glossary Backup-directory This is a directory that you can specify. April can copy all the incoming mail in the inbound-directory to this backup directory before she starts importing. If something goes wrong, then you can just start over by copying the files from the backup directory to the inbound ! This is all optional ofcourse, but very usefull. @endnode @node GBad_Msg "Glossary" @TOC glossary Bad_Msg This is a special echomail-area where messages end up that aren't technically correct. Messages that got truncated during their travels through the network, messages without a decent origin or subject, they all end up there. Also, duplicate messages can (optionally) go to this area, and it is also used as the area for messages that are 'too old for importing'. That means that there wasn't any room in the area itself for the messages, for example when you receive 500 messages at one time, while you specified that only 400 messages are allowed in that area. 100 will go to the bad_msgs then, so they are not lost ! The reason why a message went to Bad_msgs is mentioned in the subject of the message. @endnode @node GBBS "Glossary" @TOC glossary BBS Bulletin Board System, a computersystem with a modem connected that is available for other persons to call in. Most of the time the BBS will be available 24 hours a day, and contains echomail, files, online games en all kinds of bulletins. When there is a mailer installed 'in front' of the bbs, a bbs can become a node in a network and exchange net- and echomailmessages with other nodes. @endnode @node GBossSysop "Glossary" @TOC glossary Boss/Sysop The person that put a lot of money and time is his hobby to start up and keep his bbs running. Per definition, this is a nice guy or gal that will always be willing to help the users with their problems, or help them to become a point. Through you boss you receive your mail, and you send your messages into the rest of the network through him. @endnode @node GChain "Glossary" @TOC glossary Chain A serie of message about one subject. It contains a whole chain of messages and replies.. April detects those chains in two ways: If messages have the same 'subject'-line they are considered to be part of a chain, and further the MSGID en SUBJECT kludges are used to build a complete tree of messages. You can always see this tree in the upper right part of the ShowMsgmenu. By reading such a chain, you can easily follow a discussion for example. @endnode @node GDups "Glossary" @TOC glossary Dups These are duplicate messages. Normally, messages are sent only once through the network, but Murphy hits when you least expect him :-) Throught faults in the routing-scheme of the messages or sysop-errors, messages can be send accidentily twice to a certain node. This is not only a waste of money, but it is also very annoying to read messages twice... So April detects those double messages and deletes them while importing. @endnode @node GDomain @TOC glossary Domain Domain is the name of a Net. See also: @{"Net" link GNet} @endnode @node GEchomail "Glossary" @TOC glossary EchoMail Echomail is electronic mail that is 'echo-ed' between several nodes in a network. If you write a message in a message-area on one node connected to the network, then your message will be echo-ed to all the other systems connected to that same area. That way, you don't have to call around the world yourself to reach someone, you can just call a node close to you, and the message will reach him through the network. Although a message is most of the time addressed to one person, ANYONE can read and reply to your message! For personal messages it is better to use netmail. @endnode @node GEditor "Glossary" @TOC glossary Editor With a (mail)editor you can read all incoming netmail and echomail and a good editor has a lot of funktions to make this a easy as possible, and enables you to write, archive, printout and reply to those messages. @endnode @node GExport "Glossary" @TOC glossary Export This is the opposite of Import. All areas are checked to see if you wrote any messages in them, and if some are found then they will be packed in the outbound directory, so your mailer can send them to your boss(es). @endnode @node GFakeNet "Glossary" Fake-net This is the same as your pointnetnumber. This is a little trick which made points possible in FidoNet.. Since Fidonet had only 3d adressing (Zone:Net/Node) and points would need 4d (Zone:Net/Node.Point) they came up with a the following idea: just make a netnumber that doesn't really exist, like 26000. Then just pretent that your points are a node in that net, and export the mail to that (fake!) node. Like if your number SHOULD be 2:282/309.1, you fakenumber would become 2:26309/1. That way, you only need 3d addressing in your software. And since there isn't a REAL 2:26309/1, no harm is done... Just ask you boss what fakenet-number he has chosen, and enter it in the approriate field in BBSInfo. @endnode @node GFidoNet "Glossary" @TOC glossary FidoNet The Domain name of a Net (network) for which April has been written. See: @{"Net" link GNet} @endnode @node GFileAttach "Glossary" @TOC glossary FileAttach Connect a file to a message. Your mailer will then send your file to the address of the message. The person for whome the file is ment, will receive it when he polls for his mail. @endnode @node GFileRequest "Glossary" @TOC glossary FileRequest With FileRequest we mean that you can request files from a @{"BBS" link GBBS}. FileRequests cannot be generated by April. For this you should use an external program like Freq (by Roy v.d. Woning). A file with the requested file will be generated and be placed in the @{"Outbound" link GOutDirOutbound} file has Such a file has a *.REQ extension. @endnode @node GFlowLines @TOC glossary FlowLines With these lines we mean the path, kludges and seenby. With flow we mean the way a message has travelled. @endnode @node GForward "Glossary" @TOC glossary Forward Forwarding means moving a message from one area to another. You can also do this in combination with a reply, so you can answer to a message in a different area than the original message was written... (Be sure that the addressee is reading that other area also !). @endnode @node GHeader-file "Glossary" @TOC glossary Header-file (*_HDR) The messages that April saves to disk are kept in two files per area: a _HDR file and a _MSG file. The _HDR file contains things like the FROM: field, the TO: field, subjects, dates, and some other information that April uses. DON'T mess with a #?_HDR file, if you change only one byte, the whole file can become unreadable ! @endnode @node GHolddirInbound "Glossary" @TOC glossary HoldDir/Inbound This is the directory that April checks for new incoming mail. Normally this should also be the inbounddirectory of your mailer ofcourse. Traditionally this directory is Mail:Inbound/. All *.PKT|*.SU?|*.MO?|*.TU?|*.WE?|*.TH?|*.FR?|*.SA? files are considered (packed) mail, and will be imported into the messagebase of April. Other files in this directory will be left alone, or optionally moved to a Files Backup Directory. @endnode @node GImport "Glossary" @TOC glossary Import This is the proces of putting the incoming mail on disk, so you can easily read/write/search and reply to the echomail and netmail. First, April will make a backup of all the incoming mail in the inbound directory, then the right programs will be called to unpack the packed mail, the *.PKT files are (sometimes in more than one 'round') checked, and all messages are moved to the right area. During that process, there are checks for double messages, broken messages, and the maximum amount of diskspace and memory that April is allowed to use is taken into account. Old messages are deleted to make room for new ones, everything is sorted on the date the messages are written, and all chains are linked together. See also: @{"April Import" link "Import"} @endnode @node GKludge "Glossary" @TOC glossary Kludge Kludges are small lines of text in the body a message, used by pointsoftware. Normally, you won't be able to see them, but with April you can switch them on... Kludges all have in common that they start with a Control-a character at the beginning of a line. A kludge is a way to work around something. The format of the *.PKT files that the messages are sent in, isn't very flexible. When FidoNet started using 4d instead of 3d addressing, there was no room for the 4th pointnumber in the *.PKT file.. So they invented a kludge, FMPT 1 at the beginning of the messagetext to be able to see that the message came from point number one. @endnode @node GLastImport "Glossary" @TOC glossary LastImport With LastImport we mean the last time we imported our post. So, if we talk about LastImport messages we mean the messages that have been imported since our last import. @endnode @node GLog-file "Glossary" @TOC glossary Log-File A textfile where all actions of April are noted down. Afterwards, e.g. when something went wrong, you can take a look at what exactly happened, how many messages were imported or exported... See also: @{"GeneralConfigs" link GeneralConfig} => @{"Opties" link GeneralOptions} @endnode @node GMail "Glossary" @TOC glossary Mail Echomail or netmailmessages. Those are electronically sent messages in general, sent through computernetworks like FidoNet. @endnode @node GMailer "Glossary" @TOC glossary Mailer A program which contacts a BBS and retrieves your mail from it. A Mailer is normally also capable of handling frequests and file-attached messages. Examples of wellknown mailers: Trapdoor and Welmat. @endnode @node GMaxMBnr "Glossary" @TOC glossary MaxMBnr The maximum number of messages that is allowed in a messagearea. When there arrive more messages in one area, the oldest ones are deleted automatically. @endnode @node GMaxMBsize "Glossary" @TOC glossary MaxMBsize The maximum size in kilobytes that is allowed in a messagearea. When the the messagebase is getting larger, the oldest message(s) will be deleted to make room for the new ones.. This can have unexpected results, like when you are replying to the oldest message in the messagebase then there is a good chance that that message will disappear to make room for your answer ! Use the Protect vlag to protect certain messages from deletion. @endnode @node GMessage-file "Glossary" @TOC glossary Message-file (*_MSG) This is the part of the messagebase where the text of the messages is kept on disk. @endnode @node GModerator "Glossary" @TOC glossary Moderator A moderator is someone who checks the messages of an area. He supervises mostly every message on discriminating or rude language. It's also his job to see to it, that the subject of a message is conform the subject of that area. @endnode @node GNamesmenu "Glossary" @TOC glossary NamesMenu This menu gives an overview of all messages that are imported in one area in a list with all the names, dates, subjects and flags. Here you can make a selection of the messages you want to read, or find a message quickly. See also: @{"NamesMenu" link NamesMenu} @endnode @node GNet "Glossary" @TOC glossary Net FidoNet is divides into 6 zones, one for each continent. Those zones are divided again into different regions, and those regions are divided into nets. That way, the northern part of The Netherlands is the 282-net in region 28 in zone 2 of FidoNet. In a net you have several nodes, and those nodes can have one or more points. This structure takes care of an efficient routing of mail, and prevents dupes. @endnode @node GNetmail "Glossary" @TOC glossary Netmail This is (mostly) private mail adressed to one particular person instead of mail written in an echomail-area. Most of time only points and nodes are able to use netmail. Since you can specifically address a message to one person, netmail can be considered as private mail. But when you route your netmail through the network the de addressed system instead of directly calling the other node (crashing) the mail, then all the sysops of the nodes between you and the addressed system will be able to read the mail. It is very important to enter the right nodenumber, otherwise it will never reach it's destination. @endnode @node GNode "Glossary" @TOC glossary Node A node consist of a computersystem connected to a modem. The system received a nodenumber, and is placed in a net and a zone, so the node can send and receive echomail an netmail within a computernetwork. @endnode @node GNodenumber "Glossary" @TOC glossary Nodenumber This is the number that is your address within a computernetwork. If your boss had nodenumber 2:282/309, then your pointnumber or nodenumber will be e.g. 2:282/309.1. With this nodenumber you can receive and write mail, and people can always look up in the nodelist where a message came from. @endnode @node GOrigin "Glossary" @TOC glossary Origin This is the last line of an echomailmessage. Origininally, this was intended to give some space to tell where the message came from, but more and more people use these 56 characters to add something funny to their message. Just use your imagination ! April has a random system integrated so every message can have a random one chosen from a collection of origins. @endnode @node GOutdirOutbound "Glossary" @TOC glossary Outdir/Outbound This is the directory for outgoing mail. Here will the messages that were written by you end up, after they have been exported by April and packed with the ARCer. All you messages will wait there for you mailer to send them to your boss. @endnode @node GPacket "Glossary" @TOC glossary Packet A packet is a standard format to send messages to other nodes. Since there are a lot of different computers used in FidoNet, the format of a *.pkt file is described in very great detail in the technical documentation of FidoNet. That way, it is very good possible to become a point from a node that uses an Ms-Dos PC or and Atari ST while you use an Amiga yourself. @endnode @node GPath "Glossary" @TOC glossary Path This is a list of number that you can find under all echomailmessages. This line is a kludge, so it start with a ^a. The numbers give the route that the message has taken through the network; that way, you can easily see where something went wrong, or where a message came from. @endnode @node GPoint "Glossary" @TOC glossary Point A point is really just another user of a bulletin board, but he is slighly different because he gets his echomail with a mailer, and can read and write mail off-line. A point has a pointnumber, so he or she can use netmail too. However, he is still considered as a normal user, and will still be under supervisory of his boss. @endnode @node GPointNr "Glossary" @TOC glossary PointNr This is the number you get from your Boss. See: @{"Point" link GPoint} @endnode @node GPoll "Glossary" @TOC glossary Poll Fido-talk for calling with your mailer to your boss. During a poll you send your mail, receive new mail from your boss, and you can also pick up files or some some using fileattaches or filerequests. @endnode @node GPrivUser "Glossary" @TOC glossary PrivUser An ordinary ASCII-file with a list of names combined with nodenumbers. It's a kind of little personal telephonebook, where you can look when writing netmail or when you forgot how to spell that difficult name again. That way you don't have to memorize all the nodenumbers from people you know, to write a netmail to then. It's necesserry to keep this list yourself, because points are NOT in the normal nodelist... Sometimes you can get so called pointlists, wich have the same format as the privuserlist that April uses. With April, you can put some more information in the privuser than just name and number, but she will still read the old format of those pointlists. @endnode @node GRegion "Glossary" @TOC glossary Region A region is a collection of nets, that are most of the time grouped together based on the geographical location. Most of the time a region is just about one country.. Region 28 in FidoNet is The Netherlands for example. @endnode @node GSeenBy "Glossary" @TOC glossary Seen-By Some contol-information that you can find under all echomailmessages. The number are the nodenumbers from other nodes that that particular message was also exported to. This is very important to know, that way you can prevent that a message will be exported twice to one node, and thus create dupes. @endnode @node GShowMsgMenu "Glossary" @TOC glossary ShowMsgMenu Here you will see the message. It's the environment where all messages can be read. See also: @{"ShowMsgMenu" link ShowMsg} @endnode @node GTearline "Glossary" @TOC glossary Tearline "A short, product-specific banner" according to the FidoNet technical documentation. You will find a tearline under each message, and it starts with three dashes and a space: --- So if you write a message with April, you message will get a tearline inserted like: --- April x.xxBeta Just to mark the end of your message and tell the world that you are using the wonderfull April to write that message :-) When you register April, there will be a + added, so everyone can see that you registered your April, and that you keep developers developing. @endnode @node GTempDir "Glossary" @TOC glossary TempDir This is the directory that will temporarily hold the packets that were in an Arced mailbundle. When e.g. LhA unarcs a mailbundle, it will unarc the *.PKT files to the TempDir, and imports those to your messagebase. Take care that you have enough room in your TempDir ! @endnode @node GTosser "Glossary" @TOC glossary Tosser A tosser is the software that takes care of the maintanance of your messagebase. It moves the new incoming messages to your messagebase, exports newly written ones to the outbound, it deletes the oldest messages for you, and also linking and sorting of messages is done by this piece of software built-in to April. @endnode @node GZone "Glossary" @TOC glossary Zone FidoNet has been divided into 6 zones at this moment, 1 per continent. Within such a zone you have several regions, and those are divided again into nets, etcetera. This way, a very big 'tree-structure' is build, to divide FidoNet into some orderly organized parts. @endnode @node GZoneGate "Glossary" @TOC glossary Zone-Gate This is the a BBS which works as a gate between two different zones. It's the only system that's allowed to transfer messages between zones. See also: @{"Zone" link GZone} @endnode @node glossary "Glossary" Glossary @{"2D/4D Adressing " link G2D4D } @{"FidoNet " link GFidoNet } @{"Nodenumber " link GNodenumber } @{"April_General " link GApril_General } @{"File attach " link GFileAttach } @{"Origin " link GOrigin } @{"April.arealist " link GApril.arealist } @{"File request " link GFileRequest } @{"Outdir/Outbound " link GOutdirOutBound } @{"April.prefs " link GApril.prefs } @{"FlowLines " link GFlowLines } @{"Packet " link GPacket } @{"Archive " link GArchive } @{"Forward " link GForward } @{"Path " link GPath } @{"Area " link GArea } @{"Header-file (*_HDR) " link GHeader-file } @{"Pattern " link Pattern } @{"AreaFix " link GAreaFix } @{"Holddir/Inbound " link GHolddirInbound } @{"Point " link GPoint } @{"Areamenu " link GAreamenu } @{"Import " link GImport } @{"PointNet " link GFakeNet } @{"AutoLoadHeader " link AutoLoadHeader } @{"Kludge " link GKludge } @{"PointNr " link GPointNr } @{"Backup Directory " link GBackupDirectory } @{"LastImport " link GLastImport } @{"Poll " link GPoll } @{"Bad Msg " link GBad_Msg } @{"Log-file " link GLog-file } @{"PrivUser " link GPrivUser } @{"BBS " link GBBS } @{"Mail " link GMail } @{"Region " link GRegion } @{"Boss " link GBossSysop } @{"Mailer " link GMailer } @{"MsgBuffer " link MsgBuffer } @{"Chain " link GChain } @{"MaxMBnr " link GMaxMBnr } @{"ShowMsgMenu " link GShowMsgMenu } @{"Collapse Quotes " link CollapseQuotes } @{"MaxMBsize " link GMaxMBsize } @{"Seen-Bye " link GSeenBy } @{"Dups " link GDups } @{"Message-file (*_MSG)" link GMessage-file } @{"Sysop " link GBossSysop } @{"Echomail " link GEchomail } @{"Moderator " link GModerator } @{"Tearline " link GTearline } @{"Editor " link GEditor } @{"Namesmenu " link GNamesMenu } @{"TempDir " link GTempDir } @{"Export " link GExport } @{"Net " link GNet } @{"Tosser " link GTosser } @{"External Menu " link External } @{"Netmail " link GNetMail } @{"Zone " link GZone } @{"Fake-net " link GFakeNet } @{"Node " link GNode } @{"ZoneGate " link GZoneGate } @endnode @node Index Index of the April Manual @{"'%' - Codes " link Codes } @{"External Config " link ExternalConfig } @{"NamesMenuConfig " link NamesMenuConfig } @{"2D / 4D " link G2D4D } @{"External Delete " link ExtDelete } @{"Net " link GNet } @{"AboutTheseDocs " link AboutTheseDocs } @{"External Edit " link ExtEdit } @{"Netmail " link GNetmail } @{"Acknowledgements " link Acknowledgements } @{"External Move " link ExtMove } @{"Node " link GNode } @{"Add To PrivUser " link AddToPrivUser } @{"External None " link ExtNone } @{"Nodenumber " link GNodenumber } @{"April_General " link GApril_General } @{"External Pattern " link ExtPattern } @{"Open/Close lines " link OpenAndClose } @{"April.arealist " link GApril.arealist } @{"External Sort " link ExtSort } @{"Openings Edit " link OpeningsEdit } @{"April.prefs " link GApril.prefs } @{"External SortMv " link ExtSortMv } @{"Origin " link GOrigin } @{"Archive " link Archive } @{"Extra info " link Extra } @{"Origin Edit " link OriginEdit } @{"Archive (Glos)" link GArchive } @{"ExtraFonts " link ExtraFonts } @{"OutdirOutbound " link GOutdirOutbound } @{"Area " link GArea } @{"FakeNet " link GFakeNet } @{"Packet " link GPacket } @{"AreaFix " link GAreaFix } @{"FidoNet " link GFidoNet } @{"Path " link GPath } @{"AreaList Add " link Add } @{"FileAttach " link GFileAttach } @{"Point " link GPoint } @{"AreaList All " link All } @{"FileRequest " link GFileRequest } @{"PointNr " link GPointNr } @{"AreaList BBSInfo " link BBSInfo } @{"Flags of MSG/Area " link Flags } @{"Poll " link GPoll } @{"AreaList Configs " link AreaListConfigs } @{"FlowLines " link GFlowLines } @{"PrivUser " link PrivUser } @{"AreaList Copy " link Copy } @{"Forward " link Forward } @{"PrivUser (Glos)" link GPrivUser } @{"AreaList Delete " link Delete } @{"Forward (Glos)" link GForward } @{"PrivUser Add " link PrivAdd } @{"AreaList Edit " link Edit } @{"FromTo Window " link FromToWindow } @{"PrivUser All " link PrivAll } @{"AreaList Make " link Make } @{"GeneralConfig " link GeneralConfig } @{"PrivUser Edit " link PrivEdit } @{"AreaList Move " link Move } @{"GeneralOptions " link GeneralOptions } @{"PrivUser Delete " link PrivDelete } @{"AreaList None " link None } @{"GeneralStrings " link GeneralStrings } @{"PrivUser Move " link PrivMove } @{"AreaList Pattern " link Pattern } @{"Glossary " link Glossary } @{"PrivUser None " link PrivNone } @{"AreaList PCopy " link PCopy } @{"GotoAreaMenu " link GotoAreaMenu } @{"PrivUser Pattern " link PrivPattern } @{"AreaList Sort " link Sort } @{"GotoNamesMenu " link GotoNamesMenu } @{"PrivUser Sort " link PrivSort } @{"AreaMenu " link AreaMenu } @{"GotoShowMsg " link GotoShowMsg } @{"PrivUser SortMv " link PrivSortMv } @{"Areamenu (Glos)" link GAreamenu } @{"Group Add " link GroupAdd } @{"Project Menu " link Project } @{"AreaMenuConfig " link AreaMenuConfig } @{"Group Del " link GroupDel } @{"Rescan " link Rescan } @{"ARexx " link ARexx } @{"Group Edit " link GroupEdit2 } @{"Region " link GRegion } @{"AutoLoadHeader " link AutoLoadHeader } @{"Groups window " link GroupEdit } @{"Registration " link Registration } @{"BackupDirectory " link GBackupDirectory } @{"GroupsAndLanguages" link GroupsAndLan } @{"ReplyMSG " link ReplyMSG } @{"Bad_Msg " link GBad_Msg } @{"GroupAdd Language " link GroupLan } @{"Reply & Forward " link ReplyForward } @{"BBS " link GBBS } @{"Hard & Software " link hardensoft } @{"Requirements " link Requirements } @{"BeforeImport " link BeforeImport } @{"Header-file " link GHeader-file } @{"Rip origin " link RipOrigin } @{"BossSysop " link GBossSysop } @{"HolddirInbound " link GHolddirInbound } @{"SaveConfigs " link SaveConfigs } @{"Browse " link Browse } @{"How to use April " link Usage } @{"ScreenConfig " link ScreenConfig } @{"Bugs & Suggestions" link Bugs } @{"Installation " link Installation } @{"ScreenTitle " link ScreenTitle } @{"CarbonCopy " link CarbonCopy } @{"Introduction " link Introduction } @{"SeenBy " link GSeenBy } @{"Catch up " link CatchUp } @{"Import " link Import } @{"Select All " link SelectAll } @{"Chain " link GChain } @{"Import (Glos)" link GImport } @{"Select Marked " link SelectMarked } @{"Closings Edit " link ClosingsEdit } @{"Kludge " link GKludge } @{"Select MSG " link SelectMSG } @{"Collapse Quotes " link CollapseQuotes } @{"Language Edit " link LanguageEdit } @{"Select Pattern " link SelectPattern } @{"Config Menu " link Config } @{"LastImport " link GLastImport } @{"Set MSG Flags " link SetMSGFlags } @{"CopyrightNotice " link CopyrightNotice } @{"Log-file " link GLog-file } @{"ShowMSG " link ShowMSG } @{"Delete MSG " link DeleteMSG } @{"Mail " link GMail } @{"ShowMsgConfig " link ShowMsgConfig } @{"Domain " link GDomain } @{"Mailer " link GMailer } @{"ShowMsgMenu " link GShowMsgMenu } @{"Dups " link GDups } @{"MaxMBnr " link GMaxMBnr } @{"Tearline " link GTearline } @{"Echomail " link GEchomail } @{"MaxMBsize " link GMaxMBsize } @{"TempDir " link GTempDir } @{"EditHeader " link EditHeader } @{"Menus " link Menus } @{"Tosser " link GTosser } @{"EditMsg " link EditMsg } @{"Message Menu " link Message } @{"TosserConfig " link TossConfig } @{"Editor " link GEditor } @{"Message-file " link GMessage-file } @{"TosserImport " link TossImport } @{"Export " link Export } @{"Moderator " link GModerator } @{"TosserStrings " link TossStrings } @{"Export (Glos)" link GExport } @{"MsgBuffer " link MsgBuffer } @{"UnselectAll " link UnselectAll } @{"External " link External } @{"MsgInfo " link MSGInfo } @{"Write MSG " link WriteMSG } @{"External Add " link ExtAdd } @{"NamesMenu " link NamesMenu } @{"Write/Reply/Edit " link WRE } @{"External All " link ExtAll } @{"Namesmenu (Glos)" link GNamesmenu } @{"Zone " link GZone } @{"ZoneGate " link GZoneGate } See also: @{"Glossary" link Glossary} @endnode