-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnfoTools.txt
169 lines (125 loc) · 7.4 KB
/
nfoTools.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
nfoTools.txt 0.0.12 UTF-8 2023-02-12
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
nfoWare/nfoWorks nfoTools
=========================
<https://github.com/orcmid/nfoTools>
<https://github.com/orcmid/nfoTools/blob/master/nfoTools.txt>
USEFUL TOOLS IN DEVELOPMENT OF NFOWARE/NFOWORKS PROJECTS
NFOTOOLS: SOURCE CODE VERSION CONTROL REPOSITORY
------------------------------------------------
nfoTools is a collection of utilities and software components. The
tools are designed for use in composition of larger software projects
for information-processing applications (and games of course). nfoTools
can apply anywhere in the complete learning-and-improvement lifecycle of
software projects.
nfoTools includes a Toolcraft on-ramp that supports beginners who want
to understand more about programming and the tacit understanding of
experienced software developers. Crawl first, then walk, then run.
Progressive discloser is used in a way that allows more-experienced
visitors to quickly skip over details they already know. Review of the
basics may be useful though.
Emphasis is on development of software for Microsoft Windows and using
Microsoft Windows desktop tools as instruments of such efforts. Only
freely-available tools are required in addition to a Windows PC or laptop.
The working language is English. This is how the author is equipped.
While nfoTools are useful independently, they are chosen and developed
first in service of specific software efforts originally housed on
nfoWare.com, nfoWorks.org, and more-recent efforts now on GitHub.
MANIFEST
nfoTools.txt
this manifest and job-jar file
README.md
Introduction to the orcmid/nfoTools repository.
devKits/
providing components and kits that are useful in the construction
stage of computer programs for utility and application purposes.
docKits/
providing components and kits, including tutorials and other aids,
that are useful in the documentation for GitHub-housed software-
development projects conducted in the open
docs/
source of GitHub Pages documentation for nfoTools and accessible at
<https://orcmid.github.io/nfoTools/>
LICENSE.txt
The open-source software license that applies to the entire
nfoTools collection except where stated otherwise.
NOTICE.txt
Notice that applies with respect to particular components of
the nfoTools collection and their external origins.
.gitattributes
A declaration of file attributes for use in Git repositories of
the nfoTools source code.
.gitignore
A declaration of artifacts to be ignored and excluded from Git
repositories, applying to working files that are not part of the
managed archive materials
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
Copyright 2016-2021, 2023 Dennis E. Hamilton
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
ATTRIBUTION
Hamilton, Dennis E. nfoTools: Source Code Version Control Repository.
nfoTools project text file nfoTools.txt version 0.0.11 dated 2021-09-02,
available on the Internet as a version of
<https://github.com/orcmid/nfoTools/blob/master/nfoTools.txt>
TODO
* Cover toolcraft and the intention of relying exclusively on freely-
available software tools and libraries. Provide in docs/tools/
* Explain the licensing approach and handling of open-source code and any
contributions to it.
* Address beginner mind. Cover in docs or wiki here. I need a way to
rely on this from other projects that beginners and hobbyists may take
interest in. This is a skill, along with arranging comfirmable
experiences.
* Address process and social matters too: GitHub and Discord, for example.
* Also address or recognize learning approaches and available guildance
as well: Udemy, Coursera, etc.
* Mutate to precise construction structure compatible with usage of docs/.
* Add on-ramp rerequisites and summaries/tutorials on file explorer, adding
git and GitHub support, downloading and installing software, zip usage,
editing with Visual Studio Code, installing Visual Studio build tools,
console operation (cmd.exe), and creating C/C++ software projects.
* Consider a folio structure similar to that of nfoWare & nfoWorks. Explain
what those are/were.
* The raysan5/raylib-game-template is inspiration for use on rayLab and
also nfoTools. I need to find out if multiple templates are possible and
having that work with a variety of rayLab and nfoTools cases.
* I am conflicted on the folio structures which I am perpetuating in docs/
and without corresponding code-side folders. I think that I could use
accession naming, but I am leary of it, even though it has served me so
well.
* It looks like showdefs is a devkits project if not a dev/ one. It also
looks like some games should be moved to games. I'm unclear on the
AddBib utility. It's maybe not docEng, and I don't know where that goes
exactly. It is like a Unix utility, though I don't necessarily want that
as a category. Meanwhile, I want to see if I can recover the older
history of showdefs.
* Thanks to Dare Obasanjo I am made aware of the Inclusive Design initiative
at Microsoft. <https://www.microsoft.com/design/inclusive/>. This will
be an important topic. I think it comes under skills as well as tools.
* In the synopsis for nfoTools, I need to emphasize the documentation also.
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
0.0.12 2023-02-12T16:28Z Note on Inclusive Design, other thoughts, cleanups
0.0.11 2021-10-17T20:37Z Handwringing about ShowDefs and such
0.0.10 2021-09-02T19:31Z Manage TODOs
0.0.9 2021-08-30T18:48Z Add explicit rulers (tacit understanding, duhh)
0.0.8 2021-08-30T17:42Z Manage TODOs, looking into template possibility too
0.0.7 2021-08-20T17:30Z Improved text, attribution, and TODOs
0.0.6 2021-08-18T21:03Z Manage TODOs, emphasizing newbie on-ramps
0.0.5 2021-08-18T20:48Z Add README.md and manage TODOs, touch-up text.
0.0.4 2021-02-06T17:53Z Add docKits/ manifest entry, manage TODOs.
0.0.3 2021-01-31T23:18Z Add docs/ manifest entry, manage TODOs
0.0.2 2016-12-02-17:39 Complete Staging for the first devKits components.
0.0.1 2016-11-30-13:45 Initial setup with devKits/ as the first area for
introduction of reusable components.
0.0.0 2016-11-30-09:11 Transposition of Adv10.txt 0.0.4 from the Adv10
project for use as boilerplate.
***** end of nfoTools.txt *****