Re: speeding up elog : gcc compile optimizations, posted by Stefan Ritt on Mon Aug 2 09:05:48 2004
|
> Is there something else which is making this difficult to do?
Not really, but hsearch() & Co. are not available under Windows, so I have to extract the
|
too many <table> tags, posted by Heiko Scheit on Mon Aug 2 14:56:56 2004 
|
There are too many <table> tags when displaying a singel entry. E.g.
in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
is not aligned with the others (see attachment).
|
|
Re: too many <table> tags, posted by Stefan Ritt on Tue Aug 3 11:16:46 2004
|
> There are too many <table> tags when displaying a singel entry. E.g.
> in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> is not aligned with the others (see attachment).
|
|
Re: too many <table> tags, posted by Heiko Scheit on Tue Aug 3 13:06:54 2004
|
> > There are too many <table> tags when displaying a singel entry. E.g.
> > in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> > is not aligned with the others (see attachment).
|
|
curly parenthesis problem , posted by Heiko Scheit on Tue Aug 3 15:44:07 2004
|
Everything after curly parenthesis is ignored in attribute entry boxes
like 'Subject' above
|
|
THREAD DISPLAY = sucks up coded spaces, posted by Steve Jones on Fri Aug 6 22:35:10 2004
|
I was trying to do some hard coded spaces using:
Thread display = For: $Date for Shutdown. $DataCenter:
|
|
URL bug in elogd.cfg, posted by Steve Jones on Mon Aug 16 23:49:13 2004
|
Under 2.5.4-2 build1.460, when I edit the demo elogd.cfg the following happens:
- I start with
|
|
text display of ascii files not a good idea, posted by Heiko Scheit on Mon Aug 23 13:43:58 2004
|
I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea. E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
|