Yellow is the New Blog

Last night I released a small but crucial update to DesignCatalog. It's hard for me to believe, but I've now been using this application (for all intents and purposes, in its current form) for nearly 6 years. And in all that time, I've never gotten burned by its reliance upon DXL. In other words, when using it to revert to a previous version of a design element, I've never ended up with a corrupted design element or even lost any code... at least, not that I noticed (i.e. nothing broke). Imagine my surprise, therefore, when I noticed that it wasn't storing the archived elements in note-format (/me looks sheepishly at the floor). I'm assuming that the reason I never got bitten by that before is that I primarily use it to archive versions of non-visual elements (specifically, agents and script libraries), and DXL is typically quite safe for those, even without using note-format. But it's a bit riskier for the other 1,500 of you who have downloaded DesignCatalog and may be using it for pages/forms/views, etc.

So version 1.2.2 is - aside from updating the About/Using docs to reflect the new release #/date - nothing more than remedying said oversight... an addition of 3 lines of code, to be precise. One of these days I'm going to update it to include some of the newer design elements (like Web Services and XPages), but in the meantime at least it'll now be round-trip safe for all the element categories it already supports.