> > add this file in ultraedit
> > UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
> > I hope this will help you...
> 
> Have you maybe forgotten the attachment to this message?

yes :s

i put the last version on this link
http://public.mba.be/demo/elog/u-edit-elog-syntax.txt

> add this file in ultraedit
> UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
> I hope this will help you...

Have you maybe forgotten the attachment to this message?

Hello Folks,

Found an interesting problem with 2.3.7 under redhat 9.0 linux.

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.

Also, the self registration function equal to 3 does not always send email.

Cheers,
Roberto

UltraEdit Syntax coloring
=========================
add this file in ultraedit
UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
I hope this will help you...

it gives different color according to elog commands
some attributes are use internaly like

ShellOnSubmit
ShellParam

if somebody has other suggestion to improve the display ask me

> Now if you just port elog over to an apache and mysql enviroment, it would 
> be perfect! 

ELOG runs under apache, as described in the installation documentation, so 
half-perfect...

> > I noticed that my custom start page did not display the Welcome title icon.
> > It worked fine in prior elogs.
> > 
> > any hints?
> 
> Indeed there is a bug, it has to do that some icons wnt into the themes 
> directory and are served now from there. So the bug will fixed in the next 
> version (the fix is already avaliable from CVS). As a temporary workaround 
> you just move your image to the themese/default/ directory and it should 
> work.
> 
> An absolute path like /usr/local/... does not work, because this would open 
> a security hole (someone could access any picture on your computer just by 
> requesting an absolute path in the URL), so I removed that option from the 
> software and the documentation.

I did the work-around (moving icon to theme/default) and it worked. Thanks.

Now if you just port elog over to an apache and mysql enviroment, it would be
perfect! 

> I noticed that my custom start page did not display the Welcome title icon.
> It worked fine in prior elogs.
> 
> any hints?

Indeed there is a bug, it has to do that some icons wnt into the themes 
directory and are served now from there. So the bug will fixed in the next 
version (the fix is already avaliable from CVS). As a temporary workaround 
you just move your image to the themese/default/ directory and it should 
work.

An absolute path like /usr/local/... does not work, because this would open 
a security hole (someone could access any picture on your computer just by 
requesting an absolute path in the URL), so I removed that option from the 
software and the documentation.

Is there a possibility to integrate into ELOG some more features in terms 
of page formating?

Currently, the .cfg file allows you to specify only the data structure of 
the dataentry/consultation HTML page. And you only have very limited 
possibilities to change the layout of the page (basically only the order of 
attributes on the page and with the help of the .css file the font, color 
and background of the page as a whole).

What we would like to do is to :
+ apply a stylesheet class to an attribute (change the particular TD class)
+ specify the width of a textfield (sometimes it is really not necessary to 
have such a long textfield area for a 3-letter long code)
+ put an attribute on the same line as the previous one (instead of putting 
it automatically on the next line)

Therefore, in addition to the current attributes & parameters, we suggest 
the following syntax in the .cfg file:
+ parameter AttribPos which would specify the position of an attribute, 
it's lenght (for text attributes only) and the .css class to apply
+ parameters in [] are optional
AttribPos AttribName = same_line, width, [class]

Examples: 
AttribPos DateUp =  0,20, [important]   
+ Attribute "DateUp" will be put on the next line, the textfield width will 
be 20 characters and a .important class will be applied to it from the 
default (or specified) .css file.

AttribPos DateUp =  1,15,
+ this puts the DateUp attribute on the same line, width 15

We believe that these improvements would help to make the ergonomy of the 
screen better and thus facilitate the user-dataentry/consultation.