Flow Chart to Code (FCTC)  

Limitations


1.
Saving Flowcharts

Running JDK 1.3 or below, flowcharts cannot be saved (they are normally saved as XML files, and XML support was only added in JDK 1.4).  In these circumstances, saving as a GIF file (see Printing Flowcharts below) and Exporting the Source Code at least provides a record of the saved flowchart.  JDK 1.4 (or better) is the preferred JRE to run under.



2.
Printing Flowcharts

The program does not print flowcharts out directly, but rather saves them as a GIF file.  This file can then be opened in a browser, word processor, or other program to provide scaling and printing capability.



3.
Exporting Source Code

All program-generated and user-supplied source code is always saved along with the flowchart.  The Export Source Code function attempts to collect all code snippets (in order of flow) associated with the flowchart and save them as an ASCII text file.  There must be only one START box and a STOP box, and the path between these must be drawn correctly.  Version 1.2 of the FlowChartToCode program does not collect for output to file the additional snippets that may be stored with the flowchart associated with complex multiple paths (branches coming out of the side of CASEs, and code STEP boxes coming out of the close gadget and non-default buttons of a DIALOGs).   These are all currently being addressed for the next upgrade, which will be free to all users.



4.
Flowchart Symbol Selection

While drag-and-drop capability would have been nice, it was beyond this first production version of the program.  Symbol selection is done using the right mouse menu.



5.
Running as an Applet

Currently, because of sandbox issues, there are no plans to modify the program to run in a non-demo mode as an Applet.  If there is enough demand and users provide some ideas for easy implementation of this feature, then I will certainly look into that possibility



Go to FCTC Home Page