> Hello,
> I am running Elog V2.1.3 on Solaris 8 and I was very pleased about this 
> tool.But now I have a problem: Sometimes it takes a lot of time submitting 
> an entry into a logbook, up to 3 minutes. This behaviour does only occur 
> sometimes. Did anyone of You experience something like this?

I have seen that behaviour only with certain versions of Netscape, running on 
the same machine than the elogd server. Since I did not observe this with IE 
or Opera, I attributed this to a Netscape flaw. Have you tried different 
versions of Mozilla?

- Stefan

> When I make a new entry I get an email with 
> 
>    subject: New ELOG entry
> 
> But when I or someone else changes an entry I also get an email with a 
> 
>    subject: New ELOG entry
> 
> I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my 
> programming capabilities so I enter this request.

I have implemented this feature in V2.2.2.

> I noticed a long url got hard-wrapped when I entered a long one, I patched 
> the source code. I don't know if this was done intentionally, otherwise you 
> might want to change this also.
> 
> diff elogd.c elogd.c.org 
> 4468c4468
> <     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
> ---
> >     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

If the wrap=soft is used, users tend to enter very long lines (without 
hitting return in between). If this line then gets displayed, it can be very 
wide and the user has to horizontally scroll the browser window. What I can 
do is in the display (not the entry) to concatenate URLs which are separated 
only by a CR/LF. But you then have some cases where you have an URL to the 
end of the line, then some other text starting on the next line, which then 
get concatenated falsely (unless you use some clever code which scans 
for ".html" or "xxx/xxx" or something like that.

> Now I don't like both parameters. 20 is too long for my display (1024x768) 
> and 76 is too short. Something dynamically would be cool, but a parameter 
> somewhere in a config file would also be acceptable. (just a thought, makes 
> it easier to upgrade)

You always had the option "Message width = xx" to change the width on the 
text box, and I added in V 2.2.2 the parameter "Message height = xx" where 
you can change the 20 to something else.

> if you have a site that requires authentication to the smtp server, how do 
> you specify this info in elog???
> 
> thanks,
> eric

This is not implemented right now. Unfortunately, I don't hve an smtp server 
here which requires authentication, so I cannot develop this. If anyone has a 
server from which I have *remote* access from here (pc810.psi.ch), I will put 
this additional authentication in.

When I make a new entry I get an email with 

   subject: New ELOG entry

But when I or someone else changes an entry I also get an email with a 

   subject: New ELOG entry

I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my 
programming capabilities so I enter this request.

I noticed a long url got hard-wrapped when I entered a long one, I patched 
the source code. I don't know if this was done intentionally, otherwise you 
might want to change this also.

diff elogd.c elogd.c.org 
4468c4468
<     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
>     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set 
hard to:

  /* set textarea width */
  width = 76;

Now I don't like both parameters. 20 is too long for my display (1024x768) 
and 76 is too short. Something dynamically would be cool, but a parameter 
somewhere in a config file would also be acceptable. (just a thought, makes 
it easier to upgrade)

if you have a site that requires authentication to the smtp server, how do 
you specify this info in elog???

thanks,
eric

Hello,
I am running Elog V2.1.3 on Solaris 8 and I was very pleased about this 
tool.But now I have a problem: Sometimes it takes a lot of time submitting 
an entry into a logbook, up to 3 minutes. This behaviour does only occur 
sometimes. Did anyone of You experience something like this?