You do realize that as an alternative to having the XSL generate the entire
function, it could simply emit javascript variables, and a linked js file
could use those variables in its machinations. Something like:
XSL output (in head section):
<script>
var g_msg = 'hello world';
</script>
Linked js file:
function sayHello() {
alert( g_msg );
}
Regards,
--A
From: "Annmarie Rubin (anrubin)" <anrubin(_at_)cisco(_dot_)com>
Reply-To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
CC: "Annmarie Rubin (anrubin)" <anrubin(_at_)cisco(_dot_)com>
Subject: RE: [xsl] xsl variable not resolved in javascript output again
Date: Thu, 19 May 2005 06:06:25 -0700
David,
Good suggestion. The syntax for escaping the angle brackets when not
using the CDATA section was pretty tricky. This is what finally worked:
Ann Marie
<xsl:comment>
function showbook() {
var showframeURL = '<xsl:value-of
select="$__Frameset_File_Name_token"/>' + "?" + document.URL;
<![CDATA[
var hideframeURL = unescape(document.URL);
if (window.self == top)
{
document.write("<a href='" + showframeURL + "' title='Show table of
contents and index'><font face='verdana, arial, helvetica, sans serif'
size='1'>Show Book</font></a>");
}
else
{
document.write("<a href='" + hideframeURL + "' target='_top'
title='Hide table of contents and index'><font face='verdana, arial,
helvetica, sans serif' size='1'>Hide Book</font></a>");
}
}
showbook();
//]]></xsl:comment>
</script>
_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--