There are a number of large and small configuration and data files in the Arachnophilia user installation area (user home directory/.Arachnophilia). Many of them are self-documenting because they contain comments. These files exist because of the Arachnophilia basic design philosophy -- expose as much functionality to the user as possible. Instead of only requiring the user to learn the program, make the program learn from the user.
Each logon user gets a separate set of these files installed in his home directory, which means Arachnophilia is very much a personal program -- it looks the way you want, acts the way you choose to make it act, and other users' choices cannot interfere. Here is a detailed list:
A list of unadorned executable names used in the browser search carried out by the Browser Configuration dialog.
The command list used by the Ctrl-right-click list. This is one of the few macro-bearing files that must be edited directly. It is easy to edit in plain-text form, unlike the main macro collection, which contains some rather esoteric traits and therefore needs a special, dedicated editor.
A list of character numbers and corresponding HTML entities. This list is used by the HTML entity-> char and char-> entity macros.
A list of file types, extensions (or suffixes if you prefer) and other file traits. This file makes it easy to add extensions to existing file types, or even to add new file types. It contains some detailed comments.
A list of FTP site definitions. This file doesn't exist by default, it is created after some definitions have been entered into the FTP Service dialog. This file is separate from the main macro file because it can contain (trivially encrypted) passwords -- users may want to exchange macro files and not realize they are giving away their passwords. So this file stays in the user's Arachnophilia directory unless he really knows his way around Arachnophilia and actually wants to pass it on.
The database used by the Tips of the Day dialog. It is very easy to add data to this file. Each tip is separated from others by "*" characters, this allows multi-line tips.
These files are provided to demonstrate the external class invocation feature explained in The Java Custom Clas Interface page.
This directory contains Arachnophilia's documentation in HTML form. It is always a good idea to visit www.arachnoid.com/arachnophilia/Documentation from time to time to see if the documentation has been updated.
This is a list of tag combinations that the HTML Beautifier should skip over (not parse between the opening and closing tags) when indenting an HTML or similar file. This has been included because HTML is in constant flux, and Arachnophilia is likely to be used for markup languages where the rules are different than for vanilla HTML.
This is a list of tags that are not paired with a closing tag (such as <li> and <option>). I expect this to change over time, and I don't want to have to rewrite Arachnophilia when that happens. Also, of course, there are markup languages that differ in their rules -- this file allows you to accommodate those diferences.
This file contains the tags whose contents should not be parsed by the HTML compressor macro. This prevents compression of area whose formatting must be preserved, such as <pre></pre> tag pairs.
This is the main Arachnophilia macro file. It contains the entire Arachnophilia macro tree -- all the toolbars, menus and the like. It is formatted in XML, so it should be possible to:
- Export and import to/from other applications that read XML,
- Easily exchange macro sets and subsets with other Arachnophilia users, and
- Understand it to some extent by reading it directly.
Macro importing and exporting is made easy using the macro tree browser's file read and write features.
This is the default spelling dictionary. It doesn't have to be a zip file if that is not convenient. Any file in this directory with a suffix of ".txt" will be read by the spell checker, as explained in the tips of the day and on the Spell Checker page
This file appears after the user has chosen to add words to the spell checker. It can be edited directly.
This file identifies tag pairs inside which the spell checker should not search. An example would be a <style></style> tag pair containing only style definitions, or a <script></script> tag pair containing only JavaScript or another language, information that would only confuse the spell checker.
This is the set of file templates that Arachnophilia uses to create new documents. The templates can contain Arachnophilia macros, which will be processed before the document is presented to the user. These are easy to customize for particular tasks.