--- nfo/perl/libs/XML/XUpdate/XSLT.pm	2003/05/01 17:03:52	1.2
+++ nfo/perl/libs/XML/XUpdate/XSLT.pm	2003/05/01 20:11:49	1.3
@@ -4,11 +4,12 @@
 #
 # By Andreas Motl, andreas.motl@ilo.de
 #
-#    $Id: XSLT.pm,v 1.2 2003/05/01 17:03:52 joko Exp $
+#    $Id: XSLT.pm,v 1.3 2003/05/01 20:11:49 joko Exp $
 #
 #    $Log: XSLT.pm,v $
-#    Revision 1.2  2003/05/01 17:03:52  joko
-#    revamped processing: a) _calculate and b) _apply (NEW)
+#    Revision 1.3  2003/05/01 20:11:49  joko
+#    * added pod from xupdate.pl
+#    - extracted xml to external files
 #
 #    Revision 1.1  2003/04/30 02:36:32  joko
 #    initial commit
@@ -16,10 +17,60 @@
 #
 ###############################################################################
 
+=pod
+
+
 =head1 NAME
 
 XML::XUpdate::XSLT - A perl module for updating xml documents using XUpdate via XSLT.
 
+
+=head3 Overview
+
+  This is not the same xupdate currently available from CPAN at
+  http://search.cpan.org/author/PAJAS/XML-XUpdate-LibXML-0.4.0/xupdate .
+  
+  Its intention - however - is identical:
+  xupdate - Process XUpdate commands against an XML document.
+
+
+=head3 Their implementations differ:
+
+    1. xupdate (by Petr Pajas) uses ...
+    XML::XUpdate::LibXML - Simple implementation of XUpdate format 
+    
+    ... which is based on XML::LibXML which in turn is:
+    [...]
+    This module is an interface to the gnome libxml2 DOM parser (no SAX parser support yet), 
+    and the DOM tree. It also provides an XML::XPath-like findnodes() interface, providing 
+    access to the XPath API in libxml2. 
+    [...]
+
+    2. This xupdate attempts to implement the XUpdate specs using XSLT only.
+    
+
+=head3 Yet another xupdate - facts in short:
+
+  S: It would be nice to have a pure perl thingy which does (almost) the same stuff....
+  
+  Q: Can we achieve compliance with its (XML::XUpdate::LibXML) API? (or just a subset ....)
+  
+  Q: Can we achieve the processing using CPAN's XML::XSLT?
+  S: Proposal: XML::XUpdate::XSLT!?
+  
+  Q: Can we mimic/use the interface of the - already established - 'xupdate' program???
+  
+  Q: Should we follow the CRUD path first? (CRUD means: Create, Retrieve, Update, Delete)
+  S?: Proposal: XML::XUpdate::XSLT::API uses XML::XUpdate::XSLT::CRUD
+
+
+=head4 Todo
+
+  o What about proper encoding? (ISO-8859-1 or UTF-8)
+  o Is it possible to create the required "xsl_template.xml" at runtime via XSL itself?
+  o Cache contents of external files (*.xml). Performance!
+  
+
 =cut
 
 
@@ -32,6 +83,7 @@
 
 use XML::XSLT 0.41;
 use Carp;
+use File::Basename;
 use Data::Dumper;
 
 # Namespace constants
@@ -40,7 +92,7 @@
 
 use vars qw ( $VERSION );
 
-$VERSION = '0.02';
+$VERSION = '0.01';
 
 
 ######################################################################
@@ -54,7 +106,7 @@
   $self->{DEBUG} = $args->{debug};
   $self->{WARNINGS} = $args->{warnings};
 
-  $self->__init_default_macros();
+  $self->__init_default_stylesheets();
 
   return $self;
 
@@ -72,22 +124,10 @@
   my $xml = shift;
   my $options = shift;
   if ($options->{encap}) {
-    $xml = qq(<?xml version="1.0" encoding="ISO-8859-1"?>
-  
-    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
-    
-        <!--
-        This XML Stylesheet is the result of a translation from 
-        XUpdate lingo. It actually applies the payload to the 
-        original xml document. (it's the second processing step!)
-        -->
-        
-        <xsl:output method="xml" />
-
-$xml
-        
-    </xsl:stylesheet>
-  );
+    my $template = $self->__slurp_file("xsl_template.xml");
+    # FIXME! What about the quirky? Is there a better one?
+    $template =~ s!<xsl:quirky_placeholder />!$xml!;
+    $xml = $template;
   }
   $self->{XML}->{xsl}->{$name} = $xml;
 }
