Thank you very much for your request, well motivated and described. I hope I 
will soon find time to impelment this.

I implemented your request. The syntax is:

Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>

<flags>
  Sum of following values:
    1: Display attribute in same line as previous attribute
    2: Display radio buttons or check boxes in separate lines (if applicable)

<css_class_name>,<css_class_value> 
  Cascading Style Sheet class names used for cells containing attribute name
  or value, respectively. The classes must be defined in the style sheet file 
  (usually themes/default/default.css)

<width>> 
  Width of the text entry field in characters

<size> 
  Maximum number of characters allowed. 

Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
ommitted, so specifying for example only the flags is possible.

In order to have several attributes in one line, each line is now a separate 
table. This requires adjustment of the CSS class "attribname". Best you use 
the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).

You can compare the two different approaches (one attribute per line/multiple 
attributes per line) in this forum and the "archive" logbook. The "subject" 
field in this forum also uses a different style class.

Note that if you upgrade to the current CVS version 
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
have to change following options in your elogd.cfg:

- The style sheet must contain the new class "attribhead"
- "Email message body" has been replaces by "Email format"
- "Filtered browsing" is now off by default
- Locking (during editing of messages) is disabled by default, and enabled 
by "Use lock = 1"

Very interesting, indeed!
Thank you very much for the implementation. I believe this is a big step ahead 
in terms of ELOG screen formating (and therefore easier/more ergonomic 
dataentry/reading).

We will test your modifications as soon as you make a new release.

Tomas


> I implemented your request. The syntax is:
> 
> Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>
> 
> <flags>
>   Sum of following values:
>     1: Display attribute in same line as previous attribute
>     2: Display radio buttons or check boxes in separate lines (if applicable)
> 
> <css_class_name>,<css_class_value> 
>   Cascading Style Sheet class names used for cells containing attribute name
>   or value, respectively. The classes must be defined in the style sheet file 
>   (usually themes/default/default.css)
> 
> <width>> 
>   Width of the text entry field in characters
> 
> <size> 
>   Maximum number of characters allowed. 
> 
> Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
> ommitted, so specifying for example only the flags is possible.
> 
> In order to have several attributes in one line, each line is now a separate 
> table. This requires adjustment of the CSS class "attribname". Best you use 
> the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).
> 
> You can compare the two different approaches (one attribute per line/multiple 
> attributes per line) in this forum and the "archive" logbook. The "subject" 
> field in this forum also uses a different style class.
> 
> Note that if you upgrade to the current CVS version 
> (http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
> have to change following options in your elogd.cfg:
> 
> - The style sheet must contain the new class "attribhead"
> - "Email message body" has been replaces by "Email format"
> - "Filtered browsing" is now off by default
> - Locking (during editing of messages) is disabled by default, and enabled 
> by "Use lock = 1"

I know there's an item on the wishlist for password expiration, so how 
about account expiration..?? (after so many days of inactivity).

One complaint that comes from management is that when a user leaves the 
agency, the elog account seems to never get deleted.  There way of asking 
me, why I never keep up with the user account deletions.  Ha Ha, like I 
have time to constantly compare the user list from elog to the user list of 
other systems.

Another plea on my part, for Elog to allow for authentication via external 
database - such as LDAP, so we wouldn't have to maintain another user 
database.

Thanks,
Eric

> I know there's an item on the wishlist for password expiration, so how 
> about account expiration..?? (after so many days of inactivity).

Ok, added to the wishlist.

> Another plea on my part, for Elog to allow for authentication via external 
> database - such as LDAP, so we wouldn't have to maintain another user 
> database.

I had that request more than once. The problem with it is that I cannot 
implement it, since he have no LDAP server here at our institute to try it. So 
if someone teaches me how to do LDAP authorization correctly, I can put it in, 
but not before.

whishlist

an entry like
file:///E:/Dossier\!!shorcut
will open IE with these current adresse

Stef could you add a logbook  
'wishlist'
'subgroup' contribution/icons

> an entry like
> file:///E:/Dossier\!!shorcut
> will open IE with these current adresse

Yes it does, and what is your question?

> Stef could you add a logbook  
> 'wishlist'
> 'subgroup' contribution/icons

If you have any icons, just put it under the contributions logbook. There 
are only few entries, so no deed to make a subgroup.

As for wishlist, start with the "Forum" Logbook. If a wish gets "accepted", 
I put it on the official web page.

> > an entry like
> > file:///E:/Dossier\!!shorcut
> > will open IE with these current adresse
> 
> Yes it does, and what is your question?
> 
> > Stef could you add a logbook  
> > 'wishlist'
> > 'subgroup' contribution/icons
> 
> If you have any icons, just put it under the contributions logbook. There 
> are only few entries, so no deed to make a subgroup.
> 
> As for wishlist, start with the "Forum" Logbook. If a wish gets "accepted", 
> I put it on the official web page.

sorry for my 'stupid' question please delete this entry :)