[Tinymux] Disabling the Logon WHO

[Stephen Dennis]

The changes to the helpfiles project have been made and posted to TinyMUX
2.3 and TinyMUX 2.4.

Speaking of CVS, TinyMUX sources are accessible via CVS as follows:

cvs -d :pserver:anon at cvs.muxsh.net:2401/annex/cvsroot<http://pserver:anon@cvs.muxsh.net:2401/annex/cvsroot>login
Password: <blank, so just hit return>
cvs -d :pserver:anon at cvs.muxsh.net:2401/annex/cvsroot<http://pserver:anon@cvs.muxsh.net:2401/annex/cvsroot>checkout
TinyMUX23
cvs -d :pserver:anon at cvs.muxsh.net:2401/annex/cvsroot<http://pserver:anon@cvs.muxsh.net:2401/annex/cvsroot>checkout
TinyMUX24
cvs -d :pserver:anon at cvs.muxsh.net:2401/annex/cvsroot<http://pserver:anon@cvs.muxsh.net:2401/annex/cvsroot>checkout
helpfiles

I think people will generally grok the layout of the TinyMUX23 and TinyMUX24
except that there is an extra 'mux' sub-directory at the very top of tree.
./dounix.sh, ./dowin32.sh, unix/, and win32/ are used to build the
patchfiles and tarballs. Everything needed to build the top-level
distribution is there with four caveats. 1) The ./dounix.sh script uses
makepatch, 2) the ./dowin32.sh script is written to be run under cygwin on
Windows. One would need to compile a new netmux.exe and then copy it
manually into mux/game/bin/; 3) the ./dowin32.sh script requires genpatch to
generate the .utp files, and 4) ./dowin32.sh uses JAR32 from ARJsoftware and
PKZIP 2.50.

If I were ever hit by a truck (not that I'm planning to be hit by a truck),
it would be relatively easy to change ./dounix.sh to use diff instead of
makepatch, drop support for genpatch/dopatch (which no one is probably using
anyway), and drop support for JAR32.

The helpfiles project require some explanation.

All the topics in help.txt and wizhelp.txt are broken down into individual
files in helpfiles. logout_cmd_access is located in
~/helpfiles/wizhelp/cnfs/logout_cmd_access, for example. In ~/helpfiles/help
and ~/helpfiles/wizhelp, there are a set of TOC files (i.e. Table of
Contents) files which control which topics to include, where the topics are
located, and which order to include them. One advantage of this approach is
that changes to a single topic can affect multiple versions of help.txt or
wizhelp.txt. That is, the helpfiles for downlevel versions of TinyMUX
benefit from some of the changes made in the latest version.

To re-build help.txt for example, go to ~/helpfiles/tools, and 'g++ -O2 -o
buildhelp buildhelp.cpp'. Copy or link 'buildhelp' into ~/helpfiles/help and
~/helpfiles/wizhelp. You only need to do this once.

Then, in ~/helpfiles/help, ./doit.sh will build help23.txt, help24.txt,
help23.patch, and help24.patch. The later are useful to assure that you are
affecting the changes you intend to make. ./post.sh copies the resulting
help files to TinyMUX23 and TinyMUX24 project for check-in there.

./sort.sh is useful for sorting the TOC files, but remember that some topics
are intentionally out of order. For example the HELP topic is placed first.


Brazil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tinymux.org/pipermail/tinymux/attachments/20051011/41111a18/attachment.html