Woops, I accidently posted too quick!

Anyway, I was able to successfully load the xml into an array, but I can't 
get my mouse over function to be able to see the definitionArray, the 
function invariably gives an "object expected" error.  It acts as if it is a 
scoping problem, but I declare  definitionArray in a body onLoad event so it 
should be there...



"sl" wrote:

> If you're just focusing on display things such as tooltips, then don't 
> forget that CSS alone (rather than Xslt) to render an Xml file can be very 
> powerful and is supported on a number of browsers.
> 
> steven :: http://stevenR2.com
> 
> 
> "Michael D." <MichaelD@d...> wrote in message 
> news:375AE4C5-C015-4EB7-80BE-38341A42330B@m......
> > Martin,
> >  Thanks for the suggestions.  We are developing in a limited environment 
> > (a
> > corporate training department), and don't have access to anything other 
> > than
> > simple html files (and anything interesting I can do inside of such), as 
> > well
> > as various Macromedia products.  Can't do anything server side, our 
> > courses
> > can't even directly interface with our Learning Management System (LMS) 
> > yet...
> >
> > However, one advantage of the environment is that all the desktops of
> > learners are standardized on MSIE 6, so I can be pretty confident that
> > anything IE-specific that I develop will work.  It is a 12,000+ employee
> > company, so I don't see any overnight change in browser standard 
> > ocurring...
> > :-)
> >
> >
> >
> > "Martin Honnen" wrote:
> >
> >>
> >>
> >> Michael D. wrote:
> >>
> >> >   I am just getting started with XML, trying to create a glossary.xml 
> >> > file
> >> > to use in various internal e-learning courses.  I've figured out how to
> >> > create a XSL transformation in my glossary.xml file, but I haven't 
> >> > figured
> >> > out how to actually include my glossary.xml in a real live .html page, 
> >> > and
> >> > have the transformations take effect.
> >>
> >> If you want to use XML and XSLT then consider doing that on the server
> >> (e.g. with ASP or with ASP.NET) where you can be sure you have an XSLT
> >> processor. Then you can simply build HTML documents dynamically and
> >> include anything you create as the result of an XSLT transformation.
> >>
> >> Doing XSLT client-side in the browser is pretty restricted, only IE 6
> >> with MSXML 3 comes with an XSLT 1.0 processor, then Mozilla/Firefox and
> >> recent Safari versions. But scripting XSLT transformations is different
> >> in IE 6 and Mozilla and as far as I know not possible in Safari.
> >>
> >> In terms of HTML all you can do is e.g.
> >>    <iframe src="glossary.xml"></iframe>
> >> where glossary.xml then references your stylesheet e.g.
> >> <?xml-stylesheet type="text/xsl" href="glossaryStylesheet.xml"?>
> >>
> >>
> >> -- 
> >>
> >> Martin Honnen --- MVP XML
> >> http://JavaScript.FAQTs.com/
> >> 
> 
> 
>