> > Is there a way to simulate an ELOG SUBMIT?
> 
> Have a look at the elog utility which comes in the package. It does exactly 
> this. It "simulates" a browser and does a submit directly to elogd. So you 
> can either redo the elog code somewhere, or call elog with the proper 
> command line parameters to insert logbook entries.

Thank you, Stefan!

Hello everybody.

I am sure that some of you (just like me) experimented already with themes 
and especially now with .CSS in order to give ELOG a different "look" 
and "feel". 

I was wondering if we could maybe share examples of such adapted 
ELOG's .CSS files (or themes). Maybe you can take a screen shot of your 
favorite ELOG "face" (no sensitive data, of course) and post it here as an 
attachement. Or is everybody using only the original look that Stefan 
delivers as default?

Let's share some inspiration. I'll post mine as soon as finished the re-
look.

Tomas

Hi, 

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.

Thus far, the only work-around I could think of is to make a reference to a 
local html file which redirects to the http:// resource outside of the 
server.

When tried the absolute path, i got "The requested 
file /usr/local/elog/http://www.myserver.com/my_elog_menu.htm was not found 
on this server" error message. I'm wondering if it's just a bug or if there 
is a reason for it.

Thanx,
Tomas

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

I guess this question got somehow lost.
So once again : Is there a possibility to EDIT an existing message with 
elog.exe ?

Tomas


> > Is there a way to simulate an ELOG SUBMIT?
> 
> Have a look at the elog utility which comes in the package. It does 
exactly 
> this. It "simulates" a browser and does a submit directly to elogd. So 
you 
> can either redo the elog code somewhere, or call elog with the proper 
> command line parameters to insert logbook entries.

We did some tests of your elog utility. It does what we need except for one 
important thing: EDIT existing messages. Is there a way to edit en existing 
message? Adding a new message or replying to an existing message works fine 
but in our case we need to have the ability to modify messages that were 
created in the past.

Tomas

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. 

I was wondering if there is a way to have a more detailed log of users' 
activities?
Current Logfile = <file> gives a good base for information about 
logins/access to 'protected' logbooks. 

What we would like to have is information about when a user reads an ELOG 
entry (to be able to determine the reaction/response time). 

For instance the LOG could look sg like this: 
%%user %%datetime %%logbook %%record read/edit/new/delete 

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"