> 1. Is there a possiblity to fix the position of the attribut fields if they are in
> the same line? As. ex. if one attribute is empty or contain a very short value it may
> be possible that the position of the following atrributes in the line are moving to
> the left, if the value is very long, they move to the right side. This make it
> sometime not easy to read the informations, specially if the user browses trough some
> entries, the picture the eyes are scanning is changing.

Yes there is a possibility. In the format option, you can specify two CSS names, one for the
attribute and one for it's value. The default ones are "attribname" and "attribvalue". Just
make new ones by copying these two, renaming it to something like xxxname and xxxvalue where
"xxxx" is the name of the attribute. You find that in the file themes/default/default.css.
They contain a field called "width:" which can be changed:

.typename {
  width:150px;             <-- must be changed
  background-color:#CCCCFF;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  padding:3px;
}

By having separate classes for all attributed, you can change their width separately,
accomplishing hopefully what you need.

> 2. Did I understand you right, that tis will not work while editing? I would like to
> put this to the wish list for a uppcoming version (not very importand, but VERY nice
> to have), that it may be possible to use Format in the new and edit mode too, because
> it is somtimes more comfortable to have some attributes grouped locically in one line
> or to have a overview over all attributes on one screen without scrolling while editing.

I will put this on the wishlist.

Stefan

> Options Student name  = "Doe, John", "Foo, Bar".

I fixed this bug. Please obtain the newest snapshot (see download page).

> I know I can simply copy the settings for logbook B and repeat the settings 
> for all logbooks C-S. But is there a better way to accomplish this?

Yes. Put all common settings into the [global] section, only differences into
the individual logbook sections. Like

[global]
Attributes = ....
Options ....

[A]
; Logbook A is different
Attributes = ....
Options = ...

[B]
Option X = ...

[C]
Option X = ...

[D]
Option X = ...

This way all logbooks "inherit" the settings from the [global] section, only the
differents are superseeded in the individual sections. Still you need two lines
for each logbook, but all recurring configuration can be omitted.

> Suppose I want to have different password files for all the logbooks, but I want to 
> have a single (admin) user that can log in to all logbooks... Do I need to specify 
> the admin data in all the different password files, or can I use one global 
> password file containing the login name and password for the administrator?

I would not recomment different password files for all logbooks, but a common one and
individual "login user" options on the logbooks, like

[global]
Password file = xxx
Admin user = xxx
...

[A]
Options X = ...
Login user = <user1>,<admin user>

[B]
Option X = ...
Login user = <user2>,<admin user>

This has the advantage that there is only a single password file which is easier to
maintain.

Thanks for pointing out this bug. I fixed it. New version under CVS.

> 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

> 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

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).