Archive for July, 2010

HTML RESEARCH STATUS REPORT-2010/07/30

July 30, 2010

The user’s manual for the Programmable Software Development Environment using the tool is now being prepared.  all of the pages associated with the Introduction have been completed.

The effort to build a resume using the tool has been started.  The two biggest challenges are 1) to prepare a process that is strictly portable between an *.html and *.txt files; and 2) render the document “printer-friendly”.

As I have mentioned before, strict potability is a non-negotiable requirement of my efforts.  The *.html software development process and parts are strictly portable between the Linux Ubuntu 904-32 bit, Linux Ubuntu 919 64-bit and Windows XP professional operating system.  I do not anticipate any serious problems in accomplishing strict portability between *.html and *.txt file development.

Advertisements

ERROR-2010/07/19-UPDATE

July 24, 2010

The following error has been encountered while doing the *.html software parts development

PCG ERROR: Precfile — 1675
PCG ERROR: Precfile — 1569
PCG ERROR: Precfile — 1292
PCG ERROR: precoper — 1737
PCG ERROR: precsrce — 597
PCG ERROR: srcproj  — 2281
PCG ERROR: devproj  — 1507
PCG ERROR: mainprj  — 1281
PCG ERROR: explrpde — 168

The error resulted from a system error condition.  Specifically, while processing a text file, the system routine “ftell” returned the -1 error status. Furthermore, a single Line Feed character was read by system routine “fgets”.

I decided to replace the text read routine “fgets” for the binary routine function “fread” and manage the sequential reading of the text file myself.

This effort resulted in a significant surprise.  Specifically, the format of a text file is a bit informal.  Sometimes the line is terminated by a CRLF and sometimes it is terminated by just a LF alone.  To maintain my strict portability requirement, I redesigned the text file input routine to accept both formats.  This appears to be functional in both the Windows and Linux Ubuntu 9.04-32bit and Ubuntu 9.10-64 bit environments.

The _STATE_READ_TEXT command needs to be tested and updated as necessary.   This will be
done incidentally to the development of the *.html standard software parts kits.  I expect to publish the new version in about a week.

ERROR UPDATE–2010/07/19

July 23, 2010

The following error has been encountered while doing the *.html software parts development

PCG ERROR: Precfile — 1675
PCG ERROR: Precfile — 1569
PCG ERROR: Precfile — 1292
PCG ERROR: precoper — 1737
PCG ERROR: precsrce — 597
PCG ERROR: srcproj  — 2281
PCG ERROR: devproj  — 1507
PCG ERROR: mainprj  — 1281
PCG ERROR: explrpde — 168

The error resulted from a system error condition.  Specifically, while processing a text file, the system routine “ftell” returned the -1 error status. Furthermore, a single Line Feed character was read by system routine “fgets”.

I decided to replace the text read routine “fgets” for the binary routine function “fread” and manage the sequential reading of the text file myself.

This effort resulted in a significant surprise.  Specifically, the format of a text file is a bit informal.  Sometimes the line is terminated by a CRLF and sometimes it is terminated by just a LF alone.  This may be caused by the fact that I have a strict portability requirement between the Linux and Windows operating system and have used the files on both systems.  It is also interesting to note that both systems appear to be reasonably tolerant of both forms.

To maintain my strict portability requirement, I redesigned the text file input routine to accept both formats.  This appears to be functional in the Windows environment. I will now test it in Linux Environment.

ERROR CAUSE–2010/07/19

July 21, 2010

The following error has been encountered while doing the *.html software parts development

PCG ERROR: Precfile — 1675
PCG ERROR: Precfile — 1569
PCG ERROR: Precfile — 1292
PCG ERROR: precoper — 1737
PCG ERROR: precsrce — 597
PCG ERROR: srcproj  — 2281
PCG ERROR: devproj  — 1507
PCG ERROR: mainprj  — 1281
PCG ERROR: explrpde — 168

The error resulted from a system error condition.  Specifically, while processing a text file, the system routine “ftell” returned the -1 error status. Furthermore, a single Line Feed character was read by system routine “fgets”.

I have read a lot of text files by the precfile routine which uses these routine and have experienced no difficulties until this event.  Several questions still remain unanswered:

