can one use a IOption field for conditional tests?, posted by FX FRERE on Tue Feb 9 18:54:22 2010
|
Hi again,
I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:
IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK
{1} Show Attribute Edit = Attribute1, Attribute2
Thread Icon = Status
Attribute1 and 2 do not have any sense if the result was successful,
ELOG interprets the {1} and {2} as being part of the icon name!
thanks again for your help
FX |
Re: can one use a IOption field for conditional tests?, posted by Stefan Ritt on Fri Mar 12 11:26:27 2010
|
FX FRERE wrote: |
Hi again,
I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:
IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK
{1} Show Attribute Edit = Attribute1, Attribute2
Thread Icon = Status
Attribute1 and 2 do not have any sense if the result was successful,
ELOG interprets the {1} and {2} as being part of the icon name!
thanks again for your help
FX
|
Conditions won't work for IOption attributes. You need an additional attribute like:
Attributes = Status, Subject, Icon
Options Status = OK{1}, Failed{2}
Ioptions Icon = icon1.gif, icon2.gif
{1}Preset icon = icon1.gif
{2}Preset icon = icon2.gif
|
Grouping Logbooks, posted by mike cianci on Sun Dec 14 17:04:24 2008
|
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
Re: Grouping Logbooks, posted by Stefan Ritt on Mon Dec 15 09:01:35 2008
|
mike cianci wrote: |
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data. |
Re: Grouping Logbooks, posted by mike cianci on Fri Feb 12 08:31:14 2010
|
Stefan Ritt wrote: |
mike cianci wrote: |
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data.
|
Stefan, sorry to bother you yet again. but I can not seem to get the "Subdir" to do what I want (user error I am sure). Thanks for any help you can give.
[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1
[OLH.gsh]
Subdir = \\ssoelog\ELOG\logbooks\OnlineHelps
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1 |
Re: Grouping Logbooks, posted by Stefan Ritt on Fri Mar 12 10:15:20 2010
|
mike cianci wrote: |
Stefan, sorry to bother you yet again. but I can not seem to get the "Subdir" to do what I want (user error I am sure). Thanks for any help you can give.
[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1
[OLH.gsh]
Subdir = \\ssoelog\ELOG\logbooks\OnlineHelps
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1
|
First of all, why do you a reply to a very old message? For each new topic you should start a new thread.
I don't know exactly what goes wrong in your case. Just a few ideas:
- Having a '.' in a logbook name can cause trouble, better remove it
- Having a subdir starting with '\\' might work, but I never tried it, does it work if you use a subdirectory on the same drive just with "Subidr = \elog\..." ?
- There is also the option "Logbook dir = ..." which you might try
|
Log Thread Close Automatically, posted by tom on Sat Feb 20 14:57:27 2010
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages. |
Re: Log Thread Close Automatically, posted by Yoshio Imai on Mon Feb 22 11:15:48 2010
|
tom wrote: |
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
Did you consider using the "Restrict edit time" option? It should provide the necessary functionality, as long as you don't want to lock the entry at a fixed absolute time, but really only x hours after creation (also, as you talked about closing the "thread" automatically, there is no option to prevent replies after a certain amount of time).
See the administrator's guide. |
Re: Log Thread Close Automatically, posted by Stefan Ritt on Fri Mar 12 09:18:11 2010
|
tom wrote: |
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
What you need is
Restrict edit time = ...
as written in the manual. |
Limit elog e-mail to only people involved with an entry, posted by Paul Paquette on Sat Mar 6 19:13:55 2010
|
Howdy and Thank you in advance.
Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry. I have the Elog server on Windows XP Pro running version 2.7.8.2282.
Thank you
Paul
|
Re: Limit elog e-mail to only people involved with an entry, posted by Stefan Ritt on Fri Mar 12 08:57:07 2010
|
Paul Paquette wrote: |
Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry. I have the Elog server on Windows XP Pro running version 2.7.8.2282.
|
That should be possible with the following configuration options:
Suppress email to users = 1
Email all = <your e-mail>, <your supervisor e-mail>, $user_email |
Wrong author when replying a reply, posted by Mads Jessen on Mon Mar 8 16:16:39 2010
|
When replying on a reply, the author is set to the author on the original reply? Othervice it workes great!
part of code:
...
Preset Author = $long_name
Locked Attributes = Author
Subst on reply author = $long_name
...
|
Re: Wrong author when replying a reply, posted by David Pilgram on Tue Mar 9 00:48:28 2010
|
Just to say that this bug was fixed some time ago - I don't remember when (a senior moment).
I know because I reported it to Stefan (along with the rest of the universe), as it was appearing
on this forum when it was running on that particular SVN version.
If you update to the latest version of elog, all will be fine.
David.
(helping Stefan, since I usually give him such a hard time). |
Re: Wrong author when replying a reply, posted by Stefan Ritt on Thu Mar 11 15:38:32 2010
|
Mads Jessen wrote: |
When replying on a reply, the author is set to the author on the original reply? Othervice it workes great!
part of code:
...
Preset Author = $long_name
Locked Attributes = Author
Subst on reply author = $long_name
...
|
I use:
Preset Author = $long_name
Preset on reply Author = $long_name
|
Summary text field is empty for replied entries, posted by Thomas on Thu Mar 11 12:01:35 2010
|
It is possible to show the (new) text of a replied entry in the summary text field ?
Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.
|
Re: Summary text field is empty for replied entries, posted by Stefan Ritt on Thu Mar 11 14:59:29 2010
|
Thomas wrote: |
It is possible to show the (new) text of a replied entry in the summary text field ?
Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.
|
In principle you can adjust the number of lines shown in the summary text file with the option summary lines = x. If you increase that value, you start seeing some part of the reply. For elog itself it is impossible to distinguish the reply text from the origial text, since some people use plain text like
> original
> text
reply
with the reply sometimes below, sometimes above the original text. Other people use full HTML with tables (like in this forum), where it is very hard internally to distinguish between original and reply text. The easiest is not to quote the original text in replies, then you will see it always. |
Re: Summary text field is empty for replied entries, posted by Thomas on Thu Mar 11 15:29:40 2010
|
Stefan Ritt wrote: |
Thomas wrote: |
It is possible to show the (new) text of a replied entry in the summary text field ?
Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.
|
In principle you can adjust the number of lines shown in the summary text file with the option summary lines = x. If you increase that value, you start seeing some part of the reply. For elog itself it is impossible to distinguish the reply text from the origial text, since some people use plain text like
> original
> text
reply
with the reply sometimes below, sometimes above the original text. Other people use full HTML with tables (like in this forum), where it is very hard internally to distinguish between original and reply text. The easiest is not to quote the original text in replies, then you will see it always.
|
Thank you very much for your answer.
Is there any way to invert the order of the original text and the reply text ? |
Re: Summary text field is empty for replied entries, posted by Stefan Ritt on Thu Mar 11 15:35:40 2010
|
You just start writing on top of the cited text 
Thomas wrote: |
Stefan Ritt wrote: |
Thomas wrote: |
It is possible to show the (new) text of a replied entry in the summary text field ?
Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.
|
In principle you can adjust the number of lines shown in the summary text file with the option summary lines = x. If you increase that value, you start seeing some part of the reply. For elog itself it is impossible to distinguish the reply text from the origial text, since some people use plain text like
> original
> text
reply
with the reply sometimes below, sometimes above the original text. Other people use full HTML with tables (like in this forum), where it is very hard internally to distinguish between original and reply text. The easiest is not to quote the original text in replies, then you will see it always.
|
Thank you very much for your answer.
Is there any way to invert the order of the original text and the reply text ?
|
|
Single Button Entry, posted by Geoff Ellis on Tue Feb 16 04:17:24 2010
|
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this? |
Re: Single Button Entry, posted by Yoshio Imai on Thu Feb 18 18:50:57 2010
|
Geoff Ellis wrote: |
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide). |
Re: Single Button Entry, posted by Capt. Ben Smith on Sun Feb 28 07:25:10 2010
|
Geoff Ellis wrote: |
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
This would be of value for me as well. I'm trying to develop a event log for a research ship. Thanks. -ben |
Re: Single Button Entry, posted by Stefan Ritt on Wed Mar 3 14:29:08 2010
|
Capt. Ben Smith wrote: |
Geoff Ellis wrote: |
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
This would be of value for me as well. I'm trying to develop a event log for a research ship. Thanks. -ben
|
There are several ways:
1) Use conditional attributes (see https://midas.psi.ch/elog/config.html#conditional). If you have several standard entries, put the into the option list of a "type" attribute. Then depending on that value, you can pre-populate other attributes/options. This is then not a single-button solution, but a single-click plus one selection from a drop-down list solution which should be pretty close.
2) You can make a bookmark in your browser. Take the URL of the logbook, add "?cmd=New" and then for each attribute you can select a preset value using "&p<attribute>=<value>". So for example on the demo logbook you can use
https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&ptype=Routine&pcategory=General&pauthor=Ellis
which opens the new entry dialog, and pre-set values for Type, Category and Author. Then you can make several bookmarks for different standard entries.
- Stefan |
Preset text =, posted by tom on Sat Feb 20 18:29:31 2010
|
I am looking for the correct syntax for Preset Text =
I have an html file I want set in the editor so that my users can just enter in the data below the predetermined heading. What is the correct syntax/file location.
Thanks! |
Re: Preset text =, posted by Stefan Ritt on Sun Feb 21 13:48:56 2010
|
tom wrote: |
I am looking for the correct syntax for Preset Text =
I have an html file I want set in the editor so that my users can just enter in the data below the predetermined heading. What is the correct syntax/file location.
Thanks!
|
The documentation says:
Preset text = <string> or <file>
This preset value is used for the main body text. It can be a string or a file, which must be present in the logbook directory. Alternatively, an absolute path can be used if the file name starts with a "/" (Unix) or "\" or "x:" (Windows).
and there is nothing to add. There is no special syntax on that file, it just gets copied 1:1 into the edit box. |