The ParserMonster Framework derives much of its flexibility from plain old text and image files!

Some of them are read-only, embedded files. They never change unless you receive an update.

Others are read-write, which means that you can edit them.

Finally, you can create your own. If you follow the correct syntax, you can extend the ParserMonster Framework with customized data.

The following file types make up the ParserMonster Framework Data-driven System:

The most visible of these files is the Task file. It contains the commands and directives that make the framework come to life. Naturally, the more task files you have, the more powerful your program becomes. If you learn to write your own tasks, you may not have buy more than one ParserMonster-based product! (The obvious corollary is that, yes, you can mix and match tasks - as long as they are not embedded in the program package.)

The icons associated with task files are read-only, but you can add your own.

Script files are task files with super powers.

As you become more proficient with writing tasks and scripts, you'll want to explore constants, flags and variables.

You won't have access to most of the constant files maintained by ParserMonster. Constants are names for a number, a literal string, a formula or a state ( true / false ). It is easier to write $LongTime than Hh:Nn:Ss ampm) and it is nearly impossible to remember some of the really long values, such as the regular expression for something like $regexEmailAddress.

These are your files. ParserMonster can read several types, in addition to all plain text files of which it is aware. To ensure that ParserMonster is aware of a filetype, it must be mapped explicitly to one of these general groups:

• txt - Plain text
• rtf - Rich text format (not always, though!)
• doc - Microsoft Word format
• xls - Microsoft Excel format (except binary)
• xml - XML format

ParserMonster has a predefined list of recognized filetypes. If you need to extend or override this list, just create a cx- file with your own mappings.

(Note, due to the versatility of cx- files, the mapping may change in the future.)