Developer Blog

the progress we are making

February 12th  Inside the Xopus Application Framework

For the development of Xopus 4 we have created the Xopus Application Framework. This framework provides us a stable platform needed to build a serious application like Xopus in Javascript.

January 15th  Highlighting the current context element

We received a request from a customer who wanted to highlight the current context element, i.e. the element where the cursor is currently in. As we already highlight elements when you hover over menu items, it took little effort to make this functionality available in the API. Here is the script that you can use:

July 10th  Xopus plays Tic-Tac-Toe

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.

February 29th  Validating your HTML/CSS for use in Xopus

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.

February 25th  Incompatible Markup Pointers Revisited

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.

February 21st  prettyPrintLargeNumber

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.

January 24th  How to style unknown elements in IE

Two days ago I posted what I thought was just a little tip on the weblog of Sam Ruby. He was trying to style the new elements from HTML5 in Internet Explorer. Here at Xopus we have known for several years (since about 2002 or 2003) that you have to do document.createElement(elementName), which somehow lets the CSS engine know about that new element. But apparently we were the only ones who knew this. Ian Hickson even called it the most noteworthy news of the day.

December 11th  Picky dates

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.