Working Ubuntu 10.10 ELOG binaries, posted by Louis de Leseleuc on Wed Jan 26 19:35:48 2011
|
Hello,
Can anyone please send me, or publicly provide, working Ubuntu 10.10 binaries (64-bit) for ELOG?
I have compiled and installed the program. While the core functionalities are OK, I have run into irritating bugs in filtering and config editing that are not present in the online demo (but are in my local demo and logbook).
Hence I suspect compilation to be the cause.
For the curious:
- Saving the config within ELOG scrambles the elog.conf file
Theme = default
Comment = Louis's Lab Book
Attributes = Project, Type, Category, Subject
after saving becomes
Them = defaultt
Commnt = Louiss's Lab Book
Attribute = Prroject, Type, Category, Subject
- In the Find page, drop-down filters for attributes are ignored, but text is searched
- In the threaded view, Quick filters "dissociate" posts and replies, so that all rows are now in reverse chronological order
Cheers!
Louis
|
Re: Working Ubuntu 10.10 ELOG binaries, posted by Louis de Leseleuc on Wed Jan 26 19:38:58 2011
|
Louis de Leseleuc wrote: |
Hello,
Can anyone please send me, or publicly provide, working Ubuntu 10.10 binaries (64-bit) for ELOG?
I have compiled and installed the program. While the core functionalities are OK, I have run into irritating bugs in filtering and config editing that are not present in the online demo (but are in my local demo and logbook).
Hence I suspect compilation to be the cause.
For the curious:
- Saving the config within ELOG scrambles the elog.conf file
Theme = default
Comment = Louis's Lab Book
Attributes = Project, Type, Category, Subject
after saving becomes
Them = defaultt
Commnt = Louiss's Lab Book
Attribute = Prroject, Type, Category, Subject
- In the Find page, drop-down filters for attributes are ignored, but text is searched
- In the threaded view, Quick filters "dissociate" posts and replies, so that all rows are now in reverse chronological order
Cheers!
Louis
|
Hmm actually that last bug is also present in the demo. Any hope of fixing that?
True, some posts may not match the filters, leaving replies "orphan". I suggest that any orphan reply be either attached to the nearest upper level, or if not possible, be styled as a post instead of a reply (no arrow or indent) so as not to mistake it for a reply to the message above.
The benefit would be to be able to follow threads matching certain categories. |
Wishlist: Roption, posted by David Pilgram on Thu Jan 20 18:51:53 2011
|
Hi Stefan,
Roptions, or Radio Buttons. Do you recall that on old
radios, if you gently pressed a button you could release whichever
button was already in, without selecting the new button; in other
words no selection made.
I'd like this same facility with elog. Now I know that it can be
done by (for example) in the config file preselecting one of the
selections on reply- or indeed one that does not exist to "clear" it,
but in this case that is not the route I'd want to take every time.
What I'd like is a (optional) button along with all the others, which
if you click on it, it will clear any selection for that particular Roption.
At present, once an Roption has been selected, it will persist in all
replies unless or until an alternative choice is made. Alternatively, if
no selection has been made, then there is no selection on the reply, either.
[Unless something in the elog.cfg file].
Regards,
David.
|
Re: Wishlist: Roption, posted by Stefan Ritt on Fri Jan 21 08:49:31 2011
|
> I'd like this same facility with elog. Now I know that it can be
> done by (for example) in the config file preselecting one of the
> selections on reply- or indeed one that does not exist to "clear" it,
> but in this case that is not the route I'd want to take every time.
What about defining an additional option "unspecified". So you have
Roptions attr = option1, option2, option3, none
Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does
not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want. |
Re: Wishlist: Roption, posted by David Pilgram on Fri Jan 21 11:28:02 2011
|
> > I'd like this same facility with elog. Now I know that it can be
> > done by (for example) in the config file preselecting one of the
> > selections on reply- or indeed one that does not exist to "clear" it,
> > but in this case that is not the route I'd want to take every time.
>
> What about defining an additional option "unspecified". So you have
>
> Roptions attr = option1, option2, option3, none
>
> Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does
> not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.
Hadn't realised the standard was written that way.
What you propose seems fine to me.
David. |
Modification aren't accepted, posted by bob on Wed Jan 19 16:03:38 2011
|
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob |
Re: Modification aren't accepted, posted by Stefan Ritt on Wed Jan 19 16:10:58 2011
|
bob wrote: |
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob
|
Not really, you are the first one reporting this issue. Just some thoughts:
- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
- Some write protection of elogd.cfg
- Do you have more than one server running at the same time and changing the wrong one's config?
- Stefan |
Re: Modification aren't accepted, posted by bob on Wed Jan 19 16:19:56 2011
|
Stefan Ritt wrote: |
bob wrote: |
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob
|
Not really, you are the first one reporting this issue. Just some thoughts:
- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
- Some write protection of elogd.cfg
- Do you have more than one server running at the same time and changing the wrong one's config?
- Stefan
|
>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)
>- Some write protection of elogd.cfg
no
- Do you have more than one server running at the same time and changing the wrong one's config?
i have one server with elog |
Re: Modification aren't accepted, posted by David Pilgram on Wed Jan 19 18:19:49 2011
|
bob wrote: |
Stefan Ritt wrote: |
bob wrote: |
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob
|
Not really, you are the first one reporting this issue. Just some thoughts:
- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
- Some write protection of elogd.cfg
- Do you have more than one server running at the same time and changing the wrong one's config?
- Stefan
|
>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)
>- Some write protection of elogd.cfg
no
- Do you have more than one server running at the same time and changing the wrong one's config?
i have one server with elog
|
Let me report when I see this behaviour.
If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,
but the running elog is still running with the old configuration. You have to restart elog for it to read the new config file and
use the new settings.
This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg
just after it has been saved.
The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,
and it's quickest to cut-and-paste, change the heading, create a new directory and restart elog.
This may be completely off what is being reported. |
Re: Modification aren't accepted, posted by Stefan Ritt on Thu Jan 20 08:51:13 2011
|
David Pilgram wrote: |
Let me report when I see this behaviour.
If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,
but the running elog is still running with the old configuration. You have to restart elog for it to read the new config file and
use the new settings.
This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg
just after it has been saved.
The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,
and it's quickest to cut-and-paste, change the heading, create a new directory and restart elog.
This may be completely off what is being reported.
|
Minor changes you do externally to the elogd.cfg file are reflected immediately under Windows (under Linux you have to send a HUP signal to the process to re-read the configuration). But if you make major changes like adding a new logbook, you have to restart elogd. |
Re: Modification aren't accepted, posted by bob on Thu Jan 20 13:49:22 2011
|
Stefan Ritt wrote: |
David Pilgram wrote: |
Let me report when I see this behaviour.
If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,
but the running elog is still running with the old configuration. You have to restart elog for it to read the new config file and
use the new settings.
This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg
just after it has been saved.
The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,
and it's quickest to cut-and-paste, change the heading, create a new directory and restart elog.
This may be completely off what is being reported.
|
Minor changes you do externally to the elogd.cfg file are reflected immediately under Windows (under Linux you have to send a HUP signal to the process to re-read the configuration). But if you make major changes like adding a new logbook, you have to restart elogd.
|
Yes, exactly!
I prefer to use the elog.cfg for change my config.
But, How do you do for restar the elogd ? with Unregister ELOG server service ?
Anyway, thanks for yours answers !
Bob
|
Re: Modification aren't accepted, posted by Stefan Ritt on Thu Jan 20 13:52:04 2011
|
bob wrote: |
Yes, exactly!
I prefer to use the elog.cfg for change my config.
But, How do you do for restar the elogd ? with Unregister ELOG server service ?
Anyway, thanks for yours answers !
Bob
|
When running as a windows service, you open a Command Prompt and enter:
net stop elogd
net start elogd
that will restart the service. |
New entries are not visible from other logbooks based on the same logbook dir through Subdir, posted by JacekK on Fri Jan 14 00:07:01 2011
|
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new
entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to
message index of every logbook based on the same data directory as the one, where the message was physically
created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek |
Re: New entries are not visible from other logbooks based on the same logbook dir through Subdir, posted by Stefan Ritt on Thu Jan 20 08:52:43 2011
|
JacekK wrote: |
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek
|
Well, having two logbooks in the same subdirectory was initially a planned feature but really never worked. I re-visited this issue and made it working in the current SVN version. So the next release will contain the fix. |
elog command creates always UTF-8 encoded entries, posted by Andreas Luedeke on Wed Jan 19 13:30:48 2011
|
If I create an entry via the web-interface, the defined encoding of the browser is used.
If I create an entry via "elog", it is always stored in UTF-8 encoding.
For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
The only solution I found was to convert the whole logbook to UTF-8 encoding:
define "charset=UTF-8" in elogd.cfg
iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german
Has anyone any idea why ISO8859-1 does not work for me?
Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-) |
Re: elog command creates always UTF-8 encoded entries, posted by Stefan Ritt on Wed Jan 19 14:47:15 2011
|
> If I create an entry via the web-interface, the defined encoding of the browser is used.
> If I create an entry via "elog", it is always stored in UTF-8 encoding.
> For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
> The only solution I found was to convert the whole logbook to UTF-8 encoding:
>
> define "charset=UTF-8" in elogd.cfg
> iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
> iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german
>
> Has anyone any idea why ISO8859-1 does not work for me?
>
> Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-)
I just tried it submitting to the Demo logbook:
https://midas.psi.ch/elogs/Linux+Demo/15
using some German Umlauts, and saw that it works fine. "elog" does not do any conversion, just submits the text as is.
If your text is ISO-8859-1 encoded, it will be submitted as such, and your browser will correctly display it. Have you
tried removing the "charset=UTF-8" from your elogd.cfg? |
Quick Filter does not work, posted by Michael Dannmeyer on Mon Jan 17 17:24:35 2011
|
Hello,
i have a logbook with the following parameters for the Attribute "Typ":
[TEST1]
Options Typ = SDB{2}, Qualifizierung B.12.S227{4}, Qualifizierung PRO/REP{3}, Dokument zur Qualifizierung{2}, Prüf- und Wartungsvorschrift{2}, SOP ohne Change Request{2}, SOP mit Change Request{1}, Validierung PRO/REP{3}, Dokument zur Verifizierung{2}, Überprüfung und Verlängerung{2}, Spec.Sheet{2}, CoA (sofern nicht LIMS){2}, Änderungen Tg4.B07{5}, OOS (Plan/Bericht){3}, Transfer PRO/REP{3}, Studie PRO/REP{3}, Studie ohne Plan{2}, Anderes{2}
Quick filter = Date, Typ
If i choose an Entry from the "Typ" Quick Filter it shows me that there are no entries in the logbook but I'm shure that there are entries.
Can you please help? I cannot see what's wrong.
Best Regards
Michael
|
Re: Quick Filter does not work, posted by Stefan Ritt on Wed Jan 19 08:44:28 2011
|
Michael Dannmeyer wrote: |
Hello,
i have a logbook with the following parameters for the Attribute "Typ":
[TEST1]
Options Typ = SDB{2}, Qualifizierung B.12.S227{4}, Qualifizierung PRO/REP{3}, Dokument zur Qualifizierung{2}, Prüf- und Wartungsvorschrift{2}, SOP ohne Change Request{2}, SOP mit Change Request{1}, Validierung PRO/REP{3}, Dokument zur Verifizierung{2}, Überprüfung und Verlängerung{2}, Spec.Sheet{2}, CoA (sofern nicht LIMS){2}, Änderungen Tg4.B07{5}, OOS (Plan/Bericht){3}, Transfer PRO/REP{3}, Studie PRO/REP{3}, Studie ohne Plan{2}, Anderes{2}
Quick filter = Date, Typ
If i choose an Entry from the "Typ" Quick Filter it shows me that there are no entries in the logbook but I'm shure that there are entries.
Can you please help? I cannot see what's wrong.
Best Regards
Michael
|
I tried your configuration and it worked fine:
So can you try version 2.8.1 if that makes any difference. If not, can you send me your complete elogd.cfg, so that I can reproduce your problem.
- Stefan |
Re: Quick Filter does not work, posted by Michael Dannmeyer on Wed Jan 19 09:19:53 2011
|
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Hello,
i have a logbook with the following parameters for the Attribute "Typ":
[TEST1]
Options Typ = SDB{2}, Qualifizierung B.12.S227{4}, Qualifizierung PRO/REP{3}, Dokument zur Qualifizierung{2}, Prüf- und Wartungsvorschrift{2}, SOP ohne Change Request{2}, SOP mit Change Request{1}, Validierung PRO/REP{3}, Dokument zur Verifizierung{2}, Überprüfung und Verlängerung{2}, Spec.Sheet{2}, CoA (sofern nicht LIMS){2}, Änderungen Tg4.B07{5}, OOS (Plan/Bericht){3}, Transfer PRO/REP{3}, Studie PRO/REP{3}, Studie ohne Plan{2}, Anderes{2}
Quick filter = Date, Typ
If i choose an Entry from the "Typ" Quick Filter it shows me that there are no entries in the logbook but I'm shure that there are entries.
Can you please help? I cannot see what's wrong.
Best Regards
Michael
|
I tried your configuration and it worked fine:
So can you try version 2.8.1 if that makes any difference. If not, can you send me your complete elogd.cfg, so that I can reproduce your problem.
- Stefan
|
I installed 2.81 (Elog-latest) but this Version did not work. I got Error 193: %1 is not a valid Win32 Application as I tried to start the service. So i will sent you the complete elogd.cfg via Mail.
Best regards
Michael |
Found some spelling errors in eloglang.german, posted by Andreas Luedeke on Thu Jan 13 10:07:17 2011
|
corrected file is attached |
Multiple Insances of eLog on the same machine, posted by Behdad D on Fri Jan 7 05:45:41 2011
|
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad. |
Re: Multiple Insances of eLog on the same machine, posted by Stefan Ritt on Fri Jan 7 08:37:49 2011
|
Behdad D wrote: |
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad.
|
Sure. Just start with one subdirectory for each instance with a separate elogd.cfg file, where you specify a different port. Note however that there is also the concept of "top groups" (see documentation) which lets a single instance of elog look like several independent installations. |
Re: Multiple Insances of eLog on the same machine, posted by Behdad D on Sun Jan 9 07:04:00 2011
|
Stefan Ritt wrote: |
Behdad D wrote: |
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad.
|
Sure. Just start with one subdirectory for each instance with a separate elogd.cfg file, where you specify a different port. Note however that there is also the concept of "top groups" (see documentation) which lets a single instance of elog look like several independent installations.
|
Great. Thanks Stefan.
I also am already using the top groups. This is just to totally separate my work and home elog.....I have to admit I am really an elog addict. 
This elog and the idea behind it is absolutely brilliant. Very useful, easy to maintain, migrate, configure, easy to use, versatile, etc... Good on you all.
Cheers,
Behdad. |
|