| |
This document gives you an overview about new functionality
which has been integrated into WEBDLG since its initial release as well
as fixed problems.
Additionally, please refer to the
Compatibility document about the state
of any currently known problems regarding DLG compatibility.
If you encounter any problem with WEBDLG not listed here please
report it to
support@marxmeier.com
or use the
feedback form on the Eloquence web site.
Contents:
- Fixed problems:
- The EditText and ListBox cursor functionality is now equivalent
to ASCII DLG (#2708).
- An EditText/ListBox cleanup memory leak has been fixed.
- System.version now returns
"B.07.10.02".
- New functionality:
- HTML code can be used in StaticText
and Button objects. This is especially useful to further customize a
POPUP BOX layout and to embed external hyperlinks into a dialog.
- Image areas can be used to
define multiple clickable areas within an image (#2579). Each area can
have an individual rule value associated.
- The System object now returns
information about the remote host (IP address, host name and port number)
(#2673).
- Fixed problems:
- A StaticText now correctly displays the ampersand '&' character
if either the Dialog's .alt attribute is
not set or the ampersand is prefixed with a backslash character, such
as '\&' (#2173). This is now functionally equivalent to ASCII DLG.
- On recent browsers, a PushButton's accelerator key is now correctly
underscored.
- The POPUP BOX PushButton accelerator keys now work correctly.
- Using CSS to specify
the border width of POPUP BOX dialogs now works if the new
PopupBorder configuration is
set to 0 (#897).
- System.version now returns
"B.07.10.01".
- New functionality:
-
Apache 2.0 integration
The new mod_eloq2 module allows to integrate WEBDLG into existing
Apache 2.0 web servers. Please refer to the
mod_eloq documentation
for details.
-
New color attributes
The .fgcolor and
.bgcolor attributes have been introduced (#2037).
The previous .fgc and
.bgc attributes were limited in that they could
not return a string value. They also caused an ambiguity problem in the
IDE Dialog Editor. For backwards compatibility,
.fgc and .bgc
are still provided. Please refer to the
attribute reference
for details.
Pre-release 5:
- New functionality:
- The Apache 1.3 EAPI is now supported. This allows to integrate WEBDLG
into existing Apache 1.3 web servers which were compiled with the
mod_ssl functionality. Please refer to the
mod_eloq documentation
for details.
- On Linux, WEBDLG is provided for the new glibc2.2 and Red Hat 8.0
distributions. On HP-UX, the PA-RISC and Itanium architectures are
supported, both in 32bit as well as in 64bit. Please refer to the
installation instructions
for details.
- The RuleOnChange
configuration and the
.ruleonchange
attribute allow to specify the rule behavior of edittext objects.
Previously, an edittext rule was only triggered if the contents
had changed. This can now be adjusted to the ASCII DLG and JDLG
behavior where edittext rules are triggered whenever the focus changes,
either globally or for a specific dialog, groupbox or object.
- The maximum nesting level of dialog objects has been increased to 10
to retain compatibility to the latest JDLG release.
Pre-release 4:
- Fixed problems:
- A race condition could prevent a program from starting correctly
(#1390).
- Listbox and multiline edittext contents beyond 1kB caused the program
to abort with error 684 (#1924).
- Invisible checkboxes lost their state (#1925).
- Various bugs have been fixed which affected the stability of the
communication with the browser frontend.
Pre-release 3:
- New functionality:
- The image object has been
implemented, allowing graphics to be embedded into dialogs.
Optionally, a rule can be triggered when an image is clicked.
- The system and
application objects have been
implemented, allowing a program to obtain additional information
about the current DLG driver.
(#761).
- The color and font attributes
.fgc,
.bgc,
.fontface,
.fontsize and
.fontstyle
have been implemented (#758). They are realized by means of portable
in-line CSS definitions, most of which even work with Netscape 4.x
browsers.
- The .border attribute has been implemented
for the dialog,
groupbox and
image objects (#759).
However, it doesn't work with Netscape 4.x browsers.
- The .bgimage attribute has been implemented
for the dialog object (#762).
It allows a dialog to have a background graphics. With Netscape
however, this unfortunately disables any background colors
(even with Netscape 6.2).
- The .ispassword attribute has been implemented
for the edittext object (#757).
If set, any characters entered are displayed as '*' asterisk
characters.
- Fixed problems:
- The keyboard focus was not set correctly (#812).
- Radio buttons of the same group always returned the rule of the first
button (#763).
- A listbox triggered a rule even if it was empty (#811).
Pre-release 2:
- New functionality:
- Fixed problems:
- The eloqwebd could crash if too much data was transferred, e.g. on
a very long command line or many environment variables (#119).
- The EloqSessionFinishedDocument
and EloqSessionExpiredDocument
directives caused the web server to fail with a "Method not allowed"
error message because mod_eloq tried to redirect a POST request to a
HTML page (#139).
- The eloqwebd crashed if no LogFlags
were specified (#156).
- If the .file attribute was used, any national characters contained in
the referenced file were probably not displayed correctly (#236).
The encoding of external files can now be configured with the
ExtCharset directive.
- Processing multiple program start requests at the same time failed
due to technical limitations of the RUN server protocol built into
eloqwebd. The RUN server protocol is not used anymore, thus the
corresponding configuration directives are obsolete.
The DLG connection is now established automatically by means of the
eloqcore -dlg command line option which has been introduced with
Eloquence A.06.31, so the program is no longer required to perform
a DLG SET ".driver" statement (if it however does it will be ignored).
- The location of the temporary directory is now automatically
determined, thus the corresponding configuration directives are
obsolete.
- The communication FIFO files (aka. named pipes) are now located in
the eloq.web subdirectory which is automatically created in the
system's temporary directory (usually /tmp or /var/tmp).
- The eloqcore -nb command line option is no longer used.
- Logging-on with eloqsd failed when a password was used which had
7 or 15 characters. This was actually an eloqsd bug which has been
fixed with Eloquence A.06.31.
|
|
