Asing a user to an log, posted by Rob de Bruin on Fri Mar 18 11:14:58 2005
|
Hello,
I'm looking for an option to attach a user to a log?
For example:
Rob is making the log, and whant's to dedicate the log to a stagaire,
the stagiare recieves an E-mail so that he can do the job?
Bud we all want recieve the mail bud the stagiare see's that the job is for
him.
Is there a solution for it?
Best regards Rob de Bruin |
Re: Asing a user to an log, posted by Stefan Ritt on Fri Mar 18 13:36:19 2005
|
> I'm looking for an option to attach a user to a log?
>
> For example:
>
> Rob is making the log, and whant's to dedicate the log to a stagaire,
> the stagiare recieves an E-mail so that he can do the job?
>
> Bud we all want recieve the mail bud the stagiare see's that the job is for
> him.
Maybe use an attribute for that?
Like
Attributes = Author, ..., stagaire
Options stagaire = Jim, Joe, ...
So Rob can select a stagaire from the list, and the email contains this name.
- Stefan |
Non clickable column, posted by Alex H on Fri Mar 4 10:16:04 2005
|
Hi,
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)
Thanks a lot |
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: Non clickable column, posted by Alex H on Fri Mar 4 10:59:51 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?
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). |
Re: Non clickable column, posted by Stefan Ritt on Mon Mar 14 21:56:15 2005
|
> 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).
I added a new option "Link display = ...", with which you can restrict the number of
attribues which gets a HTML link. If you put
Link display = ID, Author
then only the ID column and the colum with the Author are shown as HTML links, all
other are shown as simple text.
The new version is under CVS. This option will be included in the next release. |
Re: Non clickable column, posted by Alex H on Tue Mar 15 14:11:48 2005
|
> > 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).
>
> I added a new option "Link display = ...", with which you can restrict the number of
> attribues which gets a HTML link. If you put
>
> Link display = ID, Author
>
> then only the ID column and the colum with the Author are shown as HTML links, all
> other are shown as simple text.
>
> The new version is under CVS. This option will be included in the next release.
Great news :) !
thanks a lot ! |
Display <attribute> do erroneously encoded, posted by Emiliano Gabrielli on Mon Mar 7 16:05:22 2005
|
Display subject = <b>$subject</b>
is printed to the browser encoded, so that it is diplayed as is.. |
Re: Display <attribute> do erroneously encoded, posted by Stefan Ritt on Mon Mar 14 21:11:11 2005
|
>
> Display subject = <b>$subject</b>
>
> is printed to the browser encoded, so that it is diplayed as is..
I fixed that in revision 1.587. Note however that you should do the formatting
of attributes better using the CSS functionality, since it gives you more
possibilities. See for example the subject of this forum, which has it's own
CSS class "subjname", which has a larger font size. You select your own class like
Format Subject = 0, subjname, subjvalue
in the configuration file. Then add the classes into the CSS file.
Now elog shows each attribute which contains a "<b>" encoded (as HTML). But if you
want to write a subject line like "For bold use <b> in HTML", then the "<b>"
triggers the HTML display, so it is not written as is, which is not what you want in
that case. Since there is no switch "Submit as HTML text" for the attributes, it is
hard for elog to "guess" if you want HTML encoded or not. |
2 Extendable options when created new entries, posted by Alex H on Thu Mar 3 16:46:26 2005
|
Hello,
I try to have two Extendable options : Client and Equipment
so here is the line in my elogd.cfg
Extendable options = Client, Equipment
When I create a new entrie, I have the 2 scroll menus(Client and
Equipment) and the 2 buttons(Client and Equipment) but i can't create 2
news entries, i must create one for client, after I submit, I edit one
more time and add a new equipement. Is there a solution for this?
Thanks a lot and sorry for mistakes or problem of comprehension i'am
french :) |
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. |
Trying to get "Format <attribute>" to work, posted by T. Ribbrock on Wed Mar 9 10:17:51 2005
|
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! |
length of fields, posted by Paul Harrington on Wed Feb 23 13:02:59 2005
|
When creating/updating entries in elog, excluding the main text field are
there any limits on the size of the other fields?
many thanks
Paul |
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: length of fields, posted by Paul Harrington on Thu Mar 3 10:21:21 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
Thanks. Thats useful to know.
Paul |
Re: length of fields, posted by Paul Harrington on Tue Mar 8 13:16:14 2005
|
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 |
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. |
Compilation flag/file question, posted by Benjamin Brown on Tue Mar 8 17:31:55 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. |
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: Compilation flag/file question, posted by Benjamin Brown on Tue Mar 8 19:23:14 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
Worked like a charm. Thanks again. |
boundary problem with Type lists display, posted by Emiliano Gabrielli on Wed Feb 23 18:07:24 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 |
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 |