Hi to all,

I've prepared a new Debian package.  This version will probably be the one
which you'll find in Sarge/stable.

There are some invasive changes in this version which call for a serious
test.  In accordance with a suggestion, I've changed the configuration
mechanism.  For details, please read the NEWS.Debian file attached.

Could the Debian users who follow this forum test it and give some feedback?
You can download the package from the following link:

  http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb

Thanks in advance for your participation,

> Hi to all,
> 
> I've prepared a new Debian package.  This version will probably be the one
> which you'll find in Sarge/stable.
> 
> There are some invasive changes in this version which call for a serious
> test.  In accordance with a suggestion, I've changed the configuration
> mechanism.  For details, please read the NEWS.Debian file attached.
> 
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
> 
>   http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
> 
> Thanks in advance for your participation,

It seems to work nice to me.
Just another suggestion: I think it would be better to insert a commented out
example for all allowed parameters in the distributed  /etc/default/elog

nice work :-)

> It seems to work nice to me.
> Just another suggestion: I think it would be better to insert a commented out
> example for all allowed parameters in the distributed  /etc/default/elog

Thanks for the test.  Please note that, /etc/default/elog is partially auto
created during the installation.  All options except PIDFILE and CONFFILE are
currently listed (as configured or commented out).  If you didn't see these
options (after the update), there must be a problem.   Did you mean the lack of
PIDFILE and CONFFILE in the default file?

> > It seems to work nice to me.
> > Just another suggestion: I think it would be better to insert a commented out
> > example for all allowed parameters in the distributed  /etc/default/elog
> 
> Thanks for the test.  Please note that, /etc/default/elog is partially auto
> created during the installation.  All options except PIDFILE and CONFFILE are
> currently listed (as configured or commented out).  If you didn't see these
> options (after the update), there must be a problem.   Did you mean the lack of
> PIDFILE and CONFFILE in the default file?

no, my bad (it seems :-P) .. I re-installed the package now on my laptop and seems
to work fine... maybe I have swapped the diff result when installed yesterday.

Making tests I found another problem, her is the report:

####
root@emc2:/home/albert# apt-get remove elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti saranno RIMOSSI:
  elog
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
È necessario prendere 0B di archivi.
Dopo l'estrazione, verranno liberati 2444kB di spazio su disco.
Continuare? [S/n]
(Lettura del database ... 152033 file e directory attualmente installati.)
Rimuovo elog ...
Stopping ELOG daemon: elogd.
root@emc2:/home/albert# rm /etc/default/elog
rm: rimuovere regular file `/etc/default/elog'? y
root@emc2:/home/albert# apt-get install elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti NUOVI (NEW) saranno installati:
  elog
0 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prendere 0B/530kB di archivi.
Dopo l'estrazione, verranno occupati 2444kB di spazio su disco.
Selezionato il pacchetto elog, che non lo era.
(Lettura del database ... 151926 file e directory attualmente installati.)
Spacchetto elog (da .../elog_2.5.8+r1592-1_i386.deb) ...
Configuro elog (2.5.8+r1592-1) ...
cat: /etc/default/elog: No such file or directory
Starting ELOG daemon: elogd.
####


So, removing an existing elog (not purging) and installing again raise the error.
Why installation creates the default/elog file only the first time ?  I think it
shoud do the job everytime (and everytime ask the user is there is a diff to be
checked)

> Hi to all,
> 
> I've prepared a new Debian package.  This version will probably be the one
> which you'll find in Sarge/stable.
> 
> There are some invasive changes in this version which call for a serious
> test.  In accordance with a suggestion, I've changed the configuration
> mechanism.  For details, please read the NEWS.Debian file attached.
> 
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
> 
>   http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
> 
> Thanks in advance for your participation,

btw, what about in including in default/elog also a voice for the "-x" switch ??

It is a security related thing and may be passed only on the command line to the
daemon, so it should be governed by the system elog admin.

I would like to increase the spacing between 'MOptions' choices. I have
created a new theme and have been playing with the CSS stylesheet. But can't
find how to increase this spacing. Having lots of fun otherwise!

Tks,

mark

> I would like to increase the spacing between 'MOptions' choices. I have
> created a new theme and have been playing with the CSS stylesheet. But can't
> find how to increase this spacing. Having lots of fun otherwise!

Intersting question (meaning: I don't have an answer... (;-) )

The class which applies there is "attribvalue". You can increase the padding for
that class, but that only increases the space between all options and the cell
border, but not between them. I could put each MOption in a separate cell of a
subtable. Then one could increase the padding between them, but the layout would
be fixed, meaning that they are always left-to-right. As you can see in this
forum, the MOptions nicely place below each other if the screen is too narrow.
This functionality would be lost.

Maybe someone else has a clever solution?

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

> 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

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

> 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?

> > 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).

> 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.

> > 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 subject = <b>$subject</b>

is printed to the browser encoded, so that it is diplayed as is..

> 
> 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.

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 :)

I fixed this problem in revision 1.586. It will be contained in the next release.

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!

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

> 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

> > 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

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

> 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.