> I have a question concerning the "Selection page" ELOG.cfg parameter.
> I was wondering if it is possible to specify a complete (absolute) URL 
such 
> as http://www.myserver.com/my_elog_menu.htm.
> 
> I need this type of configuration because we actually need to have the 
> custom selection page sitting on a different server from the one where 
ELOG 
> is run.

I added this possibility to the source code (->CVS), although it's not clear 
to me how this should work for you. If you don't have access to the server 
where elogd is running, how should elogd then redirect you to somewhere else?

> > I have a question concerning the "Selection page" ELOG.cfg parameter.
> > I was wondering if it is possible to specify a complete (absolute) URL 
> such 
> > as http://www.myserver.com/my_elog_menu.htm.
> > 
> > I need this type of configuration because we actually need to have the 
> > custom selection page sitting on a different server from the one where 
> ELOG 
> > is run.
> 
> I added this possibility to the source code (->CVS), although it's not 
clear 
> to me how this should work for you. If you don't have access to the server 
> where elogd is running, how should elogd then redirect you to somewhere 
else?

Thank you Stefan,
It's not that we wouldn't have access to the ELOGD server, it's the fact that 
we're trying to create our own dynamic selection page (with a more detailed 
overview of the content of different logbooks - such as the date of last 
logbook entry, number of entries in last week, month etc.) based on the 
information we send from ELOG to our SQL server. 

So in this case the user logs on to ELOGD (currently run on Linux) then will 
be redirected to the selection page on a Windows machine (ASP getting all 
necessary information from a MS SQL DB) and the dynamically created links 
refer back to the ELOGD Linux server. May seem a little too complicated but 
works fine.

Tomas

> We are using elog as a small database system, today we came across a 
> problem where 2 people were editing the same record and the first one to 
> submit his changes were overwritten when the second person submitted his.
> 
> Is there anyway to lock a logbook record when someone has pressed EDIT, 
> maybe set a flag in the logbook entry so it has to be unlocked when its 
> submitted by the originator or by an administrator.

I added some code experimentally to avoid double editing. Whenever a message 
is edited, a "stop" sign is displayed in the message list next to the edited 
messages and a warning is issued on the single message display page. If the 
original editing has been given up (browser closed) one can just ignore this 
message. I prefer this solution in comparision with a real locking, since 
the mechanisms for unlocking a stale message by the administrator is not 
necessary. Get the newest code from CVS, get also themes/default/stop.gif to 
display the stop sign, and let me know what you think.

Thanks Ill grab it tomorrow and try it,

when is the new version out btw ?

> Thanks Ill grab it tomorrow and try it,
> 
> when is the new version out btw ?

When I say "under CVS", I mean what I said in elog:233. The new version I 
will release probably next week.

In the Config Examples logbook you mentioned a forum.css.  Do you have a 
link to that css and others?

Thanks

> In the Config Examples logbook you mentioned a forum.css.  Do you have a 
> link to that css and others?

Sure, that's what the "Config Examples" logbook is for. Just click on the 
tab on top of this page. The forum you will find 
under elog:Config%20Examples/4 .

Is there a possibility to integrate into ELOG some more features in terms 
of page formating?

Currently, the .cfg file allows you to specify only the data structure of 
the dataentry/consultation HTML page. And you only have very limited 
possibilities to change the layout of the page (basically only the order of 
attributes on the page and with the help of the .css file the font, color 
and background of the page as a whole).

What we would like to do is to :
+ apply a stylesheet class to an attribute (change the particular TD class)
+ specify the width of a textfield (sometimes it is really not necessary to 
have such a long textfield area for a 3-letter long code)
+ put an attribute on the same line as the previous one (instead of putting 
it automatically on the next line)

Therefore, in addition to the current attributes & parameters, we suggest 
the following syntax in the .cfg file:
+ parameter AttribPos which would specify the position of an attribute, 
it's lenght (for text attributes only) and the .css class to apply
+ parameters in [] are optional
AttribPos AttribName = same_line, width, [class]

Examples: 
AttribPos DateUp =  0,20, [important]   
+ Attribute "DateUp" will be put on the next line, the textfield width will 
be 20 characters and a .important class will be applied to it from the 
default (or specified) .css file.

AttribPos DateUp =  1,15,
+ this puts the DateUp attribute on the same line, width 15

We believe that these improvements would help to make the ergonomy of the 
screen better and thus facilitate the user-dataentry/consultation.