Differences

This shows you the differences between two versions of the page.

--- data-driven-system [2014/08/02 19:25]
Mitch terminology change from rules to scripts
+++ data-driven-system [2015/08/15 18:35] (current)
Mitch
@@ Line 1: / Line 1: @@
-The ParserMonster Framework derives much of its flexibility from plain old text files!
+====== ParserMonster Framework Data-driven System ======
-Of course, these files have special instructions but, the point is that you can drastically alter the behavior of any program based on the ParserMonster Framework.
+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:
+===== Task Files (*.task) =====
 The most visible of these files is the [[taskfiles|Task file]]. It contains the [[ParserMonster Commands|commands]] and [[ParserMonster Directives|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 [[taskicons|icons]] associated with task files get honorable mention in this group, because you have the ability to add your own.
+===== Task Icon Files =====
+The [[iconfiles|icons]] associated with task files are read-only, but you can add your own.
+===== Script Files =====
+[[scriptfiles|Script files]] are task files with super powers.
+===== Constant Files (cx*.txt) =====
+As you become more proficient with writing tasks and scripts, you'll want to explore [[parsermonster_constants|constants]], [[parsermonster_flags|flags]] and [[parsermonster_variables|variables]].
+You won't have access to most of the [[constantfiles|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|$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.
+===== Data =====
+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|recognized filetypes]]. If you need to extend or override this list, just create a [[parsermonster_constants|cx- file]] with your own mappings.
-Once you've played with the main window, you'll want to get down to business. You don't have time to repeat the same drag and drop operations - and you won't have to! Just save the current setup as a [[scripts|script]]. You can quickly load and reuse the script whenever you need to perform a task that always operates on the same folder(s). Scripts do more than just save settings, they can orchestrate the operation of multiple tasks.
+(Note, due to the versatility of [[parsermonster_constants|cx- files]], the mapping may change in the future.)

ParserMonster Project

User Tools

Site Tools

Differences

Page Tools