halibut/buttress.h, branch master My halibut tree Rename Buttress to Halibut. I _think_ I've caught everything in this pass. 2002-08-05T10:31:35+00:00 Simon Tatham anakin@pobox.com 2002-08-05T10:31:35+00:00 c478f3d9469c09773097eba89342c311ee70a319 [originally from svn r1800] 
[originally from svn r1800]
Keywords are now collected using a B-tree rather than an array with 2001-12-14T12:44:14+00:00 Simon Tatham anakin@pobox.com 2001-12-14T12:44:14+00:00 22b1d999006ac7b67d675305087677c589f03cd6 heapsort. This makes the code much simpler for a start, but the main reason is so that we can spot duplicate keywords as we go along rather than having to wait until the end of input processing. [originally from svn r1489] 
heapsort. This makes the code much simpler for a start, but the main
reason is so that we can spot duplicate keywords as we go along
rather than having to wait until the end of input processing.

[originally from svn r1489]
Allow the user to specify the Help topic ID string for particular 2001-12-06T12:59:37+00:00 Simon Tatham anakin@pobox.com 2001-12-06T12:59:37+00:00 e695cb0dd19d1cbce0c49a71a913527a227a9e09 sections. Useful if another program needs to jump to a particular topic. (Really we should support the proper CTXOMAP / HELP_WM_HELP system for doing this, but I don't like numeric IDs; you'd have to parse a bunch of #defines in order to sensibly synchronise the IDs between help file and code.) [originally from svn r1457] 
sections. Useful if another program needs to jump to a particular
topic. (Really we should support the proper CTXOMAP / HELP_WM_HELP
system for doing this, but I don't like numeric IDs; you'd have to
parse a bunch of #defines in order to sensibly synchronise the IDs
between help file and code.)

[originally from svn r1457]
Indexing in the Help backend now seems to work! Woo! 2001-12-04T21:33:03+00:00 Simon Tatham anakin@pobox.com 2001-12-04T21:33:03+00:00 38181905971fab7106f1f4b90db8da26497158b9 [originally from svn r1450] 
[originally from svn r1450]
This update should bring the Windows Help back end up to 2001-12-04T21:12:40+00:00 Simon Tatham anakin@pobox.com 2001-12-04T21:12:40+00:00 5e3a21913b6a47e78d3e4edd4238d028b90827b7 near-complete functionality. All that's missing now is indexing and horizontal rules. [originally from svn r1449] 
near-complete functionality. All that's missing now is indexing and
horizontal rules.

[originally from svn r1449]
Most of a Windows Help back end now appears to work. Missing are 2001-12-04T19:17:48+00:00 Simon Tatham anakin@pobox.com 2001-12-04T19:17:48+00:00 69d90cdcfde25f6fb52871f0fea9c7b3010c9134 hierarchical topic navigation (menus at the bottom of non-leaf topics, and the Up button) and index support; also I want to give users the ability to specify context IDs for particular topics. Oh, and I haven't found a plausible way to express a horizontal rule in either .RTF or .HLP format. But everything else appears to be there. [originally from svn r1447] 
hierarchical topic navigation (menus at the bottom of non-leaf
topics, and the Up button) and index support; also I want to give
users the ability to specify context IDs for particular topics. Oh,
and I haven't found a plausible way to express a horizontal rule in
either .RTF or .HLP format. But everything else appears to be there.

[originally from svn r1447]
Replace Buttress's old tree23 routines with my shiny new counted 2001-12-04T18:20:21+00:00 Simon Tatham anakin@pobox.com 2001-12-04T18:20:21+00:00 ec2134d20f485b8fbf75632edf895f3aa9073227 tree234 routines; they will be useful in the WinHelp stuff at least. [originally from svn r1444] 
tree234 routines; they will be useful in the WinHelp stuff at least.

[originally from svn r1444]
Introduce the ability to relabel a section as an `example' or 2001-11-24T17:50:55+00:00 Simon Tatham anakin@pobox.com 2001-11-24T17:50:55+00:00 37727cf9cf399f80d8be6994f154256ac09dcfea `question' or so on, using the syntax \S{mysection}{example} An example of foobar so that in cross-references it will be referred to as `example 5.1.2' instead of `section 5.1.2'. NOTE WELL: until now Buttress has supported multiple section keywords using the same syntax, so that you could xref the above section as \k{mysection} _or_ \k{example} with the same effect. This behaviour is now revoked because I don't think anyone was using it; if you suddenly find you're getting undefined-keyword errors this may be why. [originally from svn r1408] 
`question' or so on, using the syntax
   \S{mysection}{example} An example of foobar
so that in cross-references it will be referred to as `example
5.1.2' instead of `section 5.1.2'. NOTE WELL: until now Buttress has
supported multiple section keywords using the same syntax, so that
you could xref the above section as \k{mysection} _or_ \k{example}
with the same effect. This behaviour is now revoked because I don't
think anyone was using it; if you suddenly find you're getting
undefined-keyword errors this may be why.

[originally from svn r1408]
Oops, that new heading-level error check was a bit over-zealous. 2001-10-26T08:08:26+00:00 Simon Tatham anakin@pobox.com 2001-10-26T08:08:26+00:00 474275049b94784ab1ba9fe2bfd75951a46e975a Fixed again. [originally from svn r1330] 
Fixed again.

[originally from svn r1330]
Enforce proper ordering of heading levels: specifically, ensure the 2001-10-25T19:28:43+00:00 Simon Tatham anakin@pobox.com 2001-10-25T19:28:43+00:00 3e043306f1594f7528788a1c593995b391fc7a5a user doesn't skip a heading level (\H before any \C or \A, or \S straight after \C with no intervening \H). The precise criterion is that when creating section a.b.c.d, sections a.b.c, a.b and a should already exist. This ensures the section tree really is a properly formed tree with no missing nodes. [originally from svn r1329] 
user doesn't skip a heading level (\H before any \C or \A, or \S
straight after \C with no intervening \H). The precise criterion is
that when creating section a.b.c.d, sections a.b.c, a.b and a should
already exist. This ensures the section tree really is a properly
formed tree with no missing nodes.

[originally from svn r1329]