[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::online_bookbuilding

Title:	Online Bookbuilding
Notice:	This conference is write-locked: see note 1.3.
Moderator:	VAXUUM::UTT

Created:	Fri Aug 12 1988
Last Modified:	Mon Jul 15 1991
Last Successful Update:	Fri Jun 06 1997
Number of topics:	440
Total number of notes:	2134

378.0. "How to chunk <MSG> sections?" by PHAROS::ILSLEY () Fri Oct 12 1990 18:21

Are there any special rules for coding sections that use <MSG> tags?
One of our writers has two or three pages of messages under a <HEADn>
tag. When displayed in Bookreader, you have to select Next Topic to 
display the second screen of messages; the message that starts the
second screen becomes a topic. You can't select More to get to the                   
second screen...

T.R Title User Personal
Name Date Lines

378.1 it's on the wishlist OLD::UTT Don't worry, be crabby. Mon Oct 15 1990 10:33 22

T.R	Title	User	Personal Name	Date	Lines
378.1	it's on the wishlist	OLD::UTT	Don't worry, be crabby.	`Mon Oct 15 1990 10:33`	22
	Messages (and glossary terms and definitions) are broken arbitrarily into topics every n messages (or <gterm>/<gdef> blocks). This approach was taken over: 1. making each message a topic -- this would probably be pretty annoying since each message would then appear separately in the topic window. 2. make the whole message section a topic -- in a long message section, the scrolling from top to bottom would be cumbersome. The side effect of making every n messages a topic is that the first set of messages is a topic, which is why you have to click on Next Topic to get from the header to the messages. People have made the same complain about glossaries. It is on the wishlist to be fixed but so far there have been more pressing problems and bugs. Thanks, Mary

    Messages (and glossary terms and definitions) are broken arbitrarily
    into topics every n messages (or <gterm>/<gdef> blocks). This approach
    was taken over:
    
    1. making each message a topic -- this would probably be pretty
       annoying since each message would then appear separately in 
       the topic window.
    
    2. make the whole message section a topic -- in a long message
       section, the scrolling from top to bottom would be cumbersome.
    
    The side effect of making every n messages a topic is that the
    first set of messages is a topic, which is why you have to click
    on Next Topic to get from the header to the messages.
    
    People have made the same complain about glossaries. It is on the
    wishlist to be fixed but so far there have been more pressing
    problems and bugs.
    
    Thanks,
    
    Mary