Re: Including the text in the CSV export, posted by Stefan Ritt on Tue Mar 1 13:39:09 2005
|
> Is there any way to include the text of a log message in the CSV export?
> Anyway to include a pointer to the attachment?
The text of a log message is usually several lines long. To my knowledge, CSV
only allows single line values, that's why I excluded the text field from the
CSV export. This is different in the XML export, which supports multi-line
values. If you teach me however how multi-line values can be represented in
CSV format, I could easily add that.
As for the attachment, do you just need a name, or a URL back to the logbook?
Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
or in HTML form like <a href="http:/...">attachment</a> ? |
Re: length of fields, posted by Stefan Ritt on Wed Mar 2 15:00:04 2005
|
> 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 |
Re: boundary problem with Type lists display, posted by Stefan Ritt on Wed Mar 2 15:19:56 2005
|
> using:
> Display mode = threaded
> List display = Subject, Type, Author, Date
>
> in the config file (omitting "ID" then) rise the bug
>
> ie, an unneeded "," is displayed after the "supposed to be printed" ID
Fixed in CVS revision 1.574 |
Re: HTML 4.1 transitional validation fails, posted by Stefan Ritt on Wed Mar 2 17:31:33 2005
|
> > I tried to substitute avery occurrence of hard coded "&" with "&" but it does
> > not do the job at all ... infact the first time the HTML code is ok, but
> > following a link let the browser to automatically decode html entities .. and
> > everything turns wrong again ... maybe the encoding should be done in
> > printing-to-the-browser-time ..
That won't help, since the 'Start page = ...' string is used for redirection (outside
of any HTML). The '&' thing should only occur inside the HMTL text.
I changed elogd.c to encode things properly, but I'm not sure if I covered all
occurences. Can you try release 1.576 if it works correctly? |
Re: Non clickable column, posted by Stefan Ritt on Fri Mar 4 10:50:57 2005
|
> 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? |
Re: Compilation flag/file question, posted by Stefan Ritt on Tue Mar 8 17:34:05 2005
|
> 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 |
Re: length of fields, posted by Stefan Ritt on Tue Mar 8 20:28:49 2005
|
> 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. |
Re: 2 Extendable options when created new entries, posted by Stefan Ritt on Mon Mar 14 21:00:57 2005
|
I fixed this problem in revision 1.586. It will be contained in the next release. |