@@ -142,7 +182,6 @@
   $self->{XML}->{result} = $self->{XSLT_ENGINE_LIVE}->toString();
 }  
   
-
 sub toString {
   my $self = shift;
   return $self->{XML}->{result};
@@ -168,81 +207,30 @@
 }
 
 
-sub __init_default_macros {
+sub __init_default_stylesheets {
   my $self = shift;
-  $self->{XML}->{xsl}->{xupdate2xsl} = qq(<?xml version="1.0" encoding="ISO-8859-1"?>
-  
-  <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+  if (my $payload = $self->__slurp_file("xupdate2xsl.xml")) {
+    $self->{XML}->{xsl}->{xupdate2xsl} = $payload;
+  }
+}
+
+sub __slurp_file {
+  my $self = shift;
+  my $filename = shift;
   
-      <!--
-      Purpose of this XML Stylesheet is to implement a set of templates 
-      to translate XUpdate lingo into an intermediate xslt stylesheet 
-      which actually performs the update to the original xml document
-      in a second step.
-      -->
-      
-      <xsl:output method="xml" />
-  
-      <!-- 1. This is the passthru logic (copy all untouched nodes). -->
-      <xsl:template name="passthru"><xsl:copy><xsl:apply-templates /></xsl:copy></xsl:template>
-      <!-- activate this -->
-      <xsl:template match="*"><xsl:call-template name="passthru" /></xsl:template>
-      <!-- override some builtin rules: see http://www.w3.org/TR/xslt#built-in-rule -->
-      <xsl:template match="comment()"><xsl:call-template name="passthru" /></xsl:template>
-  
-      <!-- 2. This is the translation part: XUpdate becomes XSLT -->
-      
-      <!-- This node "encapsulates" common infrastructure. -->
-      <xsl:template match="xupdate:modifications">
-  
-          <!-- 1. This is the passthru logic (copy all untouched nodes). -->
-          <!-- in fact this is the xsl from above translated to be able to be generated by xsl itself! -->
-              <xsl:comment> 1. passthru logic </xsl:comment>
-              <xsl:element name="xsl:template">
-                  <xsl:attribute name="name">passthru</xsl:attribute>
-                  <xsl:element name="xsl:copy"><xsl:element name="xsl:apply-templates" /></xsl:element>
-              </xsl:element>
-              <xsl:element name="xsl:template">
-                  <xsl:attribute name="match">*</xsl:attribute>
-                  <xsl:element name="xsl:call-template"><xsl:attribute name="name">passthru</xsl:attribute></xsl:element>
-              </xsl:element>
-              <xsl:element name="xsl:template">
-                  <xsl:attribute name="match">comment()</xsl:attribute>
-                  <xsl:element name="xsl:call-template"><xsl:attribute name="name">passthru</xsl:attribute></xsl:element>
-              </xsl:element>
-  
-          <!-- continue with all inline nodes -->
-              <xsl:apply-templates />
-  
-      </xsl:template>
-  
-      <!-- This node "encapsulates" infrastructure for handling the directives. -->
-      <xsl:template match="xupdate:insert-after">
-          <xsl:comment> 2. context finder </xsl:comment>
-          <xsl:apply-templates />
-      </xsl:template>
-  
-      <!-- This node passes through all attributes and childnodes rewriting the tagname only. -->
-      <xsl:template match="xupdate:element">
-          <xsl:comment> 3. rewrite / vivify elements/attributes </xsl:comment>
-          <xsl:element name="xsl:element">
-              <xsl:copy-of select="@*"/>
-              <xsl:apply-templates />
-          </xsl:element>
-      </xsl:template>
-  
-      <!-- This node passes through all attributes and childnodes rewriting the tagname only. -->
-      <xsl:template match="xupdate:attribute">
-          <xsl:element name="xsl:attribute">
-              <xsl:copy-of select="@*"/>
-              <xsl:apply-templates />
-          </xsl:element>
-      </xsl:template>
-  
-  </xsl:stylesheet>
+  # does file exist?
+  if (! -e $filename) {
+    $filename = dirname(__FILE__) . "/$filename";
+    if (! -e $filename) {
+      croak("File $filename does not exist.");
+    }
+  }
   
-  );
-
+  open(FH, "<" . $filename);
+  my @lines = <FH>;
+  my $content = join("", @lines);
+  close(FH);
+  return $content;
 }
 
 1;