Posts Tagged ‘document preparation portability’

Open Source Software Development Tool: Upgrade Progress

July 9, 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.

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.

TUESDAY: 2013/07/09

STATUS: I have started revising the Programmable Software Development
Environment manual and have updated the Overview for the Output Write
Command.

DETAIL: All of the documentation associated with Output File Write
commands is found on one page and was written using Microsoft Front
Page. It is important to me to eliminate my dependence upon this
application.

RESULTS: The Overview has been successfully modified using the
Programmable Software Development Environment. This process will
continue until all of the Output File Write commands including
_WRITE_SEGMENT have been prepared using the Programmable Software
Development Environment,

NEXT TASK: The next task will be to update the documentation associated
with the _WRITE_OUT command.

Open Source Software Development Tool: Upgrade Progress

December 21, 2012

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.

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.

THURSDAY: The new utility routine for precfile.cpp for completing a string of characters read from a “paste-in” file has been prepared. The next step will be to continue the required integration efforts.

Development of Presentations

September 12, 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 FRIDAY ACTIVITY: The presentation project was set up and the files defining her recommendation were converted to the HTML format.  It is planned to first present how it worked on a real document.

PRESENTATION SATURDAY ACTIVITY: The overall outline, i.e., the table of contents, was prepared.

PRESENTATION MONDAY ACTIVITY: The purpose page of the resume development application was prepared. Of particular importance is its capability to easily customize the document and to have an output file that can be easily pasted into a web-site.

PRESENTATION TUESDAY ACTIVITY: The defining files page of the resume development application was prepared. I need to think about what the next page will be.  It could be a “Rules of the Road” page or the first of three document defining files. It is important to note that I do not directly write documents; I design them in a similar manner as I design software.

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 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.

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.

MANUAL MAINTENANCE

May 25, 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.

TUESDAY: The Basic Register Command Capabilities table of contents has been prepared. The Output File table of contents is next.

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.