Kohana 3.2 compatibility, fixed a bunch of issues, refactored namespace logic, fixes #2

Author: Cédric de Saint Léger

LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2010 Cédric de Saint Léger
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -0,0 +1,31 @@
+Kohana_XML is a XML modules to generate and read XML documents in Kohana.
+It is build for KO3, but there are barely one or two lines that makes it KO3 specific, 
+so I guess it should work for KO2.x without much trouble.
+ 
+## Notable Features
+
+* **Extendible, configurable drivers** — You can use the XML class to write simple XML, 
+or use the Atom driver to generate Atom compliant XML, or write your own driver (extending XML 
+or another driver) to generate XML compliant to any specs you want. Driver support initial 
+configuration, which will be used when using native functions, and your own function. 
+Namespaces and prefix, value filters, default attributes, node name abstraction are all part 
+of driver configuration and are then used as such by native functions, so they are dealt with 
+on the fly. But you can also write your own function very easily in your drivers, and writing 
+an add_author($user_model) function in the Atom driver would take a second.
+
+* **Dealing with objects of the same class whatever function you use** – $xml→add_node(“test”); 
+generates another XML instance of the same driver you can add nodes to, import array or XML files
+to, search in, modify, export, combine… The whole XML document becomes modular, easy to read and 
+to modify, and to run through with method chaining. Just play Lego with your XML.
+
+* **Magic get and get()** — allows to easily run through the document. For instance 
+$atom→author→name will return an atom document author’s name, this regardless of your driver 
+configuration. As another example of node name abstraction, if you’ve decided to abstract “pubDate”
+with “updated” in your RSS2 driver configuration and “published” with “updated” in you Atom driver, 
+then $atom→updated will give you the same result as $rss→updated.
+
+* **Jelly-style driver configuration** — I liked the way Jelly initializes its models, so you can 
+configure yours just the same way. Driver configuration then goes into a static meta class, which 
+improves performance.
+
+* You can still use **DOM functions** if you wish and reintegrate in Kohana_XML

classes/xml.php

@@ -0,0 +1,13 @@
+<?php defined('SYSPATH') or die('No direct script access.');
+/**
+ *	Document   : xml.php
+ *	Created on : 1 mai 2009, 13:03:03
+ *	@author Cedric de Saint Leger <[email protected]>
+ *
+ *	Description:
+ *      XML class. Use this class to override XML_Core.
+ *      Extend this class to make your own XML based driver (Atom, XRDS, GData, RSS, PodCast RSS, or your own brewed XML format)
+ */
+
+ class XML extends XML_Core
+ {}