Posts Tagged ‘Automated *.HTML generation’

Open Source Software Development Tool: Upgrade Progress

December 17, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

Currently, the Programmable Software Development Environment has the
capability of reading a standard ASCII text file where the TAB
character is replaced with a suitable number of blanks. Each line of
the text file cannot be longer than 256 characters. On the other hand,
the Programmable Software Development Environment has the capability of
writing a paste-in text file where each paragraph is one very long
line. This capability includes the ability to include special
characters such the TAB.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

MONDAY: 2013/12/16

STATUS: I have re-documented the _TEXT_NAME manual page.

NEXT TASK: The next task will be to update the _TEXT_PATH manual page.
There are three more pages to update.

Advertisements

Development of Utility Libraries

November 9, 2012

The activity associated with development of utility software parts libraries will be presented here.

CERTIFICATION BLOG: Inorder to certify that a product has been developed in strict compliance with the specified standards and has not been patched, pseudo-random longitudinal parity bits must be included in source code in the form of comments. These comments can be at the end of each line (C, C++, C#), at the beginning of each line (HTML), or at the end of each statement (Visual Basic).  This blog will present the research and development section associated with upgrading the existing output library to facilitate both the generation and the testing of all three forms of product source code.

CERTIFICATION TUESDAY ACTIVITY: There are existing libraries for writing source code. One of these libraries writes source code with the parity bit at the end of each line.  The other writes at the beginning. There is no well-developed way of testing the parity at this time. The first step is to define a structure which will facilitate the writing and testing of all three output formats.

CERTIFICATION WEDNESDAY ACTIVITY: It occurred to me last night that in the development of a software source file, there are two checkout / formal testing phases; one to certify the proper preparation of the source file and the other to certify its proper execution.  Arrows and dates will be used to record the status of both phases. As a consequence, it is probably easier to use a separate comment line at the end or beginning of each source statement to report the status of the statement and contain the parity bit.

CERTIFICATION THURSDAY ACTIVITY: There are three basic forms of output file: Programmable Software Development Environment files; source code files, and document text files. The Programmable Software Development Environment files will always have a comment at the end of the line with the parity byte.  The source code files will have a comment line following each statement with the parity byte. The document text file has no comment. In this case certification information can be added to the text by randomly increasing spaces from one to two blanks.

Development of Presentations

September 28, 2012

The activity associated with development of presentation documents that can be used over the Internet or in a group meeting.

I met Tisha Silvers, a Marketing Strategist on a LinkedIn Group Discussion. She show sufficient interest in my technology that I eventually wrote her a recommendation.

I wrote her recommendation with my resume development application (software parts library). I subsequently offered to show her how I wrote this document. I felt that this might be easiest way for her to relate to my technology. She accepted this plan.

I chose my manual development application as the means of preparing this presentation. This application builds documents in the HTML file format. These files can be presented over the Internet, at a group meeting using a projecting computer, and can be printed for further reference.

I will present my presentation development activities on this blog.

PRESENTATION WEDNESDAY ACTIVITY: I have completed the first rough draft version of the presentation and have sent a copy of it to Tisha Silvers for her comments.  If anyone desires to get a copy, please provide me with your email address and I will send you a copy.

Development of Presentations

September 21, 2012

The activity associated with development of presentation documents that
can be used over the Internet or in a group meeting.

I met Tisha Silvers, a Marketing Strategist on a LinkedIn Group
Discussion. She show sufficient interest in my technology that I
eventually wrote her a recommendation.

I wrote her recommendation with my resume development application
(software parts library). I subsequently offered to show her how I
wrote this document. I felt that this might be easiest way for her to
relate to my technology. She accepted this plan.

I chose my manual development application as the means of preparing
this presentation. This application builds documents in the HTML file
format. These files can be presented over the Internet, at a group
meeting using a projecting computer, and can be printed for further
reference.

I will present my presentation development activities on this blog.

PRESENTATION TUESDAY ACTIVITY: I have decided that the next page will
introduce the recommendation text file and three document generation
files that defined it.

PRESENTATION WEDNESDAY ACTIVITY: I have completed the page that
introduces the recommendation text file and three document generation
files that defined it. The page describing the header/special phrases
is next.

Is Strictly Portable Web-Site Development Possible?

August 16, 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.

MONDAY: The last update of the Programmable Software Development Environment revealed the desirability of updating the web-site. I do not want to perform this effort using Front Page. I plan to restart my development of the software parts libraries associated with web-site development.  To accomplished this, I must update the test program that I am using for all of my formal testing. This will be started as soon as possible and reported in the “Economical Rigorous Software Testing at All Levels”. topic.

MANUAL MAINTENANCE

August 16, 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 Manual Update has been completed.  Please track the completion of this Programmable Software Development Environment update project in the “Open Source Software Development Tool: Upgrade Progress”. Section.

MANUAL MAINTENANCE

August 10, 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: The “_REPORT_FILE” has been successfully prepared. The development of the new “Report Generation Commands” page is next.

MONDAY: The development of the new “Report Generation Commands” page has been successfully completed. I believe that the current version of the manual is adequate for the new version of the Programmable Software Development Environment. The common line screen reporting capabilities are important for our communication. The next step will be to proof the manual. When completed, this version of the Programmable Software Development Environment can be prepared for publication

TUESDAY: My first examination of the Manual revealed link errors that have been corrected. I also observed some deficiencies in the documentation of the Project File relative to the Command-Line Report Generation File. My next task will be to re-examine and correct these deficiencies.

THURSDAY: The observed deficiencies in the documentation of the Project File relative to the Command-Line Report Generation File have been fixed. A second overall review of the manual needs to be made and then this version of the Programmable Software Development Environment can be packaged for upload. It is also important at this time to review the web-site for needed upgrade.

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.

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.