ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
733
|
Thu Oct 14 21:45:32 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.5.4-5 | Re: Extra 'append on edit' action when adding attachment |
I fixed that in revision 1.496 (see CVS). |
750
|
Fri Oct 29 20:14:17 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.5.4-6 | Re: some things for your wishlist |
> 1) elogd should report quota or disk-full problem: In case a logbook
> entry cannot be saved (quota or disk full) then a message like
> 'Could not save last entry. Please contact administrator.' should
> be displayed. Currently nothing happens. Only the submitted
> entries 'vanish'.
That has been fixed in meantime.
> 4) mark messages as unread/read on a per user basis: The
> implementation of this might be quite involved but it would be
> rather useful. One way would be to add a default attribute 'Seen
> by' to each entry, which lists the login names of the users. Or
> files LOGIN_NAME.has_seen can be created which contain the entry
> IDs of the viewed entries for each user.
There is an elegant way to achieve this already now: Use an RSS reader (like
SharpReader for Windows or Straw from Linux) and subscribe to a logbook. Then don't
read the entries directly in the logbook, but read them in your RSS reader. Once you
read them, they become automatically marked read.
> 5) alignment of attribute table (using <td colspan=2> for multi line
> stuff): see elog:669 :)
Has been fixed as well.
> - Use "and" and "or" operands in queries
Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
<str1>|<str2>
and for a "<str1> AND <str2>" one can write
<str1>.*<str2>|<str2>.*<str1>
Looks a bit complicated, but maybe some day we will get some code which rewrites
"AND" and "OR" as regular expressions. |
755
|
Sun Oct 31 20:09:31 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Request | All | 2.5.4-6 | Re: some things for your wishlist |
> > - Use "and" and "or" operands in queries
>
> Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
>
> <str1>|<str2>
>
> and for a "<str1> AND <str2>" one can write
>
> <str1>.*<str2>|<str2>.*<str1>
>
> Looks a bit complicated, but maybe some day we will get some code which rewrites
> "AND" and "OR" as regular expressions.
It seems that the quick filter searches are now (2.5.4-6) case sensitive.
Could you add an option to specify this in the config file? Or does it
exist already? |
801
|
Sat Nov 20 19:44:57 2004 |
| Ognyan Kulev | ogi@fmi.uni-sofia.bg | Request | All | | Partial Bulgarian translation |
Hi, we are using ELOG for keeping track of a server maintainance. I've
translated some of ELOG's strings. The file is attached. There will be
more translations, when I get inspired again ;-) |
806
|
Wed Nov 24 00:42:10 2004 |
| Rich Persaud | dev2id at yahoo dot com | Request | All | 2.5.4-6 | Attribute Negative Search |
Is there any way to search for all attributes _except_ a certain value? |
808
|
Wed Nov 24 00:45:43 2004 |
| Rich Persaud | dev2id at yahoo dot com | Request | All | 2.5.4-6 | Display links for multiple-option attributes |
Can "Display" links work with multiple options?
"ABC | DEF" is currently one link.
Ideally, it would be two links, each formatted per the "Display" string. |
809
|
Wed Nov 24 00:48:17 2004 |
| Rich Persaud | dev2id at yahoo dot com | Request | All | 2.5.4-6 | Non-wildcard or numeric search for numeric attribute |
Is there a way to disable wildcard matching in searches?
A search for "1" returns "1" and "10" and "11".
Is there a way to perform an explict match?
Could there be a numeric match if the attribute type is numeric? |
810
|
Wed Nov 24 00:50:27 2004 |
| Rich Persaud | dev2id at yahoo dot com | Request | All | 2.5.4-6 | Multi-parent relationships between logbook items |
Could there be a multi-value option for free text fields, e.g. comma-
separated? This would allow multi-parent relationships between log items.
E.g. specifying 12, 15 as a value would create unique Display links
for "12" and "15", based on the Display specification for that attribute.
This would be like "multiple fixed options", for the purpose of formatting. |