I'm pleased to report that XSLTXT recently got mentioned in an article on IBM's developerWorks: XML zone that talks about alternative syntaxes for XML.

Coincidentally I'm using XSLTXT at work at the moment as part of a system for editing Java UIs with NetBeans. Rather than using the code generation facilities NetBeans provides I've developed our own that takes the xml description of the screen layout produced by NetBeans and transforms it with XSLTXT to produce a dialog class. This does actually have some advantages for us over using NetBeans directly.

• The generated classes are designed for extending by subclassing instead of by editing directly. This makes it much easier to manage our customizations of the generated code.
• We can generate additional code to link each UI screen to the persistent object that it is editing.
• We use a number of custom wrapper classes round standard widgets like JButton and have a few larger composite widgets as well. Having our own generation system is easier than setting these things up as beans so that they can be directly used in NetBeans.