Posts Tagged ‘Mr. Mike’

Developing a Website using a software parts library

October 3, 2014

The activity associated with development of a software parts library for the development of a web-site will be presented here. This will be an extension of the library used to prepare Programmable Software Development Environment manual.

This effort was started a long time ago following the development of the manual software parts library. Its purpose was to eliminate the need for Front Page. It was subsequently put on hold so that other more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently offered to reconstruct my Web-Site. I told him my plan to use my tool to rebuild my site. He has had difficulties relating to my technology (It is quite different than normal programming methods) and I am not really skilled in Web-site design. We both felt that this might a great opportunity to make the technical connection.

FRIDAY: 2014/10/03

STATUS: I have examined the requirements of a header as presented in Mr. Mike’s web-site contribution and have developed a basic plan.

DETAIL: Two important factors were important to the plan. 1) For the most part, the headers are all the same for all of the web-site pages. The only one that is different is the title of the specific page. 2) There is a need to guarantee that all of the pages have been developed and are present.

RESULTS: A separate sub-task (We already have a sub-task for the CSS file and each of the HTML files) which specifies the title and link address for each of the HTML pages. The results of this task will be stored in a post-office which can be accessed by the sub-tasks that processes the HTML files. Using the proper system of post-offices, the heading data can be passed to all of the HTML sub-tasks and each of the HTML files is defined by one and only one sub-task.

NEXT TASK: The next task will be to prepare the web-site project for this new sub-task.

Developing a Website using a software parts library

August 6, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

TUESDAY: 2014/08/05

STATUS: While preparing a plan for the development of nested horizontal
group sections, I encountered a critical challenge. Specifically, there
are occasions where the material displayed on the screen is not to be
displayed on the printed output.

MR_MIKE_CONTRIBUTION: Mr. Mike’s proposed revisions to my website
included a link and navigation section which were displayed on the
screen and not on the printed page. These sections are on the left side
of a nested horizontal group.

DETAIL: There is, of course, a CSS means of accomplishing this task. I
need to include this capability into the rigorous set of web-site
development parts of the CSS web-site development library.

MY NEXT TASK: My next task will be to identify the optimal means of
including this capability into the both the vertical groups and
horizontal groups.

Developing a Website using a software parts library

April 25, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

FRIDAY: 2014/04/25

STATUS: While preparing the software group section parts, I observed
that all of ID and class names in Mr. Mike’s example were lower case.
It occurred to me that I should examine the literature to determine the
the syntax rules associated with these names.

DETAIL: I found the syntax rules in the Microsoft MSDN Library

RESULTS: The syntax rules (and I experimented with the whole_page class
in Mr. Mike’s examples) associated with the class names and the ID
names were essentially the same as the Programmable Software
Development Environment name.

NEXT TASK: I believe that a set of name management/communication parts
is in order and will be prepared. It will be first be integrated into
the whole page CSS software parts.

Developing a Website using a software parts library

April 20, 2014

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page. It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site. I told him my plan to use my tool
to rebuild my site. He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

2014/04/20

STATUS: I have performed the experiments needed to define the software
parts defining the group sections These sections contain header,
contents, and text sections and are identified by unique id names.

MR_MIKE_CONTRIBUTION: These experiments were performed on Mr. Mike’s
web-site contributions.

DETAIL: Two types of group sections are required: A top-to-bottom
collection and a left-to-right collection. The top-to-bottom collection
could be header, text and footer. The left-to-right collection could
be links and text. These group sections can contain other group
sections.

MY NEXT TASK: My next task will be to prepare, integrate and test the
software parts associated the top-to-bottom and left-to-right group
sections.

Developing a Website using a software parts library

March 18, 2014

The activity associated with development of a software parts library for the development of a web-site will be presented here. This will be an extension of the library used to prepare Programmable Software Development Environment manual.

This effort was started a long time ago following the development of the manual software parts library. Its purpose was to eliminate the need for Front Page.  It was subsequently put on hold so that other more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently offered to reconstruct my Web-Site.  I told him my plan to use my tool to rebuild my site.  He has had difficulties relating to my technology (It is quite different than normal programming methods) and I am not really skilled in Web-site design. We both felt that this might a great opportunity to make the technical connection.

MONDAY: 2014/03/17

STATUS: I have determined the basic definition of the standard software parts associated with the whole_page class.

DETAIL: whole_page will be defined by a software part that prepares the appropriate CSS statements. The margin and padding size will be preset. The 8% left and right margins provided in Mr. Mike’s example will be unconditionally used.  Only the background color will be specified by the argument of the software part.

MY NEXT TASK: Prepare the associated whole page software parts.

Developing a Website using a software parts library

March 5, 2014

The activity associated with development of a software parts library for the development of a web-site will be presented here. This will be an extension of the library used to prepare Programmable Software Development Environment manual.

This effort was started a long time ago following the development of the manual software parts library. Its purpose was to eliminate the need for Front Page.  It was subsequently put on hold so that other more important efforts could proceed.
 
Mr. Mike is a long time professional friend of mine who has recently offered to reconstruct my Web-Site.  I told him my plan to use my tool to rebuild my site.  He has had difficulties relating to my technology (It is quite different than normal programming methods) and I am not really skilled in Web-site design. We both felt that this might a great opportunity to make the technical connection.
 
TUESDAY: 2014/03/04
 
STATUS: I have examine web-site developed by Mr. Mike and have found that all of the styles are defined specifically in the CSS file statements.  There appeared to be no need to include html statements in the screen CSS file. An examination of the references that I obtained from the library seemed to confirm my evaluation.

DETAIL: The CSS file is a common style definition for the entire website which might consist of many pages. It appears that the html statements were included in the CSS file to take advantage this capability.

RESULTS: In the normal development process, the CSS file provides the designer with the capability of designing the style once and then using it for all of the web pages.  The Programmable Software Development Environment provides two other means of defining common elements such as the style; namely, the Software part and the Post Office communication commands.

MY NEXT TASK: My current plan to modify the previously developed software parts to remove the html statements from the screen CSS file and include them in each of the html files using no more than two software parts.

Developing a Website using a software parts library

October 8, 2013

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page.  It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site.  I told him my plan to use my tool
to rebuild my site.  He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

TUESDAY: 2013/10/08

STATUS: Two libraries, one for the CSS files and the other for the HTML
files, have been prepared with the beginning software and tested.

MR_MIKE_CONTRIBUTION: Mr. Mike, by answering my questions, has greatly
facilitated my development process.

DETAIL: The software parts that have been prepared and tested for the
CSS library are as follows:  _WEBSITE_CSS_CONSTRUCT,
_WEBSITE_SCREEN_STYLE_FILE, _WEBSITE_PRINT_STYLE_FILE,
_WEBSITE_STYLE_BEGIN, _WEBSITE_STYLE_END, and WEBSITE_CSS_DESTROY. The
software parts that have been prepared and tested for the HTML library
are as follows: _WEBSITE_HTML_CONSTRUCT, _WEBSITE_HTML_PAGE_FILE,
_WEBSITE_HTML_BEGIN, _WEBSITE_HTML_END and WEBSITE_HTML_DESTROY.

RESULTS: The two .css files and the .html file has produce the expected
display in Firefox. The Firefox Error Console display two warnings that
noted that the screen css file was not complete as yet.

MY NEXT TASK: I plan to next prepare software part that the defines the
background color and font family.

Developing a Website using a software parts library

October 6, 2013

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page.  It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site.  I told him my plan to use my tool
to rebuild my site.  He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

SATURDAY: 2013/10/05

STATUS: I have prepared a sufficient number of software parts that I
can now prepare a effort.

MR_MIKE_CONTRIBUTION: Mr. Mike’s contribution have given me a starting
point from which I can prepare my beginning software parts development
effort.

DETAIL: I have started with a experimental file that only displays the
title along the top of the web-site display program (Firefox, Internet
Explorer).

RESULTS: The files that have been prepared are as follows:
_WEBSITE_SCREEN_STYLE_FILE, _WEBSITE_PRINT_STYLE_FILE,
_WEBSITE_HTML_PAGE_FILE, _WEBSITE_STYLE_BEGIN, _WEBSITE_STYLE_END,
_WEBSITE_HTML_BEGIN, _WEBSITE_HTML_END.

NEXT TASK: The next task will be to prepare the associated library.

Developing a Website using a software parts library

October 1, 2013

The activity associated with development of a software parts library
for the development of a web-site will be presented here. This will be
an extension of the library used to prepare Programmable Software
Development Environment manual.

This effort was started a long time ago following the development of
the manual software parts library. Its purpose was to eliminate the
need for Front Page.  It was subsequently put on hold so that other
more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently
offered to reconstruct my Web-Site.  I told him my plan to use my tool
to rebuild my site.  He has had difficulties relating to my technology
(It is quite different than normal programming methods) and I am not
really skilled in Web-site design. We both felt that this might a great
opportunity to make the technical connection.

TUESDAY: 2013/10/01

STATUS: The development of the software parts required for the web-site
development kit library has been started.

MR_MIKE_CONTRIBUTION: Mr. Mike has prepared most of my web-site pages.

DETAIL: Three software parts have been prepared. _WEBSITE_CSS_CONSTRUCT
and _WEBSITE_HTML_CONSTRUCT initializes writing / certifying process
for the associated files. _WEBSITE_DESTROY resets the system for the
next sub-task.

MY NEXT TASK: The development of the software parts associated with the
preparation of the .css files will be developed first. Currently, I
plan to write both the screen and print related files in the same
sub-task.