devNotes
Diary & Job Jar
|
|
devNotes |
|
Status |
Date |
Description |
|
| in progress | 2007-07-24 |
|
|
| in progress | 2007-07-24 | Review the devNotes content pages for case-sensitivity among page names, URL links, link texts, and text mentions: d060101, d061001, d061002, d061003, d061101, d061201, d070201, d070701 | |
| in progress | 2007-07-24 | While performing reviews, identify any additional adjustments that are required to have consistency with the latest formats, styles, and organization of materials. | |
| in progress | 2007-07-24 | Have the normal-content construction-structure images links upward to the appropriate construction zone, or other superior structure. [dh:2007-08-24 The construction structure linking adopted for the nfoWare repaving will be instituted here too.] | |
| 2007-09-29 | There is a change that needs to be made in the use of fonts in the upper-right corner anchor block of standard folio pages and construction-structure pages. This change needs to be propogated through all devNotes and it needs to be figured into the repaving. | ||
| 2008-01-29 | There is a change that is also needed to the use of fonts on the interior of pages, wherever monospace is intended. Check in the attribution block at the bottom of folders to make sure this is accomplished, especially in 2007/10, which is expected to be stable. All use of fixed-pitch fonts need to be changed to be monospace font faces. | ||
| 2008-04-23 | d080402: Make into an About document-engineering folio modeled on the version for nfoWorks, starting with publishing of the current ODMdev.htm page | ||
| 2007-08-15 | d070701: Revise with addition of 0.59beta as part of the preview material | ||
| 2007-08-15 | d061201: Revise with addition of preparation for 0.59beta in the deployment | ||
| 2007-08-15 | d061001: Revise with addition of preparation for 0.59beta | ||
| 2007-07-15 | Decouple the revision of the ODMA headers from ODMNative100 and reflect as a different project in the source-control tree. | ||
| 2007-07-12 | Review Notebooks for items that should be tracked here, especially for capturing future-steps thinking. | ||
| 2007-04-26 | Review for how we are going to handle devKit versus devNotes, if at a separate level or not. How is the ODMJNI development tree related to the devKit, etc. | ||
| 2007-02-24 | Decouple OdmNative100 from ODMJNI, even though ODMJNI is the first use of it. These components develop independently and can be used directly in C/C++ applications and in other Windows-based execution models (possibly .NET, COM, and others). | ||
| 2006-11-27 | When lifting the embargo, review all license copies and statements to make sure that they include the relevant manifests by reference and by summary, as appropriate. [dh:2007-03-25 I will probably move the material to the un-embargoed locations and then clean it up.] | ||
| 2006-01-21 | When the C/C++ Materials are updated on nfoWare, and then the ODMA FAQtips are modified to rely on those too, reflect that here so we can appeal to the toolkit setup as part of the initial confirmation experiments. | ||
| 2006-01-18 | Check nfoWare notes for any additional structure required of the setup here. | ||
| 2006-01-17 | Create a devNote for document-engineering the ODMdev.htm page. | ||
| 2005-11-03 | Move the choice and installation of the VCTK into a devKit and include-page ... oops, can't do that. It would be crossing a sub-web and include pages won't do that. I need to figure out how to keep the kits self-contained while also reusing that material. | ||
| 2005-11-02 | In the documentation of the downloading and installation of Microsoft Visual C++ Toolkit 2003, change for creation of a MyProjects folder, not MyPrograms. Then all of the Scampo and Blocco examples will work. | ||
| 2005-11-02 | Document the meshing of multiple source-code-control systems. This will tie into internal techniques for identification of versions and variants in the source codes themselves. | ||
| 2005-11-02 | The description of ODMdev must account for (1) the construction and creation of ODMdev, (2) being an ODMdev developer, (3) mirroring of ODMdev and setup for VSS/SCM at the mirror, and (4) branching/getting into private projects for confirmation, use, making derivative materials, etc. | ||
| 2005-11-02 | Document the creation of a separate MyProjects (or other name) as a place to make variants and carry out experiments. This becomes a way to use an ODMdev mirror as a basis for populating source control and sharing/copying under MyProjects for confirmation experiments, other activities, without disturbing the ODMdev source. This also provides for quarantine of new updates to ODMdev so that dependencies on ODMdev can be managed effectively. | ||
| 2005-11-02 | Create ODMdev \2005\11 as the initial devKit project and folio structure. [dh:2005-11-03 Fill in the scaffolding and use the default construction zone. The devKit catalog and job jar will deal with content-development materials.] | ||
| 2005-11-02 | Create ODMdev \template\00 as a template structure for any devKit templates to use in creating materials. [dh:2005-11-03 Fill in the scaffolding and use the default construction zone.] | ||
| 2005-11-01 | Using WinZip as an alternative way to open ODF packages and Microsoft Office Open XML packages needs to be documented somewhere as part of ODMref and nfoWare materials. These may end up being documented for different aspects in different places. | ||
| 2005-11-01 | Document detection of Zip support and installation of WinZip 9.0 in a way that preserves the existing support while allowing context-menu use of the WinZip functionality, the self-extraction creator, etc. | ||
| 2005-11-01 | Document setting up to ODMdev.bat and ODMdev.lnk to have the desired features for the console window, fonts, etc. | ||
| 2005-10-31 | ODMdev.bat needs a link to a more-precise location for advice and discussion. There needs to be a package and a basic setup. [dh:2005-11-03 This looks like a Dyymmnn creation, not a construction creation even though there is overlap.][dh:2006-01-01 These need to have .txt extensions and be handled accordingly. There needs to be a better way to transfer and customize them.] | ||
| 2005-05-13 | Rebuild all of the confirm projects to verify operation with the new structure. | ||
| 2005-05-13 | Adjust the ODMdev.bat file to use the new locations for non-redistributable software. | ||
| 2005-04-22 | Correct the batch files to use the new name in the path, environment variable, and other settings. | ||
| 2005-04-01 | In the job jar for DeRisk01 list all of the materials to be described, the different experiments, and what is to be done next to make the material presentable. We can start job jars early using just an invisible C000000 until the construction structure is complete. [dh:2005-10-01 I now know to do a development pack using the folio concept. That will help us a lot. The packaging into Zips gives us a little practice at software asset packaging too. Fancy that.] | ||
| 2005-04-01 | At the beginning of DeRun02 creation in DeRisk02, see what difference it makes to use puts and putchar instead of printf. (Use simple names like printc, println, prints, borrowed from the Java stdio concept.) [dh:2005-10-01 This is just about the granularity of the linking that happens, since we are doing tight binding with non DLL run-time libraries. We want to do that, but we also need to know how much unreferenced deadweight comes in from the standard libraries.] | ||
| 2005-04-01 | Create a construction structure in each of derisk01 and derisk02. Remember to rehook the index.htm pages. | ||
| 2005-03-30 | There is an nmake and other utilities included in the %MSDK%\bin\Win64 folder and I don't know what the conditions on those are. It looks like the nmake runs on Windows XP, but I am not sure what its usage might be and what the limitations are. [dh:2005-10-01 The Binary Dump utility works fine though. I should looke to see what else works. I need to look at the Windows 2003 edition of the Platform SDK -- April 2005 edition and see how that works.][dh:2006-01-17 It turns out that these basic utilities are included with the Visual C++ 2005 Express Edition.] | ||
| 2005-03-30 | The libraries actually needed from the VC++ Toolkit 2003 need to be understood better. At some point I need to reconcile them with those of the Platform SDK too. | ||
| 2005-03-30 | I need a discussion of the first tools needed (browser and ZIP, say) and then the next ones, etc. This needs to be somewhere here. It looks like at the top level or in confirm. I don't think of needing a construction section here. [dh:2005-10-01 I was also thinking of having a %ODMdev%/setup folder. That would then be installed with the devkit. That might be a reasonable thing to do. I need to think about that some more. Maybe there needs to be something in the ODMA.info/active subtree instead, so that I don't get into the problem of having web pages in an ODMA.info/dev/setup that must work properly on an %ODMdev%\setup hard-drive location.] | ||
| 2005-03-30 | A version of md5sum was intended to be a tool of nfoWare. That connection would be useful, but not just yet. [dh:2005-10-01 I can now start nfoWare /dev in parallel. There will be no problem on local machines because the dev directories (i.e., %ODMdev% and %nfoDev%) can be in peer subtrees of a set of development projects.] | ||
| 2005-03-30 | Add something in tools to reflect the use of md5sum and the creation of md5 sums on all of the files that we have around here. Document the convention where the check file may have a name that is more informative than the file being checked, and can reveal versions (e.g., with the ODMA run-time). [dh:2005-10-01 I have no idea what that last part is about. Oh, yes, the check file may have a version-specific name even though the files in the package have generic names (and we tend to put them in a subdirectory that avoids name collisions. OK, got it. Yes, do that. But it looks like MD5 is just for play. We need at least an SHA256 equivalent when things get serious.] | ||
| 2005-03-30 | The dev/ and the ODMdev.bat file needs to be organized, if possible, so that the VC++ Toolkit /include and /lib directories are not used directly. This is so they can be used and preserved independently of the changes in releases that might occur. This should be a modest amount of material, and not a major problem. Do it when the mitigation pressure has abated, and before we conduct the ODMref engagement. [dh:2005-10-01 I need to make a decision, real soon now, whether this is done through VSS and I really bring the files over under dev/nodist or whether I continue to use the paths to the locations of the installation on the assumption that any later VC++ toolkit will be installed in a different Program Files location. I think I'd rather leave the toolkit in place, in this regard, because I don't want to comingle those basic libraries and headers with what we will be pulling in form Platform SDKs, which are likely to change more frequently. This also means that we won't be so willing for people to use the compiler from Visual Studio rather than from the toolkit, and that seems fine from a stability-preservation perspective. This should be documented and narrated.] | ||
| 2005-03-29 |
We want the dev section and the devkits to be
self-contained, so that it is easily configured to operate properly on
an user's configuration and be adjusted to operate and be confirmed with
a minimum amount of adjustment. There will also be extensive
material, in |
||
| 2005-03-29 | At some point we need a downloadable devkit that has the basic structure and executables that someone can use to create their own little ActiveODMA development area. We can also provide guidance about what that is and how to build it by hand, but it would be handy to be able to download one and have it work. [dh:2005-10-01 That seems nice. It should be something that can be obtained in the setup folder. Uh, no, in the /dev folder so that it can start there and be used to populate the rest of it. Interesting.] | ||
| 2005-03-28 |
Create an IncludePage setup for the versions of the dev
files that are being used, with the idea of including confirmations and
accounts for updates as they happen over time. There needs to be a
provenance notebook set for each dependency reflected in |
||
| 2005-03-28 |
Make a minimal structure in |
||
|
done 0.00 2008-04-24 |
2008-04-23 | d080402: Make into a Diary document-engineering folio modeled on the version for nfoWorks, and publish at ODMdiary.htm | |
|
done 0.00 2008-04-24 |
2008-04-23 | d080401: Make into Welcome document-engineering folio modeled on the version for nfoWorks, starting with the current default.htm page. | |
|
done 2008-02-15 |
2008-01-29 | d071002: Update the ODMA64 3.0 Interoperability | |
|
done 2008-02-15 |
2008-01-29 | d071003: Update the ODMA32 2.5 Integration | |
| done | 2008-02-15 | d071004: Change to be ODMA32 and have Core Stabilization be the version progression, not the title of the folio | |
|
done 2008-02-15 |
2008-01-29 | d071004: Update the ODMA Core progression as the folio and prepare to link to it from a post on Future ODMA | |
|
done 2008-02-01 |
2008-01-29 | d080102: Make folio on the ODMA Sweet Spot (with appropriate title). [dh:2008-02-01 It looks like it is about ODMA Effectiveness, the place where ODMA is the most effective.] | |
|
done 2008-02-01 |
2008-01-29 |
d080101: Create |
|
|
done 2007-08-14 |
2007-07-24 | Review the devNotes catalog for case-sensitive consistency among page names, URL links, link texts, and text mentions. | |
| done | 2007-07-25 | Add the ClustrMap to all of the latest devNotes so they will continue to appear on new pages: d070201c, d061201h, d061201i, d061101n, d061001g, d0610002d, d0610002e, d061003i | |
| done | 2007-07-15 | Add d070701 on the ODMJNI 1.0 Public Beta | |
| done | 2007-07-15 | Start a 2007/07 folder for folios about the public beta period. | |
| done | 2007-07-12 | Change d061201 so that the 0.60 beta page becomes 0.5x beta and there is a new 0.60beta page. | |
| done | 2007-04-27 | Change D000000-D000001 names here to lower-case and then change them on the site and in all mirrors plus VSS. | |
| done | 2007-04-26 | Restore the 2006/10/index.htm page to a standard index entry. | |
| done | 2007-04-26 | Restore the catalog d000001 from the 2006/10/index.htm page | |
| done | 2007-04-26 | Delete the unnecessary embargo subtree from the publicca image and from the A2 Hosting web itself | |
| done | 2007-04-26 | Delete the unnecessary embargo subtree from the VSS of the hosted-site image | |
| done | 2007-04-26 | When the embargo is moved, delete the embargo subtree from the development server. | |
| done | 2007-04-26 | Redirect the embargoed /10, /11, /12 to the 2006/10, etc. [What happens if I try to do this as a set after the one for 2007/02? Will that work or must I do them individually?][dh:2007-04-26 It worked as expected. Something to blog about.] | |
| done | 2007-04-26 | Correct the case-sensitive names to match original names | |
| done | 2007-04-26 | Share the embargoed /10, /11. /12 directories to 2006/10, etc. | |
|
done 2007-04-26 |
2007-03-25 | We need a graceful way to get the embargoed 2006 material out of embargo. It is probably by wholesale sharing of the embargoed 2006 material and transfer of it in its entirety. [dh:2007-04-26 And the embargo area can be safely redirected to the new location.] | |
| done | 2007-04-26 | Redirect tBlzT8bs/02 to 2007/02 to confirm that we can remove the embargo and then actually delete the embargoed directory. | |
| done | 2007-03-25 | Include 2007/02/d070201 in the Catalog so that its uplinks to the catalog work. Remove any cross-references from d070201 that are to material not yet removed from embargo. | |
| done | 2007-03-25 | From now on, put the construction and cataloging notes about the embargoed material here, as part of the initial steps to prepare for full lifting of the embargo on ODMJNI 1.0 development. | |
| done | 2007-03-25 | Move items that can now be disclosed to the devNotes construction log and the catalog. These are all around completed items and open items that will be completed in the un-embargoed material. | |
| done | 2007-03-25 | Take everything in <embargo>/02 out of embargo so that we don't have a problem around cross-linking across years (which doesn't work in an embargo situation). | |
| done | 2007-02-24 | Create placeholder for d070201, the ODMJNI 1.0 Reference. This is an important companion to the Guide and Usage Scenarios material. | |
| done | 2007-02-24 | Create devNotes/2007 folder in preparation for lifting the embargo and introduction of non-embargoed ODMdev material. | |
| done | 2007-02-24 | Create <embargo>/02 folder for 2007/02 material that will be released as part of the public-beta announcement. | |
|
done 2006-12-20 |
2006-11-27 | Get recent-change versions in the status of the catalog entries: d061001, d061003, d061101, d061201, | |
|
done 2006-12-05 |
2006-11-09 | There may be a separate ODMJNI 1.0 Deployment (and troubleshooting) folio(s). [dh:2006-11-27 This is still the way to go. Fill it in when I am closer to wrapping up 0.20alpha.] | |
| done | 2006-12-05 | Create d061201 on deployment and prepare to hold the 0.20 alpha deployment | |
| done | 2006-11-27 | Review all of these folios and make sure the names of files in FrontPage match those in VSS, and then that the links to the files also agree. This is a practice that is required to assure that the case sensitivity at http://Odma.info is reflected in the IIS and FrontPage extensions of the development version of the site. | |
| done | 2006-11-09 | Start embargoed folder 2006/11 and add 2006/11/d061101 on odmjni100 development. | |
|
done 2006-10-27 |
2006-10-26 | Start a new DevNote on the ODMA Connection Confirmation for ODMJNI. This probably does not need a deep path, since that only applies to the JNI-integration version, not the standalone tests. I'm not sure about that. [dh:2006-10-27 I start with OdmNative development. Also, it does sit in the same tree as ODMJNI so that the build setup is confirmed to be working where all further native code will be developed, tested, and then installed for use by the ODMJNI Java classes.] | |
| done | 2006-10-26 | Bring the Guide and Usage Scenarios over for management under a DevNote, because it is about how to use ODMJNI and constitutes technical documentation. | |
| done | 2006-10-26 | Create a D000000-format diary and job jar for use in the devNotes-embargo folder until the ODMJNI embargo is lifted. | |
|
done 2006-01-21 |
2006-01-20 | Factor materials from the front porch and construction/ construction zone to here as the more-appropriate job jar for now. | |
| done | 2006-01-18 | Create D000001 initial empty catalog page. | |
| done | 2006-01-18 | Create this D000000 for immediate use in making a job jar and diary for devNotes. |
|
|
created 2006-01-18-19:42 -0800 (pst) by
orcmid
|
