XMLmind XML Editor V2.3 Patch 1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml
===========================
V2.3 Patch 1 (June 09, 2003)
First release officially supported on Mac OS X
(Mac OS X 10.2+, Java[tm] 1.4.1. Use Software
Update to get this Java[tm] runtime or download it
from http://www.apple.com/downloads/macosx/apple/.)
Know problems on Mac OS X:
* Warnings about font metrics are reported at
startup.
* Printing large documents consumes an enormous
amount of memory and can cause XXE (i.e. the
Java[tm] VM) to crash with a bus error.
* Drag and drop and other interaction with the
system (such as playing with the open command)
can cause XXE (i.e. the Java[tm] VM) to crash
from time to time.
* If XXE is not already running, double-clicking
on a XML document will start the editor but
will fail to open the document in the newly
started editor.
* Non US keyboards only: some keyboard shortcuts
trigger the wrong actions. For example, with a
French keyboard, Command-A triggers the action
that should be triggered by Command-Q and
vice-versa, Command-Z triggers the action that
should be triggered by Command-W and
vice-versa, Command-, triggers the action that
should be triggered by Command-M and
vice-versa. That is, Java[tm] on Mac OS X always
uses the US layout for keyboard shortcuts.
* The document view cannot be rendered using
antialiased fonts, which is the default
rendering on Mac.
* Controls such as text fields embedded in the
document view are rendered using antialiased
fonts (which is not consistent with the
document view -- see above).
Moreover, these embedded text fields have font
metrics problems. That is, it is often
possible to move the caret to the middle of a
letter.
To our knowledge, most problems come from bugs in
the new Apple Java[tm] 1.4.1 runtime. They will
probably be fixed by Apple in the next few months.
Note that even with these problems, we have found
XXE nice and reliable to use on Mac.
Other enhancements:
* Added support for MacRoman encoding.
* XHTML and DocBook table row editing commands
are now also enabled when a row is explicitly
selected. Previously, these commands required
a descendant of a table cell to be implicitly
or explicitly selected.
* The dialog box displayed by the putAttribute
command to let the user input the value of an
attribute now shows current value of this
attribute.
* Process command elements mkdir, rmdir and
delete now have a quiet attribute which, when
set to true, will prevent an error message to
be reported when the operation fails.
* Command buttons embedded in the document view
now accepts element-name(), element-label(),
etc, as the value of their text parameter.
Previously, this parameter only accepted a
literal string as its value.
* The combo-box() control now can display any
attribute or element value, including an
invalid value or no value at all. Previously;
only the text-field() and text-area() controls
were able to do this.
* The date-field() control now supports gDay,
gMonthDay, gMonth, gYearMonth, gYear as the
value of its data-type parameter. Previously
this control only supported date, time and
dateTime.
* Added new embeddable command button
set-attribute-button() which can be used to
give a value to specified attribute. A pop-up
menu listing all possible values is displayed
when this button is clicked. Only works when
the type of the specified attribute is an
enumerated type or is IDREF or IDREFS.
Bug fixes:
* Fixed two bugs triggered when both attr(foo)
and a text-field() control used to edit the
value of attribute foo were used to style the
same element (this is an oversimplification of
what actually happened).
* date-field() is no longer lenient when parsing
a date. For example, previously it accepted
01/32/2003 as 02/01/2003.
