|
Demo
Discussion
|
Forum
Config Examples
Contributions
Vulnerabilities
|
Discussion forum about ELOG |
Not logged in |
|
|
|
Message ID: 374
Entry time: Wed Jun 18 14:50:23 2003
Reply to this: 375
|
|
Category: |
Info |
OS: |
Linux | Windows | Mac OSX |
ELOG Version: |
|
|
Subject: |
logboog for new project |
|
|
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. |