ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
702
|
Wed Sep 15 04:08:46 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 2.5.4 | Re: text display of ascii files not a good idea | > So a configurable size limit seems appropriate, from which on
> only 'Display attachment' is displayed. And/Or, for files
> exceeding this limit, the first N (new config option) lines could be displayed.
Ok, I changed elogd such that only the first 1000 lines of inline attachments are
displayed, with a note of how many lines are truncated. By clicking on the attachment
name, one can still download the complete attachment. I guess the number of lines do
not have to be configurable, but if someone is not happy with the 1000 lines that could
be added. |
68813
|
Tue Jun 5 10:12:06 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 3.1.1 | Re: text area height | Have you tried
Message height = ...
unit is number of text lines.
Stefan
Giuseppe Cucinotta wrote: |
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe
|
|
68815
|
Tue Jun 5 15:06:18 2018 |
| Giuseppe Cucinotta | giuseppe.cucinotta@unifi.it | Info | Linux | 3.1.1 | Re: text area height | I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...
What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.
Beppe
Stefan Ritt wrote: |
Have you tried
Message height = ...
unit is number of text lines.
Stefan
Giuseppe Cucinotta wrote: |
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe
|
|
|
Attachment 1: fig1.png
|
|
Attachment 2: fig2.png
|
|
68816
|
Tue Jun 5 21:37:26 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 3.1.1 | Re: text area height | The message height option only works if you select either "ELCode" or "plain" for encoding (this can also be made as default in the config file). For the HTML editor, the size is set internally and I don't have any influenc on it.
Stefan
Giuseppe Cucinotta wrote: |
I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...
What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.
Beppe
Stefan Ritt wrote: |
Have you tried
Message height = ...
unit is number of text lines.
Stefan
Giuseppe Cucinotta wrote: |
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe
|
|
|
|
69182
|
Fri Jul 31 08:34:35 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4 | Re: testing the client: unclear it worked | The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
Jose Caballero wrote: |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
69218
|
Mon Sep 14 15:40:02 2020 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | Re: testing the client: unclear it worked | Sorry for the late reply. I didn't get email notification about an answer to my question :)
Actually, I just wrote <hostname> and so on for privacy. In my attempt, they have real values.
And yet, I got as result: "Message successfully transmitted, ID=-1".
Follow up question: do I really need to install everything even though I only want the client? Or is there somewhere a package just with the client code?
Thanks
Jose
Stefan Ritt wrote: |
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
Jose Caballero wrote: |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
|
2323
|
Sat Oct 6 15:44:51 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.5-1890 | Re: testing for the limit of the elog database |
Arno Teunisse wrote: | So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
Yes. The rule of thumb is that currently elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow. I have already in my to-do list the task to improve the performance for large databases, and I have a rough idea where the bottleneck is, but I pushed the priority low because not many people have large databases right now (but it might change in the future). How many entries do you have? (It's not the size of the entries, but the number!) |
2324
|
Sat Oct 6 15:56:13 2007 |
| Arno Teunisse | A.Teeling3@chello.nl | Question | Windows | 2.6.5-1890 | Re: testing for the limit of the elog database |
Stefan Ritt wrote: |
Arno Teunisse wrote: | So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
Yes. The rule of thumb is that currently elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow. I have already in my to-do list the task to improve the performance for large databases, and I have a rough idea where the bottleneck is, but I pushed the priority low because not many people have large databases right now (but it might change in the future). How many entries do you have? (It's not the size of the entries, but the number!) |
That's a quick answer. I just was testing. I'm trying to introduce elog at work, so i'm not having an actual database in production. In the test database I had 125386 entries. Two column: "Customers name" and "documents".
By the way : my email address has changed : how do I change that ??
Thanks |
|