The 0.6 Beta of the .Domino Framework was published on OpenNTF on the weekend. One of the last minute additions in this release is the abillity to access the XSLT/Skins feature of the .Domino Framework from within the Inspector tool. The significance of this is that this the Inspector tool can be invoked against ANY Notes database. So this tool now allows developers to apply XSLT transformations to design elements without the need to include any additional code in the applications themselves. All the code (and XSLT) is held in the .Domino Framework database.
e.g. I frequently take on development for existing Notes applications in which the fonts used in forms an/views are inconsistent. Using Inspector I can apply an XSLT from the .Domino Framework to all view/forms that change all fonts to Default Sans Serif saving me hours of manual (and boring) coding.
0
0
1 Nathan T Freeman Permalink Peter, I assume you're using DXL processing to do this. If so, be forewarned -- while REMOVING fonts generally works very well via DXL, you can't SET True Type fonts on views at the moment. It's a known bug, that looks like it was introduced at the time they fixed the other view DXL problem with selection formulas.
DXL in general is very good if you accept it's limitations as an
API. For instance, there is no flag in DXL to display Sametime
Presence awareness on a form. So if you round-trip, say, the
standard mail template, you'll lose that feature on the output. If
you know those boundaries and accept them, DXL in incredibly
empowering. If you can't accept those limitations, it's an exercise
in pounding nails into the floor with your head.
Except some further blog topics from me about this in the near
future.
2 Peter Presnell Permalink Thx for the tip Nathan, I was unaware of the Sametime Awareness issue. I am compiling a list of known DXL weaknesses in the Domino Framework wiki, so I will add that one to the list.
3 Nathan T Freeman Permalink Heh. Well, I have a MUCH larger list in my own Journal notes. :-)