Developer Blog
the progress we are making
Usually Xopus keeps you within the bounds and rules of a structured document: bold is allowed in a paragraph, but not in a header, or a header must be followed by the name of the author.
In Internet Explorer Xopus relies on the contentEditable feature. But unfortunately activating contentEditable will change the look and feel of the HTML output of your XSLT. The goal of most of our CSS and HTML best practises is to prevent or workaround these effects.
Last December I wrote about the Incompatible Markup Pointers exception in IE. I've been able to pinpoint the source of the exception more exactly: it occurs if you want to paste HTML into a TextRange, and the window the parent element of the TextRange belongs to does not have focus.
The last few months have been extremely busy. We are working with many clients and partners to enhance their integrations. There is always a steady stream of support and forum questions. Development of the Xopus 4 platform uses a lot of our resources. And last but certainly not least Mark Wubben is following his dream to live and work in Copenhagen.
When using xs:date as a type in the schema for a node-value Xopus might give you some trouble when editing that. Say for example that you use a value-of to print the value and you put your cursor in it and start typing a new value. Xopus will be very picky about that value: only valid xs:date values will be accepted by Xopus so you could probably overwrite a couple of numbers to ge t a new date, but it is not likely to win this years' prize for most user-friendly date editing.
I was implementing Xopus for a project and they have a lot of values that need to be looked up from a settings file. They look up values for places, provinces, types of organizations, people in organizations, programs of organizations and so on. On top of that they have the standard lookups for images and links (standard because you can easily copy them from the simple demo).