> I was trying to do some hard coded spaces using:
> 
> Thread display = For: $Date for Shutdown.   $DataCenter:
> $short summary. Coordinator: $Shutdown Coordinator.
> 
> The spacing actually works mthe first time, but upon going back into editing
> the config file, the coded spaces are gone, replaced with real spaces, and
> when saved all real multiple spaces are, as one would expect, ignored.  The
> spacing reverts back to normal.
> 
> I tried other html tags but these show up as literals.

I fixed that in revision 1.448. The problem also showed up even in normal
logbook entry displays and in replies (before this fix, the   in this text
whould not have shown up). Get the new version from CVS.

> First - Some of the logbook entries should not be viewed by certain users.  
> What would be the easiest way to restrict viewing some entries?  

The easiest way is to define two logbooks, with two different password files.
The more restricted logbook contains only those users who are allowed to see the
restricted entries. Use the commands "Move to" to move entries between the two
logbooks (see documentation).

> Second - I have a welcome page for the ELOG that lists some info about the 
> ELOG.  When I start the ELOG, the user sees the login page.  After the user 
> logs in, the welcome page appears listing the restrictions.  Right now, I 
> have a hyperlink that takes the user to new, find, etc.  But I would like 
> to take the user right to the logbook and not have to come back to the 
> welcome page everytime.  How can I do this?

Right now you need an exteral page on a public webserver. This page contains
then links to your elog server. I the next version I will implement the
possibility to server *.html files directly through elog. You can then put your
welcome page under themes/default/Welcome.html, and access it through the
starting link:

http://your.elog.server/logbook/Welcome.html

You will only see the Welcome page once, since all links in elog will point back
to .../logbook/ and not to .../logbook/Welcome.html. The config option "Welcome
page = Welcome.html" you have to remove then of course. 

> The help text on the website says the following:
> 
> "The command Select can be used to select multiple messages for deletion of
> moving to other logbooks."
> 
> This is not clear but was the intent to indicate that SELECT can be used to
> either select multiple log entries for deletion OR for moving to another
> logbook?  If the latter, then this does not work if one adds the MOVE TO
> menu item to the list.  If the former then the helptext is a little misleading.

SELECT can be used for deletion OR moving OR copying. To enable the copy and move
commands, they have to be present in the "Menu commands" list, like

Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
to, Help

I added an appropriate note to the documentation, sorry for the misleading descriptoin.

> Thank you.  I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
of logbooks.

You get the "Move To" button only after pressing "Select", otherwise it does
not make sense. See attached screendump and config example.

> Just for grins, what version of compiler are you using under Linux?

gcc 3.2.2 (from RedHat Linux 9.0)

> > Thank you.  I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
> of logbooks.
> 
> You get the "Move To" button only after pressing "Select", otherwise it does
> not make sense. See attached screendump and config example.

Hmmm.  I like the little buttons with the pull-downs for selections. 
Unfortunately, I don't get that.  With a config of:

Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help

my screen only shows the "toggle" and "delete" buttons.  Was there a recent rev
that allowed this to happen (I didn't see a comment on this).  

BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
to show multiple "Move To" links (one for each logbook) or should there also be
pulldowns?  

Thanks

> > Just for grins, what version of compiler are you using under Linux?
> 
> gcc 3.2.2 (from RedHat Linux 9.0)

Well, I am running 2.95.3 - hmmm.  We have 3.3.2 - perhaps I'll try that and
see if there is a difference.

> Hmmm.  I like the little buttons with the pull-downs for selections. 
> Unfortunately, I don't get that.  With a config of:
> 
> Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
> Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help

Unfortunately menu commands are case sensitive, so you need a "Move to" instead a "Move
To". I changed this in the code so future versions will not be case sensitive any more.

> BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
> to show multiple "Move To" links (one for each logbook) or should there also be
> pulldowns?  

On the log entry screen, only menu links are possible for internal reasons, that's why I
have chosen that display mode. I agree that it can look clumsy if you have many
logbooks, but there is the "move to = <logbook list>" option to restrict the number of
target logbooks.