| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1364
|
Tue Aug 2 08:56:21 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour? |
Can you send me your elogd.cfg ?
Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text. |
|
1374
|
Thu Aug 4 22:35:57 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
| Attachment 1: summary.jpg
|
|
| Attachment 2: full.jpg
|
|
|
1383
|
Fri Aug 5 10:54:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
| Kees Bol wrote: | Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here. |
If you do not want text display in the summary view, add
Summary lines = 0
into your config file.
| Kees Bol wrote: | Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it. |
|
1405
|
Mon Sep 5 20:16:50 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.5.7 | Re: charset specified in elog.conf has no effect [updated] |
| cunnilinux wrote: | well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default) when i specified charset in the global section, the problem's gone away.
2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset
elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc
|
The documentation clearly states that the "charset" option is under the [global] section. I put it there since it does not make much sense to have separate charsets for separate logbooks. Or do you have one Russian, one Japanese and one Swedish logbook on the same server? Maybe for an international language school 
I can easily put it into the individual logbook's config, but only if more than one person requests this. |
|
1551
|
Thu Dec 15 13:08:35 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.0 | New ELOG version 2.6.0 |
Dear ELOG users,
I'm happy to announce the release of ELOG version 2.6.0. After a long period of beta testing, all functions are now sufficiently stable for a public release. The major new feature is the introduction of the ELCode tags. They are similar to the well known BBCode tags, and let you format an elog entry. It is now also possible to embed inline images in an elog entry  , which are even sent in email notifications.
So have fun,
Stefan |
|
1555
|
Tue Dec 20 09:18:19 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | SVN 1579 | Shell substitution, especially interesting for running online experiments |
Shell substitution has been introduced in an experimental state of the current SVN version of ELOG. It woks such that the subsititution list can contain $shell(<argument>) commands. The <argument> is passed to the shell of the operating system and the result is captured and subsituted. This is handy for online experiments, where one wants to pass information automatically to elog. Assume that there is a file /tmp/runnumber containing the current run number of the experiment. All one needs to put the current run number in an attribute "Run number" is the following line in the configuration file:
Preset Run number = $shell(cat /tmp/runnumber)
This subsitution works also for the main text body. Following option will put a calendar of the current month into the text body:
Preset text = $shell(cal)
note that shell subsitution works both on Windows and Unix, the "cat" and "cal" commands are however only present under Unix, but "cat" can be replaced with its Windows counterpart "type". |
|
1556
|
Tue Dec 20 11:17:17 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | 2.6.0 | Howto insert screen dumps into an elog entry |
With the new ELCode tags, one can insert screen dumps pretty easy into elog entries. I personally use HoverSnap 0.8 under Windows, there are similar tools under Linux. HoverSnap puts a "Capture.jpg" file in a selectable directoy when you press PrintScreen, then you can instert this file with the  button. Here is such a screendump example:
 |
|
1558
|
Wed Dec 21 20:39:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: 2.6.0-bata5 |
| Carl Shirey wrote: | Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help. |
There is a 2.6.0 out by now. |