-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathAdv10.txt
217 lines (162 loc) · 9.41 KB
/
Adv10.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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
Adv10.txt 0.2.0 UTF-8 2024-10-12
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
ADVENTURE VERSION 1.0
=====================
<https://github.com/orcmid/Adv10/blob/master/Adv10.txt>
THE ORIGINAL COLOSSAL CAVE TEXT ADVENTURE
DEVELOPMENT AND SOURCE CODE VERSION CONTROL
-------------------------------------------
This project is for development of a Clean C version of the
original Colossal Cave Adventure as a portable command-line
implementation. Adv10 is the foundation of the Cavern project
for progressive development of enriched versions, from command-
line to 3D animated versions.
Stable distributions of Adv10 executables are made available at
<https://orcmid.github.io/Adv10/dev> when transposition to Clean C
is completed. There will also be release branches in the source
code repository at <https://github.com/orcmid/Adv10>.
To build and run Adv10 from this source code in its current state,
you will need to use a desktop PC with Microsoft Windows and Visual
Studio Build Tools.
For more details about what you need to install to have Adv10
build successfully, consult https://orcmid.github.io/Adv10
MANIFEST
Adv10.txt
this top-level manifest and job-jar file
.gitattributes
A declaration of file attributes for use in Git repositories of
the Adv10 work
.gitignore
A declaration of artifacts to be ignored and excluded from Git
repositories. This applies to working files that are produced
when using this code locally and excluded from the public source
code.
LICENSE.txt 11,527 byte 2016-10-31 copy
Apache License Version 2.0 of January 2004
NOTICE.txt 1.00 1,251 byte 2016-12-10 Adv10 version
Notices applicable to licensing of Adv10
README.md
README file presented at <https://github.com/orcmid/Adv10>.
SECURITY.md
Security Policy statement presented on the Security tab on the
<https://github.com/orcmid/Adv10> page.
Advent/
Materials from the original game and how the Clean C source version
is extracted in a coordinated manner.
dev/
construction sets for building and testing Adv10 developer builds
docs/
folder for the authored form of GitHub Pages published at
<https://orcmid.github.io/Adv10>
Transpose/
The spiral transposition of advent.w to Adv10 Clean C sources and text
WinDev/
development of ADV10 for Windows
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
Copyright 2014, 2021-2022, 2024 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----|--*
TODO
* Re-organize along a nfoTools-consistent project structure, including
adjusting text rulers and manifest/TODO files. This will move source
into dev.
* Figure out how to get back to keeping the extractions from the *.w
form to the *.c and *.h forms so that the derivations can be matched.
* Add attribution.
* In the source-code notices, and here, add statement about English being
preserved as the authoritative content, with supplemental translations,
rather than replacement translations. This is because development is in
English and trouble-shooting is generally by English-fluent contributors.
See below.
* In the use of Adv10 at some level of release, when there is support for
additional languages, it will always be possible to have dual-language
presentation to aid in trouble-shooting and verification of operation.
* Devise a scheme where the player's map location and the identification
of the displayed text is provided in a consistent form in every output,
although barely noticeable and not generally useful in the player's own
mapmaking. It is relevant in captured output and will be usable by
game-exercising test fixtures. Users will probably figure it out.
* When there is audio, the background of each room should be distinctive,
and there can be thematic nuances as well.
* Seek out and/or develop a console library that provides something perhaps
like ncurses and at least ANSI mode operation, but more abstracted. This
is just for output formatting and not so elevated as a CUA level (at
least for 1.0.0, though a CUA version is ddesirable at some point too).
* There needs to be a better roadmap with regard to progressions thrugh to
CUA and all the supports for internationalization and accessibility.
Being able to save and restore games is also important, as will be the
ability to trace and script. The prospect of animation is considered
later. So long as it is the same game, we will have 1.x.y versions. There
might need to be reconsideration of that, and the adv10 name.
* Add the injunction that one should play the adventure and then take a
look at the code, also with a hat tip to advent.w, etc.
* Add deployment-oriented organization that will be used in releasing beta
and later versions of the Adv10 transposition.
* Keep the README at a consistent high level, with details in supporting
pages.
* Report the opening, and the various notifications, to Don Knuth and Don
Woods for their review and confirmation that their reservations are
satisfied.
* Set up command-line options for the adv10 executable too. At least the
unknown parameters, which is what "-?" will also always produce.
* Tuck the permission mails and other hard copy materials into an off-line
file folder.
* Create a sequestered web-site folder for preserving copies of the source
materials that I am basing this project on.
* Deal with dependencies and the intermediate use of libraries under Adv10.
* Cover toolcraft and the intention of relying exclusively on freely-
available software tools and libraries.
* At some point, using fixed lines will not work. We will need to change
to some form of automatic reflow. It would be interesting if that would
just take the current layout as hinting.
* Working out reflow ultimately ties into localization and use of non-Roman
texts. Since there may be significant platform/library support for that,
this will be an exercise related to the nfoWare Text topic and also the
handling of platform and library dependencies that need to be somehow
put under build control in a way that preserves the common source and the
"reference" implementation. There is much fodder here for some useful
SE4E demonstration/consideration.
* Now that it is appealed to here, get cracking on dev/WinCon/Adv10Run.bat
and get a dev/WinCon that lets folks get builds and runs to happen from
now on as part of continuous iteration.
* For audio, look into environmental sounds. For thoughts, see
<https://www.ableton.com/en/blog/sugai-ken-the-shibui-of-field-recording-and-electronics/>
* Replace nfoWare references to ones about GitHub orcmid/Adv10
*---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--*
0.2.0 2024-10-12T18:29Z Touch-up and reflect change from src/ to Transpose/
0.1.0 2024-10-11T19:55Z Updated manifest and reorganized TODOs
0.0.10 2024-10-10T20:18Z Prepare for re-organization activities,
bringing to current manifest/TODO format
0.0.9 2022-07-14T16:49Z Touch Ups, Manage TODOs
0.0.8 2021-05-22T18:18Z Manage TODOs, reflect updating of the README.md
0.0.7 2016-12-14-16:22 TODO placeholders for future structuring of the game
architecture to include automated game-testing and multiple developer/
user languages.
0.0.6 2016-12-10-09:07 Clean up Manifest and the NOTICE file to be more
specific. Version the NOTICE.txt. Review TODOs. Provid an Intro
on how to dig in here by getting Adv10 to build and run.
0.0.5 2016-10-15-12:49 Add dev/ folder for the developer build setup
0.0.4 2016-10-06-14:01 Add Manifest and license notification
Clean up TODOs for items already handled.
0.0.3 2016-10-04-11:14 Revive on GitHub as orcmid/Adv10
Switching to semantic versioning along with revival of this project
on GitHub. Touch up to reflect the new location.
0.02 2014-02-28-12:41 Further TODO Items
I have received provisional approval from Don Knuth and Don Woods and
will be proceding on that basis when producing the null implementation
and more.
0.01 2014-02-08-11:34 Add TODO Items
Reflect the VS Online tasks for this project and also the desired
deployment-oriented organization
0.00 2014-02-07-20:07 Initial placeholder
The page is enough to confirm that check-ins and pushing to the
VS Online project repository is operational.
***** end of Adv10.txt *****