The fuzzy editor title bar conveys important information. It can tell you what source file you are editing, whether the file has been changed since the last save, whether a serialized form of the file has been saved, and whether the source file has been verified for correctness (or compiled).
First of all, the title bar tells you what source ruleset file you are editing and whether the file has been changed since the last time it was saved. If you are editing a brand new ruleset that has not yet been saved to disk, the source file name appears as:
Src: Untitled.frsWhen you save the source ruleset to disk, you are asked to give the ruleset a file name, which then appears in the title bar. For example,
Src: myFuzzyRuleset.frsAny time you make a change to the ruleset, an asterisk (*) appears after the source file name:
Src: myFuzzyRuleset.frs*Return to top
A second thing that the title bar tells you is whether the source ruleset has been saved as a serialized, ready-to-run AbleBean. If you are editing a ruleset that has not been saved in serialized form, the serialized file name appears as:
Ser: Untitled.serWhen you save the ruleset in serialized form, you must give the ruleset a file name, which then appears in the title bar. For example,
Ser: myFuzzyRuleset.serNote that the source file name and the serialized file name do not have to be the same. That is,
mySourceFuzzy.frs
and
yourSerializedFuzzy.ser
can
refer to two different representations of the same fuzzy
ruleset.
Return to top
A third thing that the title bar tells you is whether the source ruleset has been saved as an XML document. If you are editing a ruleset that has not been saved in XML form, the XML file name appears as:
XML: Untitled.xmlWhen you save the ruleset as an XML document, you are asked to give the XML document a file name, which then appears in the title bar. For example,
XML: myFuzzyRuleset.xmlNote that the XML file name, the serialized file name, and the source file name do not have to be the same. That is,
mySourceFuzzy.frs
,
yourSerializedFuzzy.ser
, and
someXmlFuzzy.xml
can all
refer to three different representations of the exact same fuzzy
ruleset.
Return to top
Lastly, source fuzzy ruleset files can be saved at any stage of editing, but serialized fuzzy ruleset files and fuzzy XML documents can be saved only when the source represents a valid, executable fuzzy ruleset. Use the Verify editor action to cause the source ruleset to be parsed (or compiled) and verified for correctness. If the ruleset is valid after the Verify action, the title bar displays the word "(verified)" and you may only then save the file in serialized and XML forms, or process the rules.
After an initial load of a source ruleset or after any editing change, the ruleset is in an unknown state and the title bar displays the word "(unverified)". At these times it is not possible to save the ruleset in serialized and XML forms, nor is it possible to run the rules. Use the Verify editor action to change this state.
Return to topAn example title bar and its interpretation follows:
Src: Controller1.frs* | Ser: Controller1.ser | XML: Untitled.xml (unverified)The user is editing a fuzzy source file named
"Controller1.frs"
. The asterisk (*)
after the file name indicates that the file has been changed
since it was last saved. At some point, the source file was
saved in serialized form to the file named "Controller1.ser"
, but the file has not yet
been saved in XML form (as indicated by the file name
"Untitled.xml"
). Currently,
neither a serialized form nor an XML form can be saved to disk
because the ruleset has not been successfully compiled, or
verified (indicated by the word "(unverified)"
) since the last change was
made to the source.
At this point, a typical user action might be to use the
Verify editor action to compile the source file and then
notice whether the title bar switches to show the word
"(verified)"
. If the title bar
changes, the verification process was successful and the user
might then use the editor actions Save ruleset, Save
serialized, and Save XML to save the fuzzy ruleset in
its source, compiled, and XML forms. The title bar might
subsequently look like this:
Src: Controller1.frs | Ser: Controller1.ser | XML: Controller1.xml (verified)Return to top