Free Hero Mesh

Check-in [80ab5a543a]
Login
This is a mirror of the main repository for Free Hero Mesh. New tickets and changes will not be accepted at this mirror.
Overview
Comment:Add a paragraph in PORTING file, about alternative implementations that do not use SQLite and X resource manager.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 80ab5a543a94d90cc22191b4623c398cf45c05d5
User & Date: user on 2022-07-09 22:20:37
Other Links: manifest | tags
Context
2022-07-10
00:55
Implementation of order of execution overriding is probably corrected now. check-in: 2b0b74d47a user: user tags: trunk
2022-07-09
22:20
Add a paragraph in PORTING file, about alternative implementations that do not use SQLite and X resource manager. check-in: 80ab5a543a user: user tags: trunk
2022-07-07
00:08
Add the documentation about coordinate input binding into the bindings.doc file. check-in: ef46fdbc36 user: user tags: trunk
Changes

Modified PORTING from [35ecae0c52] to [1829f5c3c9].

154
155
156
157
158
159
160





161
162
163
164
165
166
167
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172







+
+
+
+
+







interface; if it does, then the below notes may be helpful.

The exec.c and class.c files are the most important files, and can probably
be used with minor changes even if porting to different systems and/or user
interfaces. The other files could be omitted, but then those parts must be
rewritten (possibly in a different programming language); some parts of the
existing files could be copied if needed.

Free Hero Mesh uses SQLite and X resource manager. However, it would be
possible and valid to make a implementation of Free Hero Mesh which does
not use these things, although some parts of the code might need to be
changed or else writing compatibility functions.


=== Character encoding ===

Free Hero Mesh does not and will not use Unicode. As of this writing, it
only supports single-byte character codes, although in future it is
intended that multi-byte codes (e.g. EUC-JP) might also be implemented.