Developer Blog

the progress we are making

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.

December 7th  Fixing incompatible markup pointers

Update! See here for a better explanation and solution.

October 30th  Creating an inline lookup

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).

August 28th  The Craziest DHTML Hack Ever

Hi, my name is Mark Wubben and for the past six months I've been working on the craziest DHTML hack ever. Now, to be fair, that's not six months full time, so perhaps not as crazy. And I only really got started this summer, so let's make it eight weeks.

August 27th  Javascript Obfuscation

Every now and then we get a question about our Javascript obfuscation tools. There are some tools out there that claim to be able to obfuscate any Javascript, but we haven't been able to find a tool that could hit the sweet spot between human and machine readability. The results were either human readable (though, admittedly, not by most humans) or not machine readable. So we set off to build our own.

August 20th  setAttribute with a floating point value

We received this bug report: "0,5" is an invalid priority value. We could not reproduce this problem and at first we were at a lost what the cause could be.

August 16th  Browser based

How nice, a developer blog! Now I can share the frustrations of doing a browser based editor with the whole world.