ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
980
|
Wed Mar 9 10:17:51 2005 |
| T. Ribbrock | emgaron@gmx.net | | | | Trying to get "Format <attribute>" to work |
I am currently trying to get some attributes into one line in my logbook,
with some others on a line of their own (this is on the single message page)
- pretty much like in this forum.
I searched through the forum and the config examples and found
elog:571 as well as elog:Config+Examples/4, but I cannot get it
to work.
In the forum, the "Subject:" line is on its own line and fills the whole
line, which is what I want. In my logbook, the equivalent attribute does
stand on its own line, but the 'value' only fills the space of the second
column (i.e., if it was in this forum, the 'value' of "Subject" would be the
same width as the icon above it and the rest of the line just blank).
As far as I can see, I'm using the "Format <attribute>=1" statements in the
same way as in the example - and when I compare the resulting HTML, it also
looks the same. I did notice, however, that you use different CSS classes
for "Subject" and its value. Hence my question: To get "Subject" and its
value to stretch over the full line, is there some fancy CSS footwork
involved? I was not able to find the CSS file for this forum among the
configuration examples - maybe you could add it?
Thanks in advance! |
979
|
Tue Mar 8 20:28:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: length of fields |
> Is it possible to get around this problem by having more then one main text field
> per record?
No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so. |
978
|
Tue Mar 8 19:23:14 2005 |
| Benjamin Brown | brownbr@hotmail.com | Question | Linux | 2.5.7 | Re: Compilation flag/file question |
> > If I want to go to the latest CVS release, what files do I have to compile
> > along with the elogd.c file? Also, do I need to use any special gcc flags
> > for the compilation? Thanks.
>
> You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well
>
> http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile
Worked like a charm. Thanks again. |
977
|
Tue Mar 8 17:34:05 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.7 | Re: Compilation flag/file question |
> If I want to go to the latest CVS release, what files do I have to compile
> along with the elogd.c file? Also, do I need to use any special gcc flags
> for the compilation? Thanks.
You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well
http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile |
976
|
Tue Mar 8 17:31:55 2005 |
| Benjamin Brown | brownbr@hotmail.com | Question | Linux | 2.5.7 | Compilation flag/file question |
If I want to go to the latest CVS release, what files do I have to compile
along with the elogd.c file? Also, do I need to use any special gcc flags
for the compilation? Thanks. |
975
|
Tue Mar 8 13:16:14 2005 |
| Paul Harrington | paul.harrington@oup.com | Question | All | | Re: length of fields |
The reason for the earlier question is that we are trying to use Elog to store
data in a form we'd need to store more 1500 characters in more than one field.
Is it possible to get around this problem by having more then one main text field
per record?
thanks
Paul
> > > When creating/updating entries in elog, excluding the main text field are
> > > there any limits on the size of the other fields?
> >
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> >
> > - Stefan
>
> Thanks. Thats useful to know.
>
> Paul |
974
|
Mon Mar 7 16:05:22 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | rev. 1.51 | Display <attribute> do erroneously encoded |
Display subject = <b>$subject</b>
is printed to the browser encoded, so that it is diplayed as is.. |
973
|
Fri Mar 4 10:59:51 2005 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.5.7-1 | Re: Non clickable column |
> > Is there any solution to obtain an non-clickable column ?
> > For example here : http://midas.psi.ch/elogs/Config+Examples/ what should
> > I do to obtain the data of the Category column non clickable?
> > I don't have find a solution in the Syntax of elogd.cfg
> > (http://midas.psi.ch/elog/config.html)
>
> What do you mean by "non-clickable column"? The column header for sorting, or
> the column contents which brings you to the single entry page? For both of
> them, there is no way right now to obtain that. Why do you want it?
I talk about the column contents. In fact on ELOG, we store password so its
more easyer to click twice on it to select them and after to copy them instead
of select from right to left the password and to try to copy them. The HMTL
link gave problem, its more hard to copy data from HTML link than an normal TXT.
A little hard to explain sorry for my mistakes and explication I'm French :o). |