Customizer Developer File

Hi guys! Included in this file and the "Developer" folder is all the
information that you need to write MODs for Customizer v1.0+. If you need any
help, send me a letter at the address in the program, in the ReadMe file, in
the Survey...I'm tired of typing it...:)

Oh, and please do fill out the survey, and, if you're nice, throw in some
money too...:)

Now, to create a MOD, here's what I do...

1) Run FileFinder on the program to change, and write down the file,
   location, and original text for each message that you would want to
   change.

2) Go into a text editor. (I use ProTERM)

3) Type out the MOD, using the format included in this file.

4) Save it as text.

5) Change the FileType to $F1, using whatever utility you want. (Again, I use
   ProTERM)

6) Troubleshoot it, and repeat until bug-free.

Well, I hope that you're successful, and again, drop me a line if you write a
MOD or need help writing one.

And, oh, if any of you know assembly or some other low-level language,
_please_ consider writing a faster version of FileFinder. I need it! :)

Okay then...here's the MOD format:
_____________________________________________________________________________

Customizer Module file format v1.0v3

Conventions: anything in quotes ("") is letter for letter in the actual file.
             anything in angles (<>) you replace with the appropriate info.
             anything in parentheses (()) is a comment that does NOT get put
             into the file.

             You can use any little marks you want in the appropriate spots.
             (e.g. commas in the comment lines)

Write the file as a text file, then change the filetype to $F1. THIS IS VERY
IMPORTANT. If you don't do it, Customizer will NOT recognize the file as
being a Customizer Module.

Okay then...let's start. There are no blank lines, except that there must be
five (5) comment lines, no matter if anything is in them or not.

Absolute start of file. Beyond this line is the format! (Whoa...)
_____________________________________________________________________________

"Customizer Module"
"1.0"
<Program name, keep it simple and include the version number.>
<Number of modifications in the file>
<Author of module>
<Comment line 1, max. 76 characters.>
<Comment line 2, max. 76 characters.>
<Comment line 3, max. 76 characters.>
<Comment line 4, max. 76 characters.>
<Comment line 5, max. 76 characters.>
_____________________________________________________________________________

Okay....that's the first part...now, there are twenty (20) chunks of data,
one for each module. The remaining ones MUST have data in them. You can't
go wrong with just a zero (0) as a filler for EACH ENTRY.

Remember, twenty (20) of these...
_____________________________________________________________________________

<Name of module. Max. 47 chars if more than ten (10) modifications, max. 76
 characters if ten (10) or less modifications.>
<Filename of the file that contains the data to modify.>
<High bit status. See below for info.>
<Location of data to modify. See below for info.>
<Original text in file, letter for letter.>
<Base-10 filetype of the file that contains the info to modify. (FileFinder
 supplies this at the top of its screen)>
_____________________________________________________________________________

Okay...now for some details...

High bit status: can be one of these values:

0 - High bit cleared, choice of invert given.
1 - High bit set, choice of invert given.
2 - High bit cleared, choice of invert NOT given.
3 - High bit set, choice of invert NOT given.

The "choice of invert" is for some programs, where you can get inverse text
when the high bit is opposite what is usually is. You'll have to play around
with these settings, but I found that for normal text, the high bit is
cleared for 40-column programs and set for 80-column programs. Don't ask me
why...

For the location of data to modify, use FileFinder (included). It's slow,
(you should run it on a TransWarped or Zipped GS for diesent speed...)
but it does the job. You figure out how to use it.

Well, that's about it...do what you will with it...
___
/ revden