I've run into a situation where the SUMMARY view of a logbook will extend
beyond the righthand border, thus requiring the user to scroll right.  This
does not occur in FULL or THREAD mode.  Long lines in the TEXT attribute
appear to be "pushing" the display too far to the right.  Limiting the
number of displayed summary lines works unless the first line is too long.

A temporary fix for this is to set summary lines = 0

> Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 

Where should the tooltip appear? In the entry form or when an entry is
displayed, or even in the tabular listing? I can put a title arround the
attribut names such as

<div title="Please enter some subject here">Subject:</div>

which gets interpreted by most browsers as a tooltip. However it's not
apparent to the user that leaving the cursor on top of "Subject" opens a
tooltip, especially since the cursor is displayed as the text cursor (vertical
bar), not as an arrow over the attribute. Do you have a link to a public web
page which uses tooltips?

> For a complex entry form it is desireable to try and have everything in a
> single window and this, I think, would help.

Aiming for running elog on you PDA? Let me know if you succeed...

Just have a look at elog:571 which should answer your question. Also look at
elog:Config+Examples/4 which is the configuration of this Forum (which as you can
see has all attributes in a single line, even using different fonts).

Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 
For a complex entry form it is desireable to try and have everything in a
single window and this, I think, would help.

Thanks

It is not clear to me how "Format <attribute> = " works.  At first I thought
it would allow me to rearrange how attributes are organized on the html
"page"  using 
# <flags> Sum of following flags:

    * 1: Display attribute in same line as previous attribute
    * 2: Display radio buttons or check boxes in separate lines (if applicable) 

but this does not result in any behavior that I can see.  I must admit that
I am not sure what "Values used for single message display page:" means.

My goal is to provide a more compact page, taking small attributes and
running them across the page rather than straight down.

Thanks

> Can i check , with the new snap shot , can i disable the capability for the admin 
> to delete the logbook and create new logbook
> I tried with the config -
> Allow Delete the logbook = admin 
>  but cannot , please advise

No, disabling the capability to delete the logbook is not implemented. Usually the
admin user is an experienced user who knows what she/he does. The admin user typically
also was write access directly to the elogd.cfg file, and no flag in the world can
then prevent them from adding/removing logbooks by changing elogd.cf directly.

> And As for the id , can i have the month and the day in the id , what is the 
> corresponding field for just the month and day , if there is .

No, but it's on the wishlist. I added your vote there.

> And is there a way to prevent preset value get overwritten when user do a reply
> Example , i preset a field with 
> Preset test = "9v"
> so when the user submit , it will have 9v and they may have enter some following 
> value. but when a user reply , the test field get reset back to 9v

This is clearly a bug. The 'Preset test = 9v' should not be evaluated on a reply. I
fixed that and updated the CVS and snapshot.

- Stefan

> How can I suppress all email notifications? The "Suppress default = 2" flag 
> allows me to always produce a notification, but the flag does not provide 
> an option to never produce a notification. The flag "Suppress Email on 
> edit" does help a bit, but still notifications for new messages will be 
> sent.

Suppress email to users = 1

RTFM

hi again,

we have been doing a bit of stress testing for Elog. The most important 
thing we found is that Elog stops responding when a user uploads a large 
attachment (we used a 240 Mb attachment). 

Is it possible to add a flag in the configuration file, to specify the 
maximum size of an attachment?

Bartjan Wattel