Archive for June, 2012

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.

Advertisements

Can Programming Be Strictly Portable Relative To Language?

June 29, 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++.

SATURDAY: The role of the common includes library has been significantly simplified. Specifically, it will define the certified copy process, define the sequence of includes command, and simplify the source code writing process. A quick revision and test process is anticipated.

SUNDAY: The preparation of the common include library has begun. Those software parts that are associated with system files have been tentatively prepared. To implement the potentially required multiple certified reproductions, a minor revision to the certified copy library will be required.  This revision will be the next task.

TUESDAY: The needed revisions to the certified copy library have been made and tested. The next task is the preparation of the common include software parts associated with the data files.

THURSDAY: The modified software parts associated with the common include library has been prepared. Preparation of the common include library is the next task.

Can Programming Be Strictly Portable Relative To Language?

June 22, 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++.

SATURDAY: The common names-include software parts kit is next on the modification list. Specifically, it will be adapted to be compatible with the copy certification library.

MONDAY: The common names-include software parts kit has been modified to take full advantage of the benefits of the copy certification library. This has resulted in a much simplier design.  Preparing ths software parts kit for formal test is the next step.

THURSDAY: The common names-include software parts kit has been formally tested. Updating the common include software parts kit is the next step.

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.

Can Programming Be Strictly Portable Relative To Language?

June 8, 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++.

WEDNESDAY: The development of a copy certification library has been a difficult challenge.  This library enables the service task to prepare a certifiable script that can be run in the client class. Cryptographic methods are being used to certify the communication process.  The primary challenge has been implementing the optional capability for the client class to become a service class for a subsequent process.  The preparation of the  associated software parts has been accomplished.  The actual generation of the library and its subsequent test is the next step.

THURSDAY: The copy certification library has been prepared.  Its subsequent test is the next step. This test technique is different than what has been done previously.  Specifically, a software part test file and test library is prepared for each monte-carlo test condition instead of a test source file.

Open Source Software Development Tool: Upgrade Progress

June 1, 2012

It is planned to update the Programmable Software Development Environment to provide the capability of preparing a text file copy of the command line screen display.  It is also planned to update the debug screen menu to provide the capability of making a comment (which would be recorded in the screen display file). A person desiring to learn how to use this program would want to look over my shoulder when I am using it.  This screen display file would provide an equivalent capability.

SATURDAY: A Programmable Software Development Environment system error resulted when the debug command “;<—-” is used on the _KEYBOARD command. This error is caused by an interaction between the keyboard requirements of the debug and the _KEYBOARD commands.  I will look into possible solutions. Until I find a solution, do not use the “;<—-” command on the _KEYBOARD command line.