Re: [xsl] I love programs that output programs

["Anthony J (Tony) Bufort ajbufort@xxxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

That was an extremely cool story, Mike, thank you!  1998 - and pushing a
young XSL as hard, and as creatively, as all that.  
"when it was written, they could safely assume that everyone would be
using the same browser, a situation which rapidly changed."
*head to forehead* Did it ever!  Talk about ramping up the complexity.
-TonyAnthony J (Tony) BufortAJB ConsultingGranola, WA ;)www.ajbconsulting.us
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android

------------------------------------------------------------------------

From: Michael Kay michaelkay90@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Sunday, January 19, 2025 5:26:48 AM
To: xsl-list <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [xsl] I love programs that output programs

> This really works well, much better than generating XSLT code again and
again

The first XSLT application I ever came across (it was still called XSL at
the time, this was 1998) was an on-line banking application. A key part
of the requirement was that they should be able to create different
branded front-ends to the same underlying banking engine, and this was
achieved by constructing the front-end as a set of (about 400) XSLT
stylesheets, one per user interface page, which were themselves generated
by XSLT code from a configuration file that provided a declarative
description of the front-end interface. The application was very
successful and I think the imaginative design was a key contributor to
that. The main issues were (a) migrating it from Microsoft WD-xsl to
XSLT: there's always pain in being an early adopter, and (b) when it was
written, they could safely assume that everyone would be using the same
browser, a situation which rapidly changed.

Michael Kay
Saxonica

XSL-List info and archiveEasyUnsubscribe (by email)