XBL – a dubious abbreviation for eXtensible Binding Language – is perhaps the most important part of the XUL platform that we use, other than XUL itself. XBL is a mechanism for encapsulating a XUL UI and javascript code into …

In short, overlays are a mechanism by which one XUL file can be inserted into another XUL file, in a controlled manner. That last bit is the key: “in a controlled manner”. There are lots of ways to insert one …

Back to this diagram: I’ve spent a couple of posts discussing the complexities of the DTD files. Thankfully the rest of the diagram is fairly easy to explain. A user requests a XUL file from the server – initially this …

The short version of my previous XUL post is that our framework attempts to convert entity references into translated strings by trying three different approaches until one succeeds: A fast and accurate method, provided the developer has added a <tfs_string> …

Remember this diagram from a couple of posts ago: After our previous exciting instalment some of this should start to make a bit more sense. In particular, that post explains why there’s a double-ended arrow going between the ASP.Net layer …

When we began work on our new XUL-based framework we decided that translations should be built in at a low level. Most obviously a translation could be used to switch our applications to run in French, Spanish or some other …

As my previous post described, there are a whole load of different technologies that are jammed together to produce the applications I’m writing at the moment. In order to provide a little more insight into what’s happening – and so …