Posts Tagged ‘Automated Documentation’

MANUAL MAINTENANCE

July 27, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

THURSDAY: The development of the “_REPORT_FILE” Command” page has been started. The script library error being corrected was encountered. The Manual Update may needed to be put on hold until these script library corrections have been made.

Advertisements

MANUAL MAINTENANCE

July 20, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

SATURDAY: The “_SET_TAB Command” has been successfully moved to a dedicated sub-directory.  The development of the new “_REPORT_FILE” command page is next.

MANUAL MAINTENANCE

July 7, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

MONDAY: An additional page in the PROJECT FILE section was needed before the The “COMMAND SEQUENCE” page could be updated.  This page titled “COMMAND LINE REPORT FILE” provides an overview of the new command line reporting capabilities that have been added to the Programmable Software Development Environment. It has been successfully added to the “PROJECT FILE” section of the Manual. I should now be able to modify the  “COMMAND SEQUENCE” page.

TUESDAY: The “COMMAND SEQUENCE” page of the PROJECT FILE section has been modified.   The “Display Command” page will next be moved to a dedicated sub-directory.

THURSDAY: The “Display Command” has been successfully moved to a dedicated sub-directory.  The “_SET_TAB Command” page will be moved next to a dedicated sub-directory.

MANUAL MAINTENANCE

June 29, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

THURSDAY: The PROJECT FILE COMMANDS page has been successfully moved to a dedicated sub-directory.  The COMMAND SEQUENCE page will be moved next to a dedicated sub-directory. It will also be modified to include the new commands.

MANUAL MAINTENANCE

June 15, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

FRIDAY: In response to the modifications to the Programmable Software Development Environment to provide the capability of preparing a text file copy of the command line screen display, I will need to modify the project file section of the manual. When I originally prepared this section, I did not have multiple levels of the development task file.  This has greatly simplified my upgrade activities of the software parts section. I should probably “Bite the Bullet” and start the revision of the project file section. This will be a major effort.  Once done, I can release this version of the Programmable Software Development Environment.

SATURDAY: I have examined the project file section directories and have a plan for its update. This will basically involved putting the files defining each of the pages into dedicated sub-directories. This will greatly simplify the design philosophy and will make it much easier to add the new commands. The project file’s overview page will be the first one to be moved to a dedicated sub-directory.

TUESDAY: The OVERVIEW page of the PROJECT FILE section has been moved to a dedicated sub-directory.  The FILE UPDATE CONSIDERATIONS page will be moved next to a dedicated sub-directory.

THURSDAY: The OVERVIEW page of the FILE UPDATE CONSIDERATIONS section has been moved to a dedicated sub-directory.  The PROJECT FILE COMMANDS page  will be moved next to a dedicated sub-directory.

Can Programming Be Strictly Portable Relative To Language?

June 15, 2012

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

FRIDAY: The Monte-Carlo checkout/testing process of the copy certification library has been started. Specifically, a software part test file and test library is prepared for each Monte-Carlo test condition instead of a test source file.

MONDAY: The functionality of the copy certification library has now been successfully tested. An upgrade to the script library was required.  The resistance of the copy certification library to errors in its use will now be tested.

TUESDAY: The copy certification library has now been successfully tested. It will now be applied to the portable software development process. I am very pleased with the TEST_PROJECT capabilities of the Programmable Software Development Environment. It has greatly increased my capabilities in bringing a library under development to a released status.

MANUAL MAINTENANCE

June 8, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

THURSDAY: The Output File Commands, Output File Management Commands, Output File Write Commands, and Input File Commands tables of contents have been prepared.

Is Strictly Portable Web-Site Development Possible?

May 18, 2012

The activity associated with the maintenance of whatifwe.com web-site be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the web-site files using the Programmable Software Development Environment.

THURSDAY: The web-site development process has been restarted.  A two step process is used to prepare the web-site from named blocks of text contained in an input text file,  This basic process is not only used in the development of an “*.html” but also other text files such as resumes.  As a consequence, an effort to develop a common libraries for the processing of the input text file has been started.

MANUAL MAINTENANCE

April 27, 2012

The activity associated with the maintenance of Programmable Software Development Environment Manual be presented here. Of critical importance is the use of strictly portable (Win32, Linux) standard methods for preparing the associated “*.html” files.

SUNDAY: The software part file table of contents has been successfully updated. To prepare for the next step, the return linkages in the pages referenced by the software parts file table of contents need to be updated using Front Page.

MONDAY: The return linkages in the pages referenced by the software parts file table of contents need to be updated.

TUESDAY: The Software Parts Definition table of contents has been prepared. The Program Control Instruction table of contents is next.

WEB-SITE MAINTENANCE

September 9, 2011

MONDAY: There are a number of software parts that are common between the development of the Programmable Software Development Environment manual and the web-site.  A common library is being prepared for these software parts.  These parts will be integrated into the Web-site development project first.

TUESDAY: The software parts in both the web-site and html common libraries for entering special phrases has been developed and tested.

WEDNESDAY: The web-site software parts for specifying the table of contents has been developed and tested.