Rainlendar is a customizable calendar that resides on your desktop and shows the days of the current month. It's possible to add events and tasks to the calendar and the appearance can be customized with different skins. Rainlendar can also show the events and tasks from Microsoft Outlook and Mozilla Sunbird. The events can be synchronized with a server, which will allow you to use it e.g. at home and at work. There are plenty of other features too. Check the rest of this document for details.
Rainlendar requires Windows 2000 or Windows XP to work correctly.
This product includes software developed by Lee Patterson (http://ssobjects.sourceforge.net/).
Installing for Explorer
If you are in doubt, just get the installer version of Rainlendar from the webpage (http://www.rainlendar.net) and run it. If you dislike installers, you can also get the zipped archive and uncompress it to some folder. Rainlendar is ready to be used after that. Note that if you want that the calendar starts with the Windows you need to keep the "Startup folder"-option checked in the installation.
Rainlendar is installed for the current user by default. If you want to install it for different users, just run the installer for each of them.
Installing for Litestep
Rainlendar works also as Litestep's plugin. To install in Litestep grap the zip archive and just copy the Rainlendar.dll and the skin, language and plugins folders to your Litestep directory (e.g. C:\Litestep\). You don't need the Rainlendar.exe if you are using Rainlendar as Litestep plugin. After copying, open your step.rc and add following line:
... and recycle. If that doesn't work, check the config part of this document for additional step.rc commands that you might need. You can also put the Rainlendar in other folder if you like, just make sure that the LoadModule path points to the correct place (as well as other Rainlendar specific step.rc commands).
If you installed Rainlendar with the installer you can uninstall it from the "Add or Remove Programs". Otherwise just delete all the files you uncompressed from the zip-file (make sure that Rainlendar isn't running when doing that).
Installing skinsThe skins are usually distributed in zip-files that hold the skin's ini-file and graphics files. To install a new skin you need to unzip the file into the Rainlendar's Skins-folder (usually located in C:\Program Files\Rainlendar\Skins).
The skin has one or more ini-files (i.e. a file with .ini extension). The skin's ini-file must be located in a separate subfolder under the Skins-folder (e.g. C:\Program Files\Rainlendar\Skins\MyTestSkin\Skin.ini). If you put it directly into the Skins-folder or if there are more than one subfolder things won't work. After you have the skin in correct place just refresh the calendar and you should see the new skin in the skin menu. If the skin is not visible in the menu the most likely reason is that you created an extra subfolder when the zip was uncompressed. Check the folder structure again and remove the extra subfolder by moving the skin's ini and graphics files to the parent folder.
The basic configuration of the calendar is done from a GUI which you open from the popup-menu. The settings are saved in a Rainlendar.ini-file when you press the OK-button.
Show event message in tooltip
Show message alarms
Show all today's messages at startup
Disable keyboard shortcuts
Poll wallpaper changes
Snap to screen edges
Refresh when screen resolution changes
Use separator in tooltips
Show tray icon
Hide event and todo lists when there are no items
Use native Windows transparency
Event list window
Remember dialog positions
Hide on mouse over
Opaque on mouse over
Transparent on mouse over
The layout type defines how the calendars are placed on the grid. You can for example have the calendars placed in checker style or in X-shape. Just try them out to see how they look.
This page enables to add hotkeys to various actions. The hotkeys are global so it's not necessary to have Rainlendar activated when pressing the keys. It's adviced not to use too simple hotkeys (like Shift + A) since that would execute the hotkey every time you write capital A letter.
PluginsHere is a list of installed plugins. See the Plugins page in this document for more information about them. The plugins can ge activated and deactivated from here. If the plugin has settings they can be edited by selecting the plugin from the list and pressing the Settings-button. The "Set as Default" button makes the plugin a default which basically means that it's editor (if it has one) will be used when creating new events.
AdvancedThere are also some other settings in the Rainlendar.ini that cannot be changed from the GUI. It's possible to change them directly from the Rainlendar.ini. Do not keep the config dialog open when editing the Rainlendar.ini or the settings will be overwritten when you press the OK-button. After you have edited the settings, refresh the calendar and the new sttings will be taken into use.
Here's a list of the settings in Rainlendar.ini (only the ones that cannot be changed from the GUI):
X, Y, TodoX, TodoY, EventListX, EventListY
MessageBoxX and MessageBoxY
Defines the maximum width (in pixels) of the tooltip. If set to 0 there is no limit.
TrayExecuteL, TrayExecuteM, TrayExecuteR, TrayExecuteDL,
The time in ms that defines how long the fading effects take. Set to 0 to disable the fading.
If set to 1 a context menu instead of full menu is shown when right mouse button is pressed over one of the windows.
Defines what happens when you double click the todo window:
0=Default behaviour. If an todo item is selected opens the context menu otherwise opens the todo dialog. 1=Marks the todo item checked.
2=Opens the todo dialog and selects the item.
3=Opens the todo dialog.
4=Deletes the todo item.
5=Marks the todo item as done.
List of profiles that you don't want to be visible in the calendar. Separate the list with ';'-char. E.g. HideFromCalendar=Birthday;Personal;Outlook
GridLeftToRight, GridTopToBottom, GridAcrossAndDown
Most of the skinning can be done from the GUI, which is probably the easiest way to modify the skins. However, sometimes it might be useful to do the changes directly in the skin files. The skin files weren't originally meant to be edited by hand, so some of the entries might be a bit unintuitive.
The items (numbers) in an image can be placed either horizontally or vertically. The correct placement is determined from the dimensions of the image (i.e. whichever is bigger: height or width). The images must be cropped so that they don't hold any extra space and their width (or height) must be divisional with the number of items in the image. The current version of Rainlendar supports BMP, JPG and PNG files. Them PNGs can include alpha mask.
The name of the skin file can be anything that ends with ".ini". The skins must be placed in a separate subfolders, which will give the name to the skin. The same folder can also contain several skin ini-files.
New in 0.21: The skin format has changed slightly. It is now possible to put the different parts to separate sections. The benefit from this is that you can define the drawing order by placing the sections before each other. The sections are drawn the order they are defined (except that background is drawn always first). Note that dynamic items (Time and Button) are always drawn on top of the static items (i.e. normal calendar graphics). The Image-sections can be drawn in any place.
The sections are: [Background], [Days], [Today], [Weekdays], [Month], [Year], [Event], [WeekNumbers], [Tooltip], [Todo], [MessageBox] and [EventList]. If you use these do not add the [Rainlendar]-section or the skin is read as old format.
Important! If you create a skin that uses the new format you should inform the users that it requires Rainlendar 0.21 or newer. The new skins behave quite badly in 0.20 and older versions.
ButtonsIt's also possible to add buttons to the skins. This can be only done in the skin's ini-file as there is no GUI for the buttons. To add a button you need to create a new section called [ButtonN] where the N is a number (it can be any number as long as no other button is using it). The buttons can have these values:
[Button1] Window=0 X=5 Y=5 BitmapName=button-left.png Command=!RainlendarShowPrev
Time itemsTime items show the current date or time in the calendar. It's also possible to show the time in the tooltip. They can be used to e.g. show a clock or current day. Note that the window is updated only once per minute so you cannot use seconds in the clock (or you can but it's rather pointless). To add a time item you need to create a new section called [TimeN] where the N is a number (it can be any number as long as no other time item is using it). The time items can have these values:
[Time1] Window=0 X=-50 Y=10 Rasterizer=FONT Font=-17/0/0/0/700/0/0/0/0/3/2/1/34/Arial FontColor=FFFFFF Format=%d Location=(GMT-09:00) Alaska
ImagesThe images are similar as buttons and time items except that they do not do anything. An image is just drawn in the window. To add an image you need to create a new section called [ImageN] where the N is a number (it can be any number as long as no other image is using it). The imagess can have these values:
[Image1] Window=0 X=0 Y=0 BitmapName=shine.png
FontsThe fonts are defined with 13 values and the name of the font all separated with '/'-char. The most important values are the first one which defines the height of the font and the last, which is the typeface name of the font. The height of the font is defined in logical size and not in the point size.
The different values are in order:
Check CreateFont() in Win32 API documentation for more info.
ProfilesWith profiles you can customize individual events. When you create an event there is a combo box which can be used to select the profile for the event. The combo box lists the profiles that are defined in the current skin's ini-file, but you can also give a custom profile name. If a certain profile is not defined in a skin a default settings are used instead.
The profiles are defined in the skin file by making a new section. The name of the section must start with the word "Profile" (without the quotes). After that you can put pretty much anything to make the section unique (i.e. there cannot be two sections that have same name (i.e. the string between -chars, not the "Name=" string).
The profile section must have a key called Name, which will give the identity to the profile. The name is the one that is displayed in the Edit Event dialog.
Other keys that can be in the profile section are:
The values for the keys are exactly the same as defined above. The profile settings override the default skin settings, so for example if the default ToolTipFontColor value is black and you create a profile that defines it white, all events that use that profile will draw the tooltip texts white. Note that it is not necessary to give all the keys always; you can define just the ones that are necessary (default values are used for the missing keys).
The EventIconName, EventIconAlign and EventDrawAlways can only be used with the profiles. The event icon is a small image that is displayed on top of the event with the given profile. The align uses the same alignment system as other aligns (check e.g. DaysAlign for the codes). If the EventDrawAlways is set to 1 it means that the event is drawn always on the calendar.
The priority defines what is drawn on the calendar when there are several event on the same day. The repeating events also have predefined priorities so that less frequently happening events have higher priority. Like this:
Daily Priority = 10 Weekly Priority = 20 Monthly Priority = 30 Yearly Priority = 40 Single Priority = 50The profile's priority value is added to this to determine the actual priority for the event. If you don't want that the recurrence pattern affects the priorities of the events you can define them so that they are >50 apart from each other. E.g. 100, 200, 300, etc.
The RecurringPostfixString will append the given text to the end of the events that use the profile. Note that the text will be added only to recurring events.
Currently it is not possible to create/edit the profiles from the GUI. You need to create by hand with a text editor.
[Profile 1] Name=Sunday ToolTipFontColor=00DDFF EventFontColor=DD8888 [Profile 2] Name=Important ToolTipFontColor=FFFFFF EventFontColor=FFFFFF EventFontColor2=FFFFFF EventIconName=Icons/Lightning.png EventIconAlign=18
The Rainlendar can be controlled also with Litestep !Bang-commands. You can also give the !bangs as command line arguments for Rainlendar.exe (note that this does not work if Rainlendar is OnDesktop). The bangs can also be used in other places (e.g. buttons) to control the calendar.
!RainlendarShowMonth [Month] [Year]
!RainlendarMove [X] [Y] [Window]
!RainlendarAddEvent [Day] [Month] [Year]
This plugin uses Rainlendar's custom ini-format for the events. The plugin can read and write events. You can have multiple event and todo files. The plus-button adds a new file and the cross removes the selected file. Note that the items will be saved to all of them unless you set them Read-Only (can be set from the star-button). Read Only events cannot be modified and they are not sent to other plugins (including the ServerPlugin, so they are not distributed).
This plugin can read appointments and tasks from Outlook. The read items are considered as read-only so they cannot be modified. The plugin is meant to be used only in Win2k or WinXP (the timezone conversion does not work in Win9x).
Note that the exception dates are not supported. So if you have a repeating event and you have deleted/modified one of the events in Outlook Rainlendar will show the original event still.
Use Outlook labels as event profiles
Keep MAPI-connection alive
Don't show message body
Don't show completed tasks
Imported message stores
This plugin syncronizes the events with a different clients. You need to be running the RainlendarServer (see the ReadMe.txt in the server package for more info). If the plugin is made as a default it updates the event from the server before it is edited, so there might be a small delay before the Edit Event-dialog is opened. The events are requested from the server when Rainlendar is started or when it is refreshed.
Poll events from the server
This plugin can read/write events and tasks from .ics files. This plugin can be used for example to show Sunbird's events in Rainlendar. The plugin is meant to be used only in Win2k or WinXP.
Refresh when file changes
Ignore completed tasks
Mozilla Sunbird integration HOWTO:
These are Litestep specific settings that are placed in the step.rc file. Remember to put the paths inside quotes if you have spaces in them!
The latest version will be found from http://www.rainlendar.net. You can also find new languages and skins from there. You may also send comments and bug-reports to the author. But before you do, check the Rainlendar's section in the Forum. It might already contain answers to your questions.
Please put the name of the product (i.e. Rainlendar) in the subject-field of the mail. It may be useful if you write the version of the product also. If you are reporting a bug, please try to be as exact as possible when describing the symptoms. Also write down the details of your system (like OS version, Litestep build, and so on).
GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "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 PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM 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 PROGRAM (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 PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS
22 JAN 2006 (Version 0.22.1 ▀)
25 OCT 2005 (Version 0.22 ▀)
22 JUL 2005 (Version 0.21.2 ▀)
25 MAR 2005 (Version 0.21.1 ▀)
1 MAR 2005 (Version 0.21 ▀)
5 DEC 2004 (Version 0.20 ▀)
9 MAY 2004 (Version 0.19.3 ▀)
20 MAR 2004 (Version 0.19.2 ▀)
28 JAN 2004 (Version 0.19.1 ▀)
25 JAN 2004 (Version 0.19 ▀)
4 OCT 2003 (Version 0.18 ▀)
23 AUG 2003 (Version 0.17.1 ▀)
9 AUG 2003 (Version 0.17 ▀)
15 JUN 2003 (Version 0.16 ▀)
3 FEB 2003 (Version 0.15 ▀)
23 NOV 2002 (Version 0.14 ▀)
24 AUG 2002 (Version 0.13 ▀)
10 AUG 2002 (Version 0.12 ▀)
11 JUN 2002 (Version 0.11 ▀)
3 JUN 2002 (Version 0.10 ▀)
2 MAR 2002 (Version 0.9 ▀)
15 JAN 2002 (Version 0.8 ▀)
26 DEC 2001 (Version 0.7 ▀)
3 DEC 2000 (Version 0.6 ▀)
2 OCT 2000 (Version 0.5 ▀)
4 JULY 2000 (Version 0.4 ▀)
13 MAY 2000 (Version 0.3 ▀)
6 APRIL 2000 (Version 0.2 ▀)
26 MARCH 2000 (Version 0.1 ▀)