nfoTools
Construction Zone
Diary & Job Jar
|
|
nfoTools
Construction Zone |
Status |
Date |
Description |
|
|
superseded 2023-11-26 |
2007-08-04 |
|
|
| 2023-12-16 | There are many utilities to allow inspection of file formats and report on their integrity, other issues. This has come up on raylib with regard to audio issues. This is clearly a combination of nfoTools topics and there should be some sort of omnibus folio about these and where more is found. There is also overlap with docEng and docInterop. This needs to be explored more. | ||
| 2023-12-13 | I need a Contributions section in repositories. I also need some common locations to refer individual projects to. The contributions to documentations are a challenge. | ||
| 2023-12-13 | With FrontPage content authored directly into a GitHub Pages repository, that material is unfriendly for pull requests :). I don't think I care so much. Hybrid pages work better but there is still the HTML-in-Markdown that someone needs to know how to fix. I have to address that in docEng and figure out how one can work with that not only in the open, but welcoming contributions. | ||
| 2023-12-13 | There are ways that folks with no or limited hearing are able to experience rhythms. I way to do that from/with a computer would be interesting. I wonder if my little AARP speaker would work for that, providing enough sensations/vibrations to touch. | ||
| 2023-12-13 | There needs to be something about AAC (Augmenative and Alternative Communications) among all of this. Dealing with vision and hearing, and mechanicals should be part of all of it. <https://www.asha.org/public/speech/disorders/AAc/> does not address vision and mechanical limitations it seems. Still, it is useful to know about and also have devKits for all of them. This can't be done solo or in a vacuum. I need assistance from those the assistive will support. Microsoft has much of that online. We have to see how that gets incorporated. | ||
| in progress | 2023-12-12 | Add construction structure and a construction zone to audio/ quickly for gathering notes on the Cakewalk formats, RIFF, etc., and also coverage in other sections. I need to figure out where and how to document the package formats of the Cakewalk "family" if necessary, and make some connections with dev/ and tools/ for such things. I am unsure how to capture my beta experience in some sort of educational/instructive/informative manner. Use dev/ as boilerplate. | |
| in progress | 2023-11-28 | After cleaning up construction.htm, propagate index.htm and construction.htm into all of the subfolders as boilerplate for adjustment as needed: construction, dev, games, notes, skills, tools, audio. [dh:2023-12-12: I wouldn't need construction zones everywhere, but it is easy to do. I could also have more subject-specific Diary & Job Jar items as has been the technique in the past. With hybrid techniques, I am uncertain at the moment.][dh:2023-12-13 I think "Diary & Job Jar" explains why I do want to keep these at the underpinnings level.[dh:2023-12-25 I don't need to go lower than the top tier though, because I then have the standard folio business and a tier-level content and Diary & Job Jar, e.g., a000000 and a000001 for audio. | |
| 2023-11-28 | There are numerous items to repurpose or remove in this accumulation of items. The priority is to have the construction structure completed for the nfoTools/docs/ that are already published here, and then work through other material to be preserved here from nfoWare and nfoWorks by refactoring as the material is added. An example of the hybrid structure we'll use in the future is the hybrid treatment of C/C++ in tools/ and VCrayApp in dev/, all to be the first complete hybrid cases. | ||
| 2023-11-27 | Make hybrid pages throughout the first level of subordinate folders: construction, audio dev, games, notes, skills, tools. | ||
| 2023-10-30 | remove folders that have no current purpose. They might be restored/salvaged in the future: bits, data, gaming (to games), trust. Existing dev, notes, skills, and tools may have merged material. Review and adjust those. | ||
|
in progress 2023-11-26 |
2023-10-30 | Repurpose Construction Materials and introduce a new Repurpose/Repave/Preserve activity. [dh:2023-11-28 I overlayed the original rather than adding a layer. Now they can be worked through.] | |
| in progress | 2023-10-26 | construction structure is repaved first | |
| in progress | 2023-10-26 | Scavenge to GitHub orcmid/nfoTools/docs for repurposing/preservation as orcmid.github.io/nfoTools. | |
| 2016-11-11 | Ensure the use of #vn.n.n version anchors on all pages now. | ||
| 2016-11-10 | Switch to Apache License version 2.0. There is no need to screw around with Creative Commons when the ALv2 is much easier and we can worry about rounding some of its sharp corners some other time. | ||
| 2016-11-02 | Add games/ construction structure for introduction of interactive games, including the cavern set. Start with the Toolcraft as boilerplate. | ||
| 2013-11-04 | trust/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | toolcraft/ Complete repaving of the construction structure and manage content development and repaving there, consult Toolcraft for boilerplate | ||
| 2013-11-04 | text/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | projects/ Complete repaving of the construction structure and manage content development and repaving there, consult Toolcraft for boilerplate | ||
| 2013-11-04 | meaning/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | images/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | glossary/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | dev/ Complete repaving of the construction structure and manage content development and any repaving there, consult Toolcraft for boilerplate | ||
| 2013-11-04 | data/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | construction/ Complete repaving of the construction structure and manage content repaving there, consult Toolcraft for boilerplate | ||
| 2013-11-04 | bits/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| 2013-11-04 | _private/ Complete repaving of the construction structure, consult Toolcraft for boilerplate | ||
| in progress | 2013-11-04 | notes/ Complete repaving of the construction structure and manage content repaving there, consult Toolcraft for boilerplate [dh:2023-11-27 This is now use of the Construction Structure patterns for orcmid.github.io and also orcmid.github.io/miser.] | |
| 2013-11-03 | Manage across the top level to the point where the site should be updated. Bring the structure up to speed with regard to more-recent efforts such as nfoWorks and he Miser Project. | ||
| 2012-12-31 | Included correction of URLs, fragment IDs, and titles in the repaving progress. Propagate through the front porch and bits, construction, data, dev, glossar, images, meaning, notes, projects, text, toolcraft, trust, and xml. | ||
| 2012-12-31 | Determine if a better LiveSearchSiteAuth.xml file is needed for Bing searching and site administration with regard to search. | ||
| 2012-12-31 | Review all folders for their continued function as part of nfoWare. | ||
| 2007-08-11 | General rambles in the notes below should be moved to the nfoNotes Diary & Job Jar without waiting for it to be repaved. | ||
| 2007-08-11 | When Toolcraft is ready, make the new nfoWare cover with room for announcement, etc., on the model of NuovoDoc. | ||
| in progress | 2007-08-04 | Initiate review the subordinate construction structures and construction zones for case-sensitivity among page names, URL links, link texts, and text mentions: _private, bits, construction, data, dev, glossary, images, meaning, notes, projects, text, toolcraft, trust, xml [dh:2023-11-27 This applied in the location of nfoWare. This will need to be updated for nfoTools on GitHub.] | |
| in progress | 2007-08-04 | While performing reviews, identify any additional adjustments that are required to have consistency with the latest formats, styles, and organization of materials. | |
| 2007-08-04 | Document the construction structure principles under the appropriate template documents so that this is not always being implemented and deviated from memory. [dh:2023-11-27 This requires something in docEng as a place to centralize this and the emerging case of mixing with Markdown pages. | ||
| 2007-08-04 | Also make sure there are no-follows in the bottom of everything in the templates. | ||
| 2004-01-12 |
Add an index.htm for the |
||
| 2004-01-12 | Add an eMail section. This is for confirmable experiences around e-mail and also what is accomplished with it. One thing to explore is whether eMessage is any different, or a precursor, or what. [dh:2007-08-08 I wonder if it should be simply "messaging" with e-mail as a special case, working our way up to other kinds of messaging including peer-to-peer and instant messaging, with protocols like XMPP, RSS, and Atom Publishing. dh:2012-12-31 Yes, messaging and also not about confirmable experience so much as the nfoWare how-to and supporting tools.] | ||
| 2004-01-12 | I don't have a good idea of how notes will somehow lead to there being content pages in different sections here, such as bits, data, bytes, pixels, text, meaning, etc. [dh:2007-08-09 We now know that this will be done with the FrontPage Extensions Include Page functionality. This works at maintenance time and is completely maintainable. We require nothing special of the hosted-site server. dh:2012-12-31 The abandonware stat us of Microsoft FrontPage and its inability to work properly from Windows 7 and later clients is going to impact this.] | ||
| 2004-01-12 | I want to use eMail as an example of confirmable experience. Bill and I are having lots of experiences around e-mail security, around signing e-mail, and even simple things like getting e-mail content from one place to another. I am thinking about how simple it is and how difficult it is to work out. This also shows up in the context of text. So I need to figure out how many sections to create here for starters, and what to do about making them confirmable experiences. I think I will have to do something about this. [dh:2012-12-31 This probably goes under TROSTing.] | ||
| 2004-01-10 | Hmm, where would I deal with anti-virus software and protections like that? If not here, where? Certainly trust points with regard to monkeying with files and file systems and running processes (getting launched into memory in various ways - boot sector, programs, startup process, etc.) [dh:2012-12-31 This is certainly related to trustworthiness and security provision. There might be some advice about that under toolcraft and setting up development machines. Forensic work and exploit investigation is off topic, even though some TROST or nfoWorks code may be useful in such endeavors. Not nfoWare though. Keep this item until it is reflected elsewhere.] | ||
| 2004-01-08 | Bill Anderson said that reviewing the site as it is today brought up things he wants to say there. We talked about creating places to collaborate using the site. A wiki, though in the cards, is too hard to bring up on a commercially-hosted server and I want to do something simpler. One thing I can do is create a subdirectory that has a special user ID for FTP. Band and Bill Kent (if he chooses to play) could have accounts that provided access to the shared FTP space. This is actually one of the easiest things to do. The other step is to create a blog that is mapped to the site from blogger. This allows us to make notes and to have archives of them, but it doesn't do a lot about creating organized content. So the challenge here is to come up with something simple for early collaborative activities. E-mail works now, and we haven't tried much else. We can do e-mail for now, actually. | ||
| 2004-01-08 | I just got off the phone with Bill Anderson. He suggested "laboratory" for a kind of section. We're scientists, we need laboratories. I think that goes in some places, maybe on nfoWare too. Certainly in the glossary project, and I have added that in the mention from nfoWare.htm. | ||
| 2004-01-08 | I need to preserve my writings in a place where the links to them on nfoCentrale sites or publications are at least archived so that I can recover them if ever needed. That also applies to material that I glean from the Internet and rely on. I can give credit to the original source, but I also need some way to be able to produce the cited material if it every becomes important to do that. At the same time, I must not redistribute such material. Something to work out on Orcmid's Lair as well as here, I think. [dh:2012-12-31 The practice on nfoWorks is to use cache folders within folios and to use embargoed folders with unpublished names for archiving source materials that are not redistributable.][dh:2023-10-30 This will not work with preservation on GitHub, so there will need to be a different solution, perhaps involving encryption? Or maybe off-site, as on OneDrive with its restricted access.]] | ||
| 2004-01-08 | I will be referring to Readings and Bibliographies in Orcmid's Lair and elsewhere. I need to have those pages retrofit to the current nfoCentrale construction styles and practices as being exhibited and updated here. [dh:2023-10-30 The orcmid.github.io/bib/ is now that place. | ||
| 2004-01-08 | I have a simple basis for Notes here. Retrofit this to the Notes on Miser-theory where this came from. | ||
| 2004-01-07 | I am writing this here because it is the page I am looking at. I guess I could have used my notebook, but here I am. There are topics such as Web and CD-ROM that fit into the electronic publishing that dmWare is. More to list somewhere. | ||
| 2004-01-07 | Will we take on OHS here? How do we keep this straight separate from Situating XML and also getting into higher levels, such as Situating Documents (which I am willing to do as part of Situating Data just to be ornery). This can fit into the spiral plan (oh, wow) and it does raise some questions about complete cuts of the dmWare CD as a companion to print versions and as an orderable unit from the web site. | ||
| 2004-01-07 | Use the Manning eBook I have to walk myself through the familiarization with .NET and the basic concepts | ||
| 2004-01-07 | Install .NET SDK on Compagno in preparation for being able to develop .NET elements for nfoWare. [dh:2012-12-31 I am not certain that I want to do this. There are interoperability and platform-portability considerations, but I am not at all clear when those arise and how they will be dealt with. There is also JavaScript to consider now, and the JavaScript use of native libraries too. In any case, Compagno is the wrong place.] | ||
| 2004-01-02 | Since I will be doing open source, how about creating a license that I can name and create a SourceForge project for nfoWare. [dh:2012-12-31 There will be Apache ALv2 and the development of tools will probably be under nfoWorks.][dh:2016-11-02/-28 ALv2 is the license of choice and GitHub is now the preferred location for projects, unless I choose to use Git. It appears that I can have multiple Git repositories published under orcmid.github.io. That is useful.] | ||
| 2004-01-02 | I supposed cryptography might be appropriate, but code signing certainly is. Look at whether there needs to be nfoWare as a signature and therefore as a mail alias. Expand on this. | ||
| 2004-01-02 | Create a project around the registration/assertion of naming and the signing of things. This influences the structure of download materials and also the directories here, for locating javadocs, for locating RSS feeds, for locating other things via identifiers that are issued and used. | ||
| 2004-01-02 | Create projects and tracking for a FAQ, support, and downloads section. | ||
| 2004-01-02 | Consider whether there should be a wiki here and who should play in it? Reflect in project or notes activity. This is certainly an useful place to have discussions on what is data, etc. | ||
| done | 2023-11-28 | construction.htm: Revise from nfoWare to nfoTools | |
|
not applicable 2023-11-28 |
2016-11-02 | nfoware.htm: Add gaming/ to the list | |
|
obsoleted 2023-11-28 |
2016-11-11 | Construction Structure: Get the title block nfoWorks image working on the construction-level pages. The problem is FrontPage and the IIS server has "nfowarebits-* and VSS has "nfoWareBits-*". [dh:20232-11-26 I don't think this matters any more because of the refactoring and repurposing that is going on for orcmid.github.io/nfotools. I don't know that nfoWorks will survive all of this. Some of it should, but perhaps more in docEng and docInterop, which can end up on orcmid.github.io as well, of course.].[dh:2023-11-28 The templates and include pages are adjusted. This work item no longer applies.] | |
| done | 2023-11-27 | index.md Change to mixed format in the same manner as orcmid.github.io/miser entry page. | |
|
done 2016-11-02 |
2012-12-31 | The current domain is nfoware.com directed to /home/orcmid/public_html/nfoware. nfoware.org and nfoware.net are leased but not hosted. Determine how I want to deal with that. Check limitations on my particular account. Also, transfer to the latest terms if possible. [Updated 2016-11-02 The nfoware.org and nfoware.net domains are going to be released at renewal time in 2017. That makes this question irrelevant.] | |
|
done 2013-11-04 |
2004-01-02 | Create something that will work for the nfoWare logo and image. Make at least a generic one. Choose the color scheme to be used on standard pages. [I have used a Hard-Hat Stage idea, and not done anything unusual about standard pages yet dh:2004-01-05][dh:2007-08-05 Make a default page that works more like the NuovoDoc front page and the ODMdev pages][dh:2013-11-04-13:01 The logo was created and used some time ago. It just never made it into the template for Construction Structure pages. That was repaired today.] | |
| done | 2013-11-04 | There is an nfoWare logo. I need to use it in the construction zones and construction materials also. It is nfoWorks that doesn't have a logo yet, although I am attached to something with gears, and maybe bits or coming out, or like from a forge. Maybe with a background document symbol? | |
|
done 2013-11-03 |
2012-12-31 | Review the front porch items: c000000.htm, construction.htm, default.htm, index.htm, LiveSearchSiteAuth.xml, and nfoWare.htm | |
|
not done 2012-12-31 |
2004-01-08 | Vicki's machine had something weird happen to it that is symptomatic of a virus/worm assault. I am running an emergency Norton Antivirus scan from a CD-ROM, and the machine is off the net. This is an opportunity for documenting a lot about installing XP Pro, once I figure out how to rescue the data her damaged Windows 98 system has on it. Not exactly what I meant to be doing here, and it may keep me away for a while. [dh:2012-12-31 Obsolete item. I don't know what happened then, but the reliance on Windows XP is limited only for site-development work now.] | |
|
not done 2012-12-31 |
2004-01-08 | In the index.htm construction history block, decide how I want cloaking to work in all of the links there. I think there is something to do about some of them. Also, should these make sense whether I am cloaked or uncloaked when the page is viewed? Does this over-constrain the page, and how do I rationalize it? (There is uncloaked access to construction from standard pages such as nfoWare.htm, so take that into consideration on the use of a, an, etc.) [dh:2012-12-31 This is obsoleted by the elimination of cloaking and the use of the latest Construction Structure model as part of the repaving.] | |
|
not done 2012-12-31 |
2004-01-08 | On index.htm make the nfoWare.com link in the text paragraph to an nfoWare.com site, and do the dual-flavored links - anchored at "an" and domain for the domain mention. Make the last-paragraph "default" reference use the same page, so that cloaking is not dropped automatically. [dh:2012-12-31 There is no need for cloaking. Also, the repaving to the current Construction Structure model takes care of this.] | |
|
not done 2012-12-31 |
2004-01-07 | Move open-source and other-source directories and collections to Compagno. [dh:2012-12-31 This movement is to the Windows Home Server and does not require resources on Compagno beyond the use of VSS for projects. That will be eliminated along with the retirement of Compagno.] | |
|
not done 2012-12-31 |
2004-01-06 | Add cloaked up-links out of title blocks of standard pages. [dh:2012-12-31 This is not necessary. There might be some no-follows, but the linking by appropriate domain names works and relative up links are not allowed in the current hosting-site structure.] | |
|
not done 2012-12-31 |
2004-01-05 | When nfoWare.com cloaking is operating, work on replacing the Hard Hat Stage image and include pages with something representative of Data. [dh:2012-12-31 Cloaking is no longer used. The A2hosting site provides add-on domains that work as I've always wanted. That is taking care of this problem.] | |
|
done 2008-03-01 |
2004-01-08 | See if it is worthwhile to rent nfoWare.org, nfoWare.net, and nfoWare.info too. I think not but it wouldn't hurt. [dh:2012-12-31 The rental of domain names through A2hosting is economical enough to make this affordable and it ensures the reservation of the domains for variant usages.] | |
|
done 2007-08-31 |
2004-01-10 | There are already notes on toolcraft-related topics in the nfoWare notes diary. The toolcraft provides a section for talking about that, relating what is important and how to get it to work with nfoWare, etc. | |
|
done 2007-08-09 |
2007-08-04 | Have the construction structure be consistent all the way down in how construction zones are linked and how construction-structure images links upward to the appropriate construction zone, or other superior structure. [dh:2007-08-11 This has been figured out and is being carried out as we repave. The toolcraft structure is complete as is the Front Porch. All others will be tied into the front porch in exactly the same way as toolcraft, and their completions will be marked in the same way.] | |
| done | 2007-08-09 | Revamp the index.htm using a table in the same manner as the Construction Zone tabulation. Review that one too, based on the insights recorded on #58.118-119. | |
|
done 2007-08-09 |
2007-08-08 | nfoWare.htm should not be a duplicate of the construction structure. It should appeal to the Construction Zone for that. Fix that after creating a note that generates the nfoWare.htm page. nfoWare.htm should be about what nfoWare is and what will be available here, over time. [dh:2008-08-09 That actually works, already, especially since the Construction Structure is being simplifed to connect at the index.htm and construction zone levels.] | |
|
done 2007-08-09 |
2006-01-17 | Factor the front porch treatment of ODMdev back to nfoWare. [dh:2007-08-09 We have refined things so we now need to factor the other way.] | |
| done | 2007-08-08 | construction.htm: Provide a repaired explanation of the links out of pages other than index.htm pages. | |
| done | 2007-08-08 | construction.htm: Verify that the anchor site construction zone can be found using this up-link. [dh:2007-08-08 no, it doesn't work and it can't because the browser has no idea what URL to compose and it is no longer going to give dots to the destination site. This leads to a change in the overall approach to linking. (See #58.118). | |
|
done 2007-08-08 |
2007-08-05 |
When the front porch is repaved, be sure to use the
correct name for the Construction |
|
|
done 2007-08-08 |
2007-08-04 | Review the front porch for case-sensitive consistency among page names, URL links, link texts, and text mentions. | |
|
done 2007-08-08 |
2007-08-07 | Reflect change to "Construction Material" in index.htm and nfoWare.htm | |
| done | 2007-08-08 | index.htm Make a quick pass that has this page be all about nfoWare, but with more work needed to provide a full-up construction structure. | |
| done | 2007-08-08 | Correct the naming of the default on the index.htm page | |
| done | 2007-08-08 | Update the default.htm copyright notice to extend to 2007 | |
| done | 2007-08-08 | Update hosted-site image and remove default.asp from the site along with adding default.htm for the Front Porch. | |
| done | 2007-08-08 | Correct title to use "c000000" rather than "C" | |
| done | 2007-08-07 | Replace default.asp by default.htm | |
| done | 2007-08-07 | Have all .txt files served up as UTF-8. This provides consistency for code files as well as HTML files. See how I did that on ODMdev. See the .htaccess file for devNotes. | |
| done | 2007-08-05 | Move items that are on general and global matters to here from the Construction Material Construction Zone job jar. | |
| done | 2007-08-04 | Add repaving project here for the Front Porch repaving and the Construction Structure repaving | |
| done | 2006-08-31 | Add construction zone for the InfoNuovo front porch, and begin managing the upgrade of the front porch to have managed construction structure. [dh:2007-08-04 This page was being shared with the nfoWare page, which accounts for the weirdness.] |
|
|
created 2006-08-31-12:57 -0700 (pdt) by orcmid |
