![]() |
This job jar and diary is part of the nfoWare Project-Template creation project.
Status |
Date |
Description |
2004-04-02 | I am going to use red captions in the project descriptor block but I don't know about the font. So I have two different forms in the template right now, and I will choose soon. | |
2004-03-19 | There is an interesting problem about versioning of P000006a since pages made from it often refer to it as their origin, both by explicit hyperlink and by a comment in the HTML <head> element. Something to look at, and perhaps handle as a bootspiral, is to ground the versions of templates and have a way to identify the one used in a case and also learn that there is now a later one. That is, I should not use a URL that stands for the latest one as the provenance of an use of a specific one that was latest at some earlier point in time. This may completely turn around how I look at versions. This is a topic in itself to be introduced in a note of some sort. | |
done 2004-04-01 |
2004-03-19 | Add "ad hoc" and "bootspiral" as approaches/methodologies for conduct of a project. |
done 2004-04-01 |
2004-03-19 | Add a second subordinate page to the template that will be the source of nomenclature links and terminology, other explanations, for project descriptions made with this template. |
done | 2004-03-09 | Correct the title of this page. |
done | 2004-03-09 | Add comments to the P040200 page so that people know it is a boilerplate and very raw. Remove the hyperlinks from the boilerplate that are bogus here. |
done 2004-04-01 |
2004-03-06 | Find out how the FrontPage Format Painter works and see if it can be applied to style template and preservation problems I am having. I want something that preserves format entirely server side and preferably with the static page. If I use CSS, I don't want to depend on the client being CSS capable or fully implemented. [dh:2004-03-06: It should work as a manual device. I am not sure it will work for a definition pair, but we can experiment. dh:2004-04-01: It doesn't seem to]. |
2004-03-06 | Find a way to have divisions work to impose reduced font size on definition lists, such as those used as histories at the bottom of pages like this one. The <small> tags keep being moved by FrontPage, and even put in ways where they are improperly nested. There must be a cure for this. | |
2004-02-29 | Confirm that division can be used to impose reduced font size on table entries in a consistent way, without having the sizes change from one table element to the next. Try it on this table first. | |
done | 2004-02-29 | For pages ending in tables, put the bottom horizontal rule between the history and the footing construction block. Confirm this with P000000, P000001, P000006, P000006a, P040200, and P040200a. Roll up to the construction section and reflect on all other diary pages, including in the notes section. |
done 2004-02-29 |
2004-02-28 | Have the top title block preserve paragraph style, font style, font size, and link and non-link colors in P000006, P000006a, P040200, and P040200a. |
done | 2004-02-28 | Have HTML 4.01 compliance on all pages P000006, P000006a, P040200, P040200a. Roll up to the project section also. |
done | 2004-02-28 | Have the correct font on the timestamp in the title block too: P00006, P00006a, P040200, P040200a. Roll up to the project section also. |
2004-02-28 | Somewhere we need to deal with the toolcraft of site creation (covered in the construction section), such as the use of FrontPage techniques for handling things. This could be toolcraft too, if we are willing to do that but I think we are not. We are willing to have it be a construction technique, and be part of bootstrapping, just like use of VSS, but toolcraft should somehow involve confirmable, inspectable, open-source implementations. At some point, we need to face up to and account for the disparity here. Split this over to the Notes section? I also want to mention resources and tools for use of FrontPage and for other style purposes. | |
done | 2004-02-28 | Make sure that all pages of P000006, P000006a, P040200, and P040200a have FrontPage styles for standard nfoWare pages. Roll up to other pages of the Projects section. |
done 2004-02-29 |
2004-02-28 | Make sure that the title block font selections are properly reflected in P000006, P000006a, P040200, and P040200a. Roll up to other existing pages so they are manually synchronized with the style here. |
done | 2004-02-28 | Clone a version of the P000000 projects job jar & diary for creation of the P000006a project diary template version 0.00. This is a manually-customized template. |
done | 2004-02-28 | Clone a version of the P000000 projects job jar & diary for creation of this P040200a diary. |
done | 2004-02-28 | Clone an intermediate version as P000006, the project template material that we are building. |
done | 2004-02-28 | Change the title block and bottom block to fit with the current nfoWare style requirements. |
done | 2004-02-28 | Clone a project page from DMware/projects and use it as the initial skeleton for this project's top page. |
done 2004-02-29 |
2004-02-28 | Make the Word "Project" in the title blocks link to the project catalog in all cases, no matter what level we are in a project description. Do this on this page, on P040200, on P000006, and P000006a. |
2004-02-28 |
I am starting this as a bootstrap of the Create Project Template project. That means there is no template for this page other than the skeleton purloined from the Projects Job Jar & Diary and the boostrap of P040200 itself. So, one part of the bootstrap problem is that the project for creation of the template will not be built with that template. And I don't think I will be "recompiling it" with the template that is its product. What I expect is that I will manually align the template and this project's project pages, and somehow reflect that. P040201 will be the first application of a completed template. |
|
started 2004-02-28 |
2004-01-06 | I need to create a standard project form. I will look at DMware and see how to do that. There are examples in ODMA and maybe other places too. Can this be done as a project? Why bother? dh:2004-02-28: It illustrates spiraling and there are more aspects that come up, including making a FrontPage template, having links to field definitions and related items, dealing with current and past templates for archived projects, etc. |
![]()
|
created 2004-02-28-12:06 -0800 (pst) by orcmid |