How to get more out of WebBoard version 4.x, 5.x, and 6.x with Rog's Thread Ordering System (version 1.0)

This describes freeware that I wrote which allows any virtual board manager (or WebBoard administrator) to order the display of threads within a conference.

This is particularly useful for boards in which administrative annoucements are posted, or situations in which WebBoard users have to make "reports" that must be sequenced in a certain order (such as, by date).

The basic idea is the same as WebBoard's built-in "conference order" page, except that it's applied to discussion threads within conferences.

Each thread may have a weight from 0 to 999,999.  Only staff users may assign weights to threads.  "Staff" for this purpose refers to WebBoard administrators, virtual board managers, and conference moderators.

Thread weights can be entered on the posting page by staff members.  The weights are actually carried in the post subject, and are essentially invisible to non-staff members.  For staff members, a link follows the display on the topics page: this link allows staff members to either "show" or "hide" the display of weights in post subjects.

Once a weight is assigned to a post, it will be "inherited" by all the replies to the post.  Preferably, staff members will assign the weight to a thread when the thread is relatively new (i.e. there's only one or perhaps just a few posts in the thread).  After that, the replies to those posts will continue to carry the weight (unless a staff member alters it).

The system will consider all the posts in a thread to have the weight associated with the first displayed post in a thread.  So even if the user decides to display "new" or "attention" messages, the thread should show up in the same sequence, relative to other threads.

If a thread hasn't been explicitly weighted by a staff member, it will be assigned a weight of 100,000 plus the sequence in which WebBoard displays it.  So posts that haven't been explicitly weighted will normally appear last, in the sequence that WebBoard assigns.

However staff members may also assign posts a weight that exceeds 200,000.  These posts will always appear at the end.

This system isn't currently supported for WebBoard 5, or for the "modern" layout of WebBoard 6.  If you need such an animal, please contact me.

I also don't recommend using this system on boards that have conferences with associated news groups or e-mail lists, although nothing terrible will occur if you do.  It's just that replies done via e-mail or a news group won't "inherit" the thread weight: so a staff member will have to edit the post in order to maintain consistency.

This code is freeware.  You use it at your own risk.  No warrany of fitness for use or any other form of guarantee inheres.

You may use it and/or the source code in whole or in part for any otherwise legal purpose that you deem fit; however you may not claim legal ownership of same for legal purposes against anyone who's obtained it from an "independent source" (such as this web page).


1:  Install (1): Complete Install Zips

2:  Install (2): Standard Install

3:  Install (3): Rebuilding the source files, and/or making modifications

4:  Bug reports, comments, and change requests, etc.

5:  Other freeware products

6:  Version history information

7:  Acknowledgements


1:  Install (1): Complete Install Zips

If you want this documentation, as well as all the included zip files, WebBoard 4/5 users can download to4.zip instead.  WebBoard 6 users should download to6.zip.

Once you download the complete zip file, you'll still have to follow the rest of the install instructions.

This system isn't currently supported for WebBoard 5, or for the "modern" layout of WebBoard 6.  If you need such an animal, please contact me.

Return to table of contents

2:  Install (2): Standard Install

For WebBoard 4/5 users, the install file is: to_rel4.zip.

WebBoard 5 users should use all files that end in a "5" as replacements for their equivalents (e.g. use read5.html instead of read.html).

For WebBoard 6, use: to_rel6.zip.

This system isn't currently supported for the "modern" layout of WebBoard 6.  If you need such an animal, please contact me.


These files should be placed on the folder of the board that you designate for the Thread Ordering system.  Note that there is a subfolder called "help" in each of the zips: the files on this folder must end up on the corresponding subfolder of the board.


If you've customized any of the WebBoard pages that are in my install, you'll have to either propagate your customizations to my pages, or propagate my alterations to your customized pages.

Here's a list of each file, along with the role it plays in the various operations:

WebBoard name or name on server: Purpose:
confintro.html Removed the target of "_top" for no frames users who invoke the conferences menu.  See the description of to_tpld.html below.  This file doesn't exist in WebBoard 4.
confnotify.html Removed the display of the thread weight from the subject line in the "watched" topic list.  Since there are no "watched" topics in WebBoard 4, this file isn't present in the WebBoard 4 version.
layout1.html This file was modified to load to_blk1.html on the help subfolder (the URL is actually "help?to_blk1") instead of the topics frame.  This is because 4K of compressed JavaScript source code resides in the toolbar frame, and I don't wish to reload it every time the user refreshes the topics frame.  This is the code that actually reformats the topics list, in order to resequence the threads and optionally remove the weights.  Once the toolbar frame loads completely, it will load the topics list in the topics frame.
msgsearched.html Modified to remove the display of the thread weight from the subject line in the list of messages obtained by a search.
postmsg-f.html Added the code needed to handle thread weights in message subjects when messages are posted.  (For WebBoard 5, this file is called postmsg-f5.html, and it must be renamed to postmsg-f.html.)
postmsg.html Same change as in postmsg-f.html, above.  (For WebBoard 5, this file is called postmsg5.html, and it must be renamed to postmsg.html.)
read.html Removed the weight from the subject line of displayed messages.  (For WebBoard 5, this file is called read5.html, and it must be renamed to read.html.)
readfull.html Same change as in read.html, above.  (For WebBoard 5, this file is called readfull5.html, and it must be renamed to readfull.html.)
help\to_blk1.html (This page is located on the board's help subfolder.)  This is the blank page that initially loads in the topics frame, for frames users.  See the description of layout1.html, above, for more information.  Actually, this page isn't blank: it says "Please wait ... ".
help\to_tpld.html (This page is located on the board's help subfolder.)  This is a frameset that loads whenever topics.html finds that it's the top frame: i.e. whenever the topics list is opened up in a new window, or whenever a "no frames" user logs in.  The frameset consists of two frames: one frame is invisible to the user, and contains toolbar.html - which is where the code that reformats the topics list is stored.  The visible frame is the topics frame, which initially consists of to_blk1.html, for reasons that are explained above, in the desription of layout1.html.  Since there are a few pages that have a target="_top" designation on the "conferences menu" link for "no frames" users, these pages have been modified to remove that target ... for reasons that should be obvious.
toolbar.html This is where the code resides that will reformat the topics list (in order to resequence the threads, and to remove the weights from the subject lines of posts.
topics.html This page captures the topics list, passes it to the code in the toolbar frame, and then displays the reformatted result.
useredit.html Removed the target of "_top" for no frames users who invoke the conferences menu.  See the description of to_tpld.html above.  (For WebBoard 5, this file is called useredit5.html, and it must be renamed to useredit.html.)

Return to table of contents

3:  Install (3): Rebuilding the source files, and/or making modifications

If you want to modify the system, you'll need to download the source code.  For WebBoard 4/5 users, this is in: to_src4.zip.  For WebBoard 6 users, this is in to_src6.zip

Note that these zip files are contained within the "complete" install download, as described in section 1.

You'll need to unzip these files into a new folder on your hard drive.

After you do so, you'll have to install my "JavaScript MakeFile" system onto that same folder: http://www.rs-freeware.org/jsm.

Within the JavaScript MakeFile system, I offer specific instructions for WebBoard users, at: http://www.rs-freeware.org/jsm/jsmdoc.htm#WebBoard_Regenerate.

In a nutshell: after installing the "JavaScript MakeFile" system, you'll have to modify the "make" file: to.mak.

This is the line that you'll have to change:


DEST=f:\\w\\html\\to

DEST should have the folder name of the board from which you wish to run the thread sequencing system.  If you wish to use multiple boards, please be sure to read (?install_mult)section (#?install_mult).

Note that double backslashes are required to separate folder names.

For more information about folder names, please see my DOS primer.

Return to table of contents

4:  Bug reports, comments, and change requests, etc.

You can e-mail me at rog@NOSPAM_rs-freeware.org if you encounter problems, or think that you've found a bug.

I can also be reached by telephone in the U.S. from about 9 AM U.S. central time to 5 PM U.S. central time at: 765-742-6705.  If you don't get an answer, you can use my numeric pager at: 765-417-0664 ... I'll try to call you back, if you're in the U.S, Canada, or Mexico.


Please supply me with as much information as you can about your server, your version of WebBoard, any browser or Operating System that was involved, including the WebBoard Server's Operating System  (9x, NT, 2K, XP?).  Also, please provide any configuration files, or customized WebBoard files that you were using.  Keep in mind that I might actually have to have the opportunity to try what you were doing, in order to diagnose the problem.


BTW, I don't gaurantee to answer all e-mail or fix all bugs, etc.  Please remember that this is freeware, and that my time and resources are limited.

That said, I've put a lot of work into designing, coding, testing, and documenting this product, and I'm probably going to be fairly interested in any comments anyone has, fixing any bugs, and/or extending the scope to applications that strike me as being potentially valuable to a large number of users.


Naturally, if you're willing to hire me to make changes for your special-purpose application, I'm certainly willing to consider your offer.  My standard rate is $75/hr., but I may charge less if the work is to be done for a small business (less than 25 employees), or a nonprofit organization (in the latter case, I might even do it on a gratis basis  :-)  I may also consider charging you nothing if you're suggesting an improvement that I feel is of value to a large number of other users.

You can find out more about me, including references, and a list of clients/projects at: http://www.rs-freeware.org/rog.

Return to table of contents

5:  Other freeware products

WebBoard users will find lots of WebBoard freeware at: http://www.rs-freeware.org/freeware.htm.

Anyone who writes JavaScript  (regardless of whether this is written on the client or server side),  deals with SQL, or who happens to be interested in obtaining the full power available from DOS may wish to check out http://www.rs-freeware.org/free2.htm

Return to table of contents

6:  Version history information

This is version 1.0, released on Nov. 1, 2002.

Updated May 20, 2003 to add WebBoard 5 versions of read*.html, postmsg*.html, and useredit.html.

This documentation was generated by Rog's FAQHack: a DOS/Windows-based freeware program that handles simple macro preprocessing with special support for FAQs and other structured HTML documents.

Return to table of contents

7:  Acknowledgements

I'd like to thank Rachel Rassen, Ph.D, of Lam Research Corp. for her feedback regarding another incarnation of this system.

Return to table of contents