> > i put the last version on this link
> > http://public.mba.be/demo/elog/u-edit-elog-syntax.txt
> 
> If you don't mind I added the file to this message.

surely not but as I put some new command each time you update elog :)
it's easy for us to put on on webserver
but for each update I ll send the new version

we develop some improvement to elog and modify the C source
to adapt some internal improvement.

1. shellonsubmit command : give the possibility to execute external program
from elog by sending specific parameter (user/logbook/message ID)

2. elog log file in xml format : give a better view on what happens with 
users see attachments easy to push the files to excel or sql database.

3. synchronisation to mySql or SQL server through perl routine and the 
shellonsubmit command
this will push any new/edit/delete command in sql server so we keep a full 
historic off all transaction in ELOG

4. sms gateway : from elog entry we send sms message throught internet 
gateway (perl routine)

If somebody has good experience in C and Perl I suggest to contact me to 
improve this wonderfull product
Thank Stephan

other projet : 
we use a logbook from our external phone call

from our telephone connected to RS232 and/or TAPI interface we keep the 
phone number and try to find the name from sql server : if found 
we want to push an automatic entry in elog and fill specific field like 
name/contact/last phone call....


I will ask to Stephan Ritt what's the best way to include our routine in 
his standard source ?

could we create a specific logbook for the wishlist
in elog/contribution may be some parameters for the actual status of the 
project ? 

SQL : 
for our sql link we have a probleme as elog re use id when deleted
we must generate an unique ID for each elog CREATE 
and a version# field automaticly incremented after each update.
This must be implemented in ELOG source.

> 1. shellonsubmit command : give the possibility to execute external 
> program from elog by sending specific parameter (user/logbook/message ID)
> 
> 2. elog log file in xml format : give a better view on what happens with 
> users see attachments easy to push the files to excel or sql database.

I'm happy to include these functions in the source code, please send them 
to me.

> 3. synchronisation to mySql or SQL server through perl routine and the 
> shellonsubmit command
> this will push any new/edit/delete command in sql server so we keep a 
> full historic off all transaction in ELOG

Can you please put this perl routine into the "Contributions" section

> 4. sms gateway : from elog entry we send sms message throught internet 
> gateway (perl routine)

Same as above.

> other projet : 
> we use a logbook from our external phone call
> 
> from our telephone connected to RS232 and/or TAPI interface we keep the 
> phone number and try to find the name from sql server : if found 
> we want to push an automatic entry in elog and fill specific field like 
> name/contact/last phone call....
> 
> I will ask to Stephan Ritt what's the best way to include our routine in 
> his standard source ?

As I said, put the perl programs into the "Contributions" logbook, send the 
C source code modifications to me.

> could we create a specific logbook for the wishlist
> in elog/contribution may be some parameters for the actual status of the 
> project ? 

Good idea, will do so.

Tomas send you by mail the source files and documentation in English



> > 1. shellonsubmit command : give the possibility to execute external 
> > program from elog by sending specific parameter (user/logbook/message ID)
> > 
> > 2. elog log file in xml format : give a better view on what happens with 
> > users see attachments easy to push the files to excel or sql database.
> 
> I'm happy to include these functions in the source code, please send them 
> to me.
> 
> > 3. synchronisation to mySql or SQL server through perl routine and the 
> > shellonsubmit command
> > this will push any new/edit/delete command in sql server so we keep a 
> > full historic off all transaction in ELOG
> 
> Can you please put this perl routine into the "Contributions" section
> 
> > 4. sms gateway : from elog entry we send sms message throught internet 
> > gateway (perl routine)
> 
> Same as above.
> 
> > other projet : 
> > we use a logbook from our external phone call
> > 
> > from our telephone connected to RS232 and/or TAPI interface we keep the 
> > phone number and try to find the name from sql server : if found 
> > we want to push an automatic entry in elog and fill specific field like 
> > name/contact/last phone call....
> > 
> > I will ask to Stephan Ritt what's the best way to include our routine in 
> > his standard source ?
> 
> As I said, put the perl programs into the "Contributions" logbook, send 
the 
> C source code modifications to me.
> 
> > could we create a specific logbook for the wishlist
> > in elog/contribution may be some parameters for the actual status of the 
> > project ? 
> 
> Good idea, will do so.

I implemented your request. The syntax is:

Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>

<flags>
  Sum of following values:
    1: Display attribute in same line as previous attribute
    2: Display radio buttons or check boxes in separate lines (if applicable)

<css_class_name>,<css_class_value> 
  Cascading Style Sheet class names used for cells containing attribute name
  or value, respectively. The classes must be defined in the style sheet file 
  (usually themes/default/default.css)

<width>> 
  Width of the text entry field in characters

<size> 
  Maximum number of characters allowed. 

Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
ommitted, so specifying for example only the flags is possible.

In order to have several attributes in one line, each line is now a separate 
table. This requires adjustment of the CSS class "attribname". Best you use 
the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).

You can compare the two different approaches (one attribute per line/multiple 
attributes per line) in this forum and the "archive" logbook. The "subject" 
field in this forum also uses a different style class.

Note that if you upgrade to the current CVS version 
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
have to change following options in your elogd.cfg:

- The style sheet must contain the new class "attribhead"
- "Email message body" has been replaces by "Email format"
- "Filtered browsing" is now off by default
- Locking (during editing of messages) is disabled by default, and enabled 
by "Use lock = 1"

Very interesting, indeed!
Thank you very much for the implementation. I believe this is a big step ahead 
in terms of ELOG screen formating (and therefore easier/more ergonomic 
dataentry/reading).

We will test your modifications as soon as you make a new release.

Tomas


> I implemented your request. The syntax is:
> 
> Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>
> 
> <flags>
>   Sum of following values:
>     1: Display attribute in same line as previous attribute
>     2: Display radio buttons or check boxes in separate lines (if applicable)
> 
> <css_class_name>,<css_class_value> 
>   Cascading Style Sheet class names used for cells containing attribute name
>   or value, respectively. The classes must be defined in the style sheet file 
>   (usually themes/default/default.css)
> 
> <width>> 
>   Width of the text entry field in characters
> 
> <size> 
>   Maximum number of characters allowed. 
> 
> Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
> ommitted, so specifying for example only the flags is possible.
> 
> In order to have several attributes in one line, each line is now a separate 
> table. This requires adjustment of the CSS class "attribname". Best you use 
> the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).
> 
> You can compare the two different approaches (one attribute per line/multiple 
> attributes per line) in this forum and the "archive" logbook. The "subject" 
> field in this forum also uses a different style class.
> 
> Note that if you upgrade to the current CVS version 
> (http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
> have to change following options in your elogd.cfg:
> 
> - The style sheet must contain the new class "attribhead"
> - "Email message body" has been replaces by "Email format"
> - "Filtered browsing" is now off by default
> - Locking (during editing of messages) is disabled by default, and enabled 
> by "Use lock = 1"

Contribution available for all who wants to make SKIN for ELOG!

You are invited to benefit from this free info!

Just click on the "Contributions" tab to find the info (look for ID6).

Or... goto          http://midas.psi.ch/elogdemo/Contributions/6

> i work on Windows2000
> 
> part of my elog.cfg:
> 
>     Passwort file = c:\elog\passwd.txt
>     Self register = 1
>     Guest user commands = config, admin, logout
> 
> file system:
> 
>     - i created an emty file with name passwd.txt
> 
> problem:
> 
>     - if i use the link "Register as new user" on login, it does not work.
>     - if i login as guest user and choose the menu config, it only 
>     display  the attributes Login_name, Full_name and Email.    
>     So i kann not create user.
> 
> what should i do ?
> what are my mistakes ?
> 
> Can you attache as sample password file ?

Dear Friend!,

Only mistake in your file .cfg is   spell mistake "Passwort" in "Passwort 
file = c:\elog\passwd.txt" line. It should "Password file" t=d. 

try some thing like below,

[Log]
Theme = default
Comment = Financial Accounting Bug posting 
Attributes = Resource, Project Name, Task Desc, SDT, EEDT, ACDT, Percent WC, 
Status 
Options Type = Masters, Transactions, Reports
Options Category = Bug, New Feature, Client Requirement, Change
Required Attributes = Author, Type, Bug
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Password file =D:\Program Files\ELOG\logpwd.txt
;Self register = 0
Self register = 1

Admin user =sridhar
Menu commands = Back, Login, New, Edit, config, Delete, Reply, Find, Help, 
Logout
Guest user commands = config, admin, Login, logout