rhis logbook, posted by Etienne Van Caillie on Wed Jun 4 10:47:36 2003
|
I suggest to add an attributes like OS
MOptions OS = linux, windows2000, windowsXP¨, windows2003
to indicate on which version we are speaking |
Re: syntax highligting for elog.cfg with ULTRAEDIT, posted by Stefan Ritt on Wed Jun 4 15:24:42 2003
|
> i put the last version on this link
> http://public.mba.be/download/u-edit-elog-syntax.txt
If you don't mind I added the file to this message. |
Re: bug in cfg file, posted by Stefan Ritt on Wed Jun 4 15:26:15 2003
|
> When you take the elogd.cfg file and the menu commands = <list> and guest
> menu commands = <list>, the config menu for edit the elogd.cfg stops
> working, yet if I change the URL manually, I can still get to the file and
> the menus do not change. If I delete all menu commands, then all works
> without errors, yet the menus do not match default.
Has just been fixed. Available under CVS and soon in 2.3.8. |
Re: Loging user's activity, posted by Stefan Ritt on Wed Jun 4 15:30:12 2003
|
> I was wondering if there is a way to have a more detailed log of users'
> activities?
> Current Logfile = <file> gives a good base for information about
> logins/access to 'protected' logbooks.
>
> What we would like to have is information about when a user reads an ELOG
> entry (to be able to determine the reaction/response time).
>
> For instance the LOG could look sg like this:
> %%user %%datetime %%logbook %%record read/edit/new/delete
Very nice idea, I put it on the wishlist. |
Re: HTML page formating, posted by Stefan Ritt on Wed Jun 4 15:52:52 2003
|
Thank you very much for your request, well motivated and described. I hope I
will soon find time to impelment this. |
Re: syntax highligting for elog.cfg with ULTRAEDIT, posted by Etienne Van Caillie on Wed Jun 4 17:44:40 2003
|
> > 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 |
Re: HTML page formating, posted by Stefan Ritt on Fri Jul 4 20:46:16 2003
|
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" |
Re: HTML page formating, posted by Tomas Rudolf on Fri Jul 4 21:26:03 2003
|
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" |