Re: attachment indicator in summary view, posted by Edmundo T Rodriguez on Fri Apr 4 22:53:17 2008
|
Stefan Ritt wrote: |
Dennis Seitz wrote: |
It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.
|
Nice idea. I implemented that feature, as can be seen at the contributions logbook for example. It will be contained in the next release.
|
Would it be possible to instead of appearing a "clip" and/or "multiple-clips" (as the number of attachments grow) to appear a number which will be = to the count of attachments to avoid the column become too wide?
Hope it works because this is tool better every day.
Keep up the GOOD Work! |
Re: how to set locale for date/time, posted by svrmarty on Sun Apr 6 21:13:27 2008
|
Stefan Ritt wrote: |
svrmarty wrote: |
it seems out systemlang is en_US,
#date
Thu Mar 27 14:11:59 CET 2008
and i want to change the local lang only for the elogd.
i tried it with .bash_profile in the elog homedir with
LANG=de_AT
export LANG
but it doesn't work.
how can i change it to get ?
#date
Don Mär 27 14:09:14 CET 2008
|
I investigated this and found that elogd itself does not use the locale properly, so I have to change the code. I will let you know when I fixed this problem.
|
thx |
Re: attachment indicator in summary view, posted by Stefan Ritt on Mon Apr 7 10:01:27 2008
|
Edmundo T Rodriguez wrote: |
Stefan Ritt wrote: |
Dennis Seitz wrote: |
It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.
|
Nice idea. I implemented that feature, as can be seen at the contributions logbook for example. It will be contained in the next release.
|
Would it be possible to instead of appearing a "clip" and/or "multiple-clips" (as the number of attachments grow) to appear a number which will be = to the count of attachments to avoid the column become too wide?
|
Ok, so I show individual clips up to five, and the number of attachments if more than five. |
Re: how to set locale for date/time, posted by Stefan Ritt on Wed Apr 9 22:14:05 2008
|
svrmarty wrote: |
it seems out systemlang is en_US,
#date
Thu Mar 27 14:11:59 CET 2008
and i want to change the local lang only for the elogd.
i tried it with .bash_profile in the elog homedir with
LANG=de_AT
export LANG
but it doesn't work.
how can i change it to get ?
#date
Don Mär 27 14:09:14 CET 2008
|
You do not have to change the environment variable, this is all handled inside elogd. I fixed teh above error in SVN revision 2098. Can you try it? |
Re: Problems with elog client, posted by Stefan Ritt on Wed Apr 9 23:03:53 2008
|
Yoshio Imai wrote: |
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.
Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.
Any ideas?
|
The problem had to do with the integration of native SSL into elog/elogd. I tried to fix it in revision 2099. Please give it a try. I have not tried yet the SSL mode, but I changed the -s for "subdir" to -d not to collide with SSL. |
Re: Sticky entries?, posted by Peter Freeman on Thu Apr 10 01:33:07 2008
|
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible? |
Re: Sticky entries?, posted by Stefan Ritt on Thu Apr 10 07:48:08 2008
|
Peter Freeman wrote: |
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible?
|
Sorry, I overlooked your first question.
Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:
- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"
- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.
- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background. |
Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 14:21:13 2008
|
I have tried the new revision, recompiling both client and server.
Unfortunately, the overall situation has not changed. We can still create new entries using the elog client, but editing an existing entry still does not work. However, thanks to your patch, the -v option now works again for the client side:
> elog -s -h <elog server> -p 443 -l current -u <user> <password> -a <Attributes> "TEST ENTRY"
Message successfully transmitted, ID=1
> elog -s -h <elog server> -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host <elog server>, port 443
Request sent to host:
GET /current/1?cmd=download HTTP/1.0
User-Agent: ELOG
Cookie: unm=<user>;upwd=<password>;
Response received:
ET
Error transmitting message
Again, there is no output on the server side even when running with -v in console mode. There is the expected output when an entry is successfully created using the elog client. One aspect about this output is strange, though: the "Return" statement==== Return ================================
HTTP/1.1 302 Found contains the wrong "Location" header. It is notLocation: https://elog-server.domainname/logbook/ID but ratherLocation: https://client-host.domainname/logbook/ID where "client-host" is the hostname of the computer where the elog client was called. But, since the logbook entry is correctly created, this is perhaps not a problem at all.
Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare the conditions once, e.g.
Options Category = .... , Shift {1} , ....
{1} Options Subject = Shift start {a}, Shift end {b}, ....
but the preset text declarations{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt have to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?
Cheers
Yoshio |