Subject: Re: [xsl] Practicality of Separating Data from Presentation From: "Robert S. Koberg" <rob@xxxxxxxxxx> Date: Mon, 01 Jul 2002 14:52:33 -0700 |
--------------------------------------------------------------- - XSLT is good for some things, some rather easy things become very hard to do in XSLT... XSLT is a very good partner to existing languages. In addition, u can use XSLT as a preprocessor, auto generating ASP for example. This is where XSLT is a star in auto generating code for you. --------------------------------------------------------------- My next question, James, would be, what is the best way (in your opinion) for auto-generating ASP? Do you have any examples of ASP code being generated through an XSLT file? Does it involve 'overloading' the XSLT file with ASP code - i.e. writing some ASP code within the XSLT file? I have seen some code like the following:
<xsl:text disable-output-escaping="yes"><</xsl:text>%= Now %<xsl:text disable-output-escaping="yes">></xsl:text>
as a way to create ASP code. What would be some pro's and con's to this approach - assuming there are both?
best, -Rob
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Practicality of Separatin, intelikon | Thread | Re: [xsl] Practicality of Separatin, J.Pietschmann |
RE: [xsl] XSL: For-Each Efficient o, Wendell Piez | Date | Re: [xsl] Practicality of Separatin, Wendell Piez |
Month |