ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69174
|
Sat Jul 18 17:19:31 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Re: Expanding column width when viewing in Summary mode | Hi Stefan,
Thanks for your prompt follow up. I did try commenting of the width statement for listtitle2 and also reducing it to 40% but it did not work. I restarted elogd daemon and I don't see the columns changing. I also tried putting a percentage number (40%) for listtitle1 just to try and no change either. Appreciate your help.
Thanks.
Illam
Stefan Ritt wrote: |
You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
Illam Pakkirisamy wrote: |
Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam
|
|
|
Draft
|
Sat Jul 18 17:18:54 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Re: Expanding column width when viewing in Summary mode |
Stefan Ritt wrote: |
You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
Illam Pakkirisamy wrote: |
Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam
|
|
|
69172
|
Fri Jul 17 09:18:18 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V3.1.4-a04 | Re: Expanding column width when viewing in Summary mode | You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
Illam Pakkirisamy wrote: |
Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam
|
|
69171
|
Thu Jul 16 23:29:15 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Expanding column width when viewing in Summary mode | Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam |
69170
|
Thu Jul 16 23:26:43 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Expanding column width when viewing in Summary mode | Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam |
69169
|
Tue Jul 7 11:22:45 2020 |
| Janusz Szuba | janusz.szuba@xfel.eu | Bug report | Linux | 3.1.4 | Re: bug in elog.spec | Thanks for the answer, I will try with your specfile
best
Janusz
Laurent Jean-Rigaud wrote: |
Hi,
You rights, CFLAGS should not be in specfile to take care of distrib env.
Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.
With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,
rpm -i elog-.....src.rpm
rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec
I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.
Bye,
Laurent
Janusz Szuba wrote: |
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz
|
|
|
69168
|
Mon Jul 6 20:19:21 2020 |
| Laurent Jean-Rigaud | lollspam@free.fr | Bug report | Linux | 3.1.4 | Re: bug in elog.spec | Hi,
You rights, CFLAGS should not be in specfile to take care of distrib env.
Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.
With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,
rpm -i elog-.....src.rpm
rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec
I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.
Bye,
Laurent
Janusz Szuba wrote: |
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz
|
|
69167
|
Mon Jul 6 19:09:48 2020 |
| Janusz Szuba | janusz.szuba@xfel.eu | Bug report | Linux | 3.1.4 | bug in elog.spec | Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz |
|