1.  Did the way that I transferred the manual text file to this file create the problem. I believe that I may have directly copied it from the FireFox screen and cleaned it up afterwards. (I need to learn again to never do this!).

2.  Did I encounter a system problem.

3.  Is there some specific processing problem in precfile.

I have made a error reporting patch so that I can easily identify and explore this situation.  I believe that my text transfer method may have created the error. I need to explore this situation to determine the correct solution to this problem.

ERROR ALERT–2010/07/19

July 20, 2010

The following error has been encountered while doing the *.html software parts development

PCG ERROR: Precfile — 1675
PCG ERROR: Precfile — 1569
PCG ERROR: Precfile — 1292
PCG ERROR: precoper — 1737
PCG ERROR: precsrce — 597
PCG ERROR: srcproj  — 2281
PCG ERROR: devproj  — 1507
PCG ERROR: mainprj  — 1281
PCG ERROR: explrpde — 168

The cause of the error is, at the present, unknown.  It is probably due to improper user error processing and anyone encountering this error should carefully debug their product.  The required effort will begin today to determine the cause and make the needed corrections.

HTML RESEARCH STATUS REPORT-2010/07/16

July 16, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized html files such as used in a users manual. In particular, an effort to rebuild the user’s manual for the Programmable Software Development Environment using the tool is progressing.

The development of software parts for The Bullet Lists and a single entry point for header information has been accomplished.

At the present time, the software parts libraries appears to be adequate relative preparing the programmable software development environment manual.  The only additional capabilities that might be needed would be the capability of changing the format of special phrases of text; i.e., italics, bold-face, or underscore. A method for providing this capability in a convenient way is still evolving.  Also, there may be a need for a numbered list.

It has also become apparent that this technology may be useful in the preparation of resumes. These documents are different than the manual in a very significant way:  The manual is a collection of single page files coupled together by a system of linkages where as the resume is usually a single multi-page document.  None-the-less, LinkedIn will accept a *.html file resume.

The basic question being considered today is whether I will start to rebuild the manual or add the capability needed to build the resume.

CPP-CSHARP PORTABILITY STATUS — 2010-07-08

July 9, 2010

In the pursuit of standard methods and processes that are rigorously portable between C++ and CSHARP, a new challenge has been encountered. Specifically, I am running out of post office files.  Currently, the Programmable Software Development System provides a maximum of 16 post office files for a source development sub-task.

The challenge was encountered while developing the CSHARP standard parts kit for preparing a routine associated with a specific class.  The development process based on a “driver philosophy” was progressing normally until I attempted to provide the scripts required to call a public routine of another class.

Currently, there are four post office files associated with each class:  An “includes” post office file for the other classes needed, a “typedef” post office file to contain the approved data types, a “structure” post office file to contain the data structure associated with the class, and the “class” post office that defines the actual class.  A significant mailbox management process resulted when I started processing a call to routine in another class,  Also, only four such calls could use up my post office file resource.

As required in the Deming Cycle, one needs to be sensitive to difficulties encountered in the execution of a plan and respond by changing the plan as required.  The mailbox communication structure of this project needs to be reconfigured and simplified with the goal of having no more than one post office files needed for each class.  Then routines belonging up to 14 different classes could be called by a specific routine (the routine and its class has a post office file).

This revision has been started  with an upgrade of the post office management software parts kit and the the “includes” post office software parts kits.

HTML RESEARCH STATUS REPORT — 2010-07-02

July 2, 2010

The development of the latest version with the capability of reading up to 16 text files has made it possible to prepare specialized *.html files such as used in a users manual. In particular, an effort to rebuild the user’s manual for the Programmable Software Development Environment using the tool is progressing.

The software parts needed to prepare the table of contents and a page with one or more paragraphs have been completed.

The remaining tasks are 1) Bullet Lists, 2) Numbered Lists and 3) an upgrade to facilitate the entry of header information: Book Title, Version, Copyright, and contact information.  In particular, a single entry point for the entire book is needed.  This can be easily accomplished with the Post Office Commands.

As in all of my development activities, strict portability between the Linux and Windows operating systems is being rigorously maintained.  Strict portability greatly reduces the effort and cost associated with upgrading the operating system or replacing the computer.

I have worked on either system with all of the defining files on a Flash Drive. Soon I will be able to operate exclusive off of a large flash drive which includes the operating system.