Changes between Version 9 and Version 10 of DevelopmentProcess

Timestamp:

2017-10-04 12:46:59 (7 years ago)

Author:

archibald

Comment:

--

DevelopmentProcess

@@ -2 +2 @@
 Though "a picture paints a thousand words," There's no substitute for a written document. They do take a long time to produce.[[BR]]Here's a process diagram ( bubbles are processes, documents in and out ) of how the development process goes when working in VDx and TDx.[[BR]][[BR]]
 [[Image(DevelopmentProcess.png,912)]][[BR]][[BR]]
-If we start at the "Design" documents, we see that those are fed into the VisualBRON editing process. That's the designer dragging and droppinf boxes, having fun and playing around.
+If we start at the "Designs" documents, we see that those are fed into the VisualBRON editing process. That's the designer, dragging and dropping boxes, having fun and playing around.
 
 Next the Visual Dxiner process can save or retrieve those designs in "*.vbr" format.
 
-Then if commanded, Visual DXiner will write those designs out as "BRON" pseudo code ( ending in .def ), hpwever it is possible ( if you have the generators ) to generate that directly in ".C" and ".H" files.
+If commanded, Visual DXiner will write those designs out as "BRON" pseudo code ( ending in .def ), however it is possible (if you have the generators) to generate that directly in ".C" and ".H" files.
 
-Finally the pseudo code files are interpreted by the "Textual DXiner" and along with it's generator files and design libraries will produce ... "C" and "H" code files.
+Finally the pseudo code files are interpreted by the "Textual DXiner" and along with it's generator files and design libraries, will produce ... "C" and "H" code files.