This method starts the loading of the FDL file and the parsing of it. Alternatively, you can use “LoadFlowsFromString” if you don’t have a file. This can be useful to store the flow definitions in the resources of the application. Both possibilities use the same flow (FDLParseFlow) to parse the content of the given flow definition:


The two steps (FDLFileLoader and FDLTextConverter) sends the flow definition string to the parser flow:


The steps FDLRemarksDefinitionsParser and FDLAttributeDefinitionsParser are only used for the AppDesigner.

In the first step (DSLTabReplacer) the tabs of the definition file are replaced by spaces to simplify the following steps.
The DSLFlowDefinitionParser generates new instances of datatype DSLFlowDefinition, finds the range (line numbers) of the flow definition within the text and parses the name of the flow by searching for “{“ and “}”. The content of each flow is parsed by the later steps in this flow. Each of steps work almost in the same way. Every step searches for specific key word within the flow definition range by finding the brackets.

Last edited Apr 20, 2013 at 8:50 AM by InneHo, version 5


No comments yet.