I'm sure one of the plug-in gurus could have easily written a plug-in that does what I just did with XSLT. And maybe some people won't appreciate the difference - so here's my perspective.
With a plug-in, the user is pretty much stuck with what the programmer wrote. Sure, the programmer could add a lot of customizationability (or is it just customability?), but you can't please everyone.
With XML/XSLT, the user can modify the XSLT rather easily. Sure, there's a bit of a learning curve, but it's a LOT less steep than the programming languages most are familiar with (C++, Java, VB, etc.).
Of course, the downside to the "Export to XML" is that it isn't real-time. So... the best of both worlds would be if a kind plug-in developer would write a plug-in that exported to XML, applied an external XSLT, and displayed the result in MC's internal browser. It would be even better if JRiver added the ability to export just the current view scheme to XML - I don't think this is currently possible.
Any takers?
Scott-