RE: Using Transforms and #include file

I'm doing that currently. There are two reasons for what I'm trying to do
this

1.  My site has a lot of functionality all in one page because of the
".innerHTML" technique I'm using.  I only need specific scripts for specific
content so I didn't want to mass load all script.

2. When I use the ".innerHTML" method I notice that eventhough you can see
the representation with the browser, if you try to "viewsource" nothing
shows up. I'm thinking that If I output my script in the same manner I don't
have to bare my "script soul" to the world.

-----Original Message-----
From: Hunsberger, Peter [mailto:Peter.Hunsberger@xxxxxxxxxx]
Sent: Tuesday, November 13, 2001 10:07 AM
To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
Subject: RE:  Using Transforms and #include file



> Is it possible to have something like the following output from XSL so
that
> the actual script gets inserted?  I was trying to avoid actually putting
all
> of my script into the XSL file.

Why not just have your HTML include the scripts at run time as external
files?  
I.e. output something like:

            <script language="javascript" src="JScripts/Buttons.js"
type="text/javascript"/>

which will cause the HTML file to pick up the script file from the server
and include it client side.  That way you don't have to ship it multiple
times to the client...


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list