I've worked on making the javascript compliant with both IE6 and Moziilla (especially Firebird) - although there is still some problem with Firebird's internal XSLT processor. Here's the latest screenshot of the XAlbum result:
If you're using IE6, you can load XAlbum.htm and get one-click transformation of your MPL. Mozilla won't work - though I've been trying to fix that. The files can be downloaded at
http://pages.sbcglobal.net/scottraymond/XAlbum05.zip.
I have a question for folks: How undesirable is it to use an application server component - say with Tomcat's servlet container (
http://jakarta.apache.org/tomcat/) - to take an "application server" approach with presenting the MPL as HTML? The obvious downside is the need to install Tomcat - though I, personally, found it quite easy to do. Once Tomcat is successfully installed, you'd just need to unzip a single file and the servlet that takes care of all the back-end is up and running.
The upside to using a servlet to do the transformation is an ability to do server-side processing. If you want to share your library presentation via the internet, this is pretty much a necessity. You'd need to do things like paging (you can't very well send the *whole* html (which could be MBs for most of you) all at once. It also makes it easier to pass parameters (for things like searching), etc.
Thoughts? Ideas? Please respond in the thread
http://yabb.jriver.com/interact/index.php?board=5;action=display;threadid=16293Scott-