blankslate 3.1.2 → 3.1.3

data/CHANGES

@@ -1,101 +0,0 @@
-= Change Log
-
-== Version 3.1.0
-
-* Included the to_xs arity patch needed for weird Rails compatibility
-  issue.
-
-* Escaping newlines in attributes now.
-
-* Allow method caching
-
-== Version 3.0.0
-
-* Ruby 1.9 compatiblity issues.
-
-== Version 2.2.0
-
-* Applied patch from Thijs van der Vossen to allow UTF-8 encoded
-  output when the encoding is UTF-8 and $KCODE is UTF8.
-
-== Version 2.1.2
-
-* Fixed bug where private methods in kernel could leak through using
-  tag!().  Thanks to Hagen Overdick for finding and diagnosing this
-  bug.
-
-== Version 2.1.1
-
-* Fixed typo in XmlMarkup class docs (ident => indent). (from Martin
-  Fowler).
-* Removed extra directory indirection from legacy CVS to SVN move.
-* Removed some extraneous tabs from source.
-* Fixed test on private methods in blankslate to differentiate between
-  targetted and untargetted private methods.
-* Removed legacy capture of @self in XmlBase (@self was used back when
-  we used instance eval).
-* Added additional tests for global functions (both direct and included).
-
-== Version 2.1.0
-
-* Fixed bug in BlankSlate where including a module into Object could
-  cause methods to leak into BlankSlate.
-* Made BlankSlate available as its own gem.  Currently the builder gem
-  still directly includes the BlankSlate code.
-* Added reveal capability to BlankSlate.
-
-== Version 2.0.0
-
-* Added doc directory
-* Added unit tests for XmlEvents.
-* Added XChar module and used it in the _escape method.
-* Attributes are now quoted by default when strings.  Use Symbol
-  attribute values for unquoted behavior.
-
-== Version 1.2.4
-
-* Added a cdata! command to an XML Builder (from Josh Knowles).
-
-== Version 1.2.3
-
-The attributes in the <?xml ... ?> instruction will be ordered:
-version, encoding, standalone.
-
-== Version 1.2.2
-
-Another fix for BlankSlate.  The Kernal/Object traps added in 1.2.1
-failed when a method was defined late more than once.  Since the
-method was already marked as removed, another attempt to undefine it
-raised an error.  The fix was to check the list of instance methods
-before attempting the undef operation.  Thanks to Florian Gross and
-David Heinemeier Hansson for the patch.
-
-== Version 1.2.1
-
-BlankSlate now traps method definitions in Kernel and Object to avoid
-late method definitions inadvertently becoming part of the definition
-of BlankSlate as well.
-
-== Version 1.2.0
-
-Improved support for entity declarations by allowing nested
-declarations and removal of the attribute processing.
-
-Added namespace support.
-
-== Version 1.1.0
-
-Added support for comments, entity declarations and processing instructions.
-
-== Version 1.0.0
-
-Removed use of <tt>instace_eval</tt> making the use of XmlMarkup much
-less prone to error.
-
-== Version 0.1.1
-
-Bug fix.
-
-== Version 0.1.0
-
-Initial version release.

data/README.rdoc

@@ -1,225 +0,0 @@
-# coding: UTF-8
-= Project: Builder
-
-== Goal
-
-Provide a simple way to create XML markup and data structures.
-
-== Classes
-
-Builder::XmlMarkup:: Generate XML markup notiation
-Builder::XmlEvents:: Generate XML events (i.e. SAX-like)
-
-<b>Notes</b>::
-
-* An <tt>Builder::XmlTree</tt> class to generate XML tree
-  (i.e. DOM-like) structures is also planned, but not yet implemented.
-  Also, the events builder is currently lagging the markup builder in
-  features.
-
-== Usage
-
-  require 'rubygems'
-  require_gem 'builder', '~> 2.0'
-
-  builder = Builder::XmlMarkup.new
-  xml = builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-  xml #=> <person><name>Jim</name><phone>555-1234</phone></person>
-
-or
-
-  require 'rubygems'
-  require_gem 'builder'
-
-  builder = Builder::XmlMarkup.new(:target=>STDOUT, :indent=>2)
-  builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-  #
-  # Prints:
-  # <person>
-  #   <name>Jim</name>
-  #   <phone>555-1234</phone>
-  # </person>
-
-== Compatibility
-
-=== Version 2.0.0 Compatibility Changes
-
-Version 2.0.0 introduces automatically escaped attribute values for
-the first time.  Versions prior to 2.0.0 did not insert escape
-characters into attribute values in the XML markup.  This allowed
-attribute values to explicitly reference entities, which was
-occasionally used by a small number of developers.  Since strings
-could always be explicitly escaped by hand, this was not a major
-restriction in functionality.
-
-However, it did suprise most users of builder.  Since the body text is
-normally escaped, everybody expected the attribute values to be
-escaped as well.  Escaped attribute values were the number one support
-request on the 1.x Builder series.
-
-Starting with Builder version 2.0.0, all attribute values expressed as
-strings will be processed and the appropriate characters will be
-escaped (e.g. "&" will be tranlated to "&amp;").  Attribute values
-that are expressed as Symbol values will not be processed for escaped
-characters and will be unchanged in output. (Yes, this probably counts
-as Symbol abuse, but the convention is convenient and flexible).
-
-Example:
-
-  xml = Builder::XmlMarkup.new
-  xml.sample(:escaped=>"This&That", :unescaped=>:"Here&amp;There")
-  xml.target!  =>
-    <sample escaped="This&amp;That" unescaped="Here&amp;There"/>
-
-=== Version 1.0.0 Compatibility Changes
-
-Version 1.0.0 introduces some changes that are not backwards
-compatible with earlier releases of builder.  The main areas of
-incompatibility are:
-
-* Keyword based arguments to +new+ (rather than positional based).  It
-  was found that a developer would often like to specify indentation
-  without providing an explicit target, or specify a target without
-  indentation.  Keyword based arguments handle this situation nicely.
-
-* Builder must now be an explicit target for markup tags.  Instead of
-  writing
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { strong("text") }
-
-  you need to write
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { xml_markup.strong("text") }
-
-* The builder object is passed as a parameter to all nested markup
-  blocks.  This allows you to create a short alias for the builder
-  object that can be used within the block.  For example, the previous
-  example can be written as:
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { |xml| xml.strong("text") }
-
-* If you have both a pre-1.0 and a post-1.0 gem of builder installed,
-  you can choose which version to use through the RubyGems
-  +require_gem+ facility.
-
-    require_gem 'builder', "~> 0.0"   # Gets the old version
-    require_gem 'builder', "~> 1.0"   # Gets the new version
-
-== Features
-
-* XML Comments are supported ...
-
-    xml_markup.comment! "This is a comment"
-      #=>  <!-- This is a comment -->
-
-* XML processing instructions are supported ...
-
-    xml_markup.instruct! :xml, :version=>"1.0", :encoding=>"UTF-8"
-      #=>  <?xml version="1.0" encoding="UTF-8"?>
-
-  If the processing instruction is omitted, it defaults to "xml".
-  When the processing instruction is "xml", the defaults attributes
-  are:
-
-  <b>version</b>:: 1.0
-  <b>encoding</b>:: "UTF-8"
-
-  (NOTE: if the encoding is set to "UTF-8" and $KCODE is set to
-  "UTF8", then Builder will emit UTF-8 encoded strings rather than
-  encoding non-ASCII characters as entities.)
-
-* XML entity declarations are now supported to a small degree.
-
-    xml_markup.declare! :DOCTYPE, :chapter, :SYSTEM, "../dtds/chapter.dtd"
-      #=>  <!DOCTYPE chapter SYSTEM "../dtds/chapter.dtd">
-
-  The parameters to a declare! method must be either symbols or
-  strings. Symbols are inserted without quotes, and strings are
-  inserted with double quotes.  Attribute-like arguments in hashes are
-  not allowed.
-
-  If you need to have an argument to declare! be inserted without
-  quotes, but the arguement does not conform to the typical Ruby
-  syntax for symbols, then use the :"string" form to specify a symbol.
-
-  For example:
-
-    xml_markup.declare! :ELEMENT, :chapter, :"(title,para+)"
-      #=>  <!ELEMENT chapter (title,para+)>
-
-  Nested entity declarations are allowed.  For example:
-
-    @xml_markup.declare! :DOCTYPE, :chapter do |x|
-      x.declare! :ELEMENT, :chapter, :"(title,para+)"
-      x.declare! :ELEMENT, :title, :"(#PCDATA)"
-      x.declare! :ELEMENT, :para, :"(#PCDATA)"
-    end
-
-    #=>
-
-    <!DOCTYPE chapter [
-      <!ELEMENT chapter (title,para+)>
-      <!ELEMENT title (#PCDATA)>
-      <!ELEMENT para (#PCDATA)>
-    ]>
-
-* Some support for XML namespaces is now available.  If the first
-  argument to a tag call is a symbol, it will be joined to the tag to
-  produce a namespace:tag combination.  It is easier to show this than
-  describe it.
-
-   xml.SOAP :Envelope do ... end
-
-  Just put a space before the colon in a namespace to produce the
-  right form for builder (e.g. "<tt>SOAP:Envelope</tt>" =>
-  "<tt>xml.SOAP :Envelope</tt>")
-
-* String attribute values are <em>now</em> escaped by default by
-  Builder (<b>NOTE:</b> this is _new_ behavior as of version 2.0).
-
-  However, occasionally you need to use entities in attribute values.
-  Using a symbols (rather than a string) for an attribute value will
-  cause Builder to not run its quoting/escaping algorithm on that
-  particular value.
-
-  (<b>Note:</b> The +escape_attrs+ option for builder is now
-  obsolete).
-
-  Example:
-
-    xml = Builder::XmlMarkup.new
-    xml.sample(:escaped=>"This&That", :unescaped=>:"Here&amp;There")
-    xml.target!  =>
-      <sample escaped="This&amp;That" unescaped="Here&amp;There"/>
-
-* UTF-8 Support
-
-  Builder correctly translates UTF-8 characters into valid XML.  (New
-  in version 2.0.0).  Thanks to Sam Ruby for the translation code.
-
-  You can get UTF-8 encoded output by making sure that the XML
-  encoding is set to "UTF-8" and that the $KCODE variable is set to
-  "UTF8".
-
-    $KCODE = 'UTF8'
-    xml = Builder::Markup.new
-    xml.instruct!(:xml, :encoding => "UTF-8")
-    xml.sample("Iñtërnâtiônàl")
-    xml.target!  =>
-      "<sample>Iñtërnâtiônàl</sample>"
-
-== Links
-
-Documents           :: http://builder.rubyforge.org/
-Github Clone        :: git://github.com/jimweirich/builder.git
-Issue / Bug Reports :: https://github.com/jimweirich/builder/issues?state=open
-
-== Contact
-
-Author::         Jim Weirich
-Email::          jim.weirich@gmail.com
-Home Page::      http://onestepback.org
-License::        MIT Licence (http://www.opensource.org/licenses/mit-license.html)

data/doc/releases/builder-1.2.4.rdoc

@@ -1,31 +0,0 @@
-= Builder 1.2.4 Released.
-
-Added a "CDATA" method to the XML Markup builder (from Josh Knowles).
-
-== What is Builder?
-
-Builder::XmlMarkup allows easy programmatic creation of XML markup.
-For example:
-
-  builder = Builder::XmlMarkup.new(:target=>STDOUT, :indent=>2)
-  builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-  puts builder.target!
-
-will generate:
-
-  <person>
-    <name>Jim</name>
-    <phone>555-1234</phone>
-  </person>
-
-== Availability
-
-The easiest way to get and install builder is via RubyGems ...
-
-  gem install builder    (you may need root/admin privileges)
-
-== Thanks
-
-* Josh Knowles for the cdata! patch.
-
--- Jim Weirich

data/doc/releases/builder-2.0.0.rdoc

@@ -1,46 +0,0 @@
-= Builder 2.0.0 Released.
-
-== Changes in 2.0.0
-
-* UTF-8 characters in data are now correctly translated to their XML
-  equivalents. (Thanks to Sam Ruby)
-
-* Attribute values are now escaped by default.  See the README
-  file for details.
-
-<b>NOTE:</b> The escaping attribute values by default is different
-than in previous releases of Builder.  This makes version 2.0.0
-somewhat incompatible with the 1.x series of Builder.  If you use "&",
-"<", or ">" in attributes values, you may have to change your
-code. (Essentially you remove the manual escaping.  The new way is
-easier, believe me).
-
-== What is Builder?
-
-Builder::XmlMarkup is a library that allows easy programmatic creation
-of XML markup.  For example:
-
-  builder = Builder::XmlMarkup.new(:target=>STDOUT, :indent=>2)
-  builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-
-will generate:
-
-  <person>
-    <name>Jim</name>
-    <phone>555-1234</phone>
-  </person>
-
-== Availability
-
-The easiest way to get and install builder is via RubyGems ...
-
-  gem install builder    (you may need root/admin privileges)
-
-== Thanks
-
-* Sam Ruby for the XChar module and the related UTF-8 translation
-  tools.
-* Also to Sam Ruby for gently persuading me to start quoting attribute
-  values.
-
--- Jim Weirich

data/doc/releases/builder-2.1.1.rdoc

@@ -1,58 +0,0 @@
-= Builder 2.1.1 Released.
-
-Release 2.1.1 of Builder is mainly a bug fix release.
-
-== Changes in 2.1.1
-
-* Added <tt>reveal</tt> capability to BlankSlate.
-
-* Fixed a bug in BlankSlate where including a module into Object could
-  cause methods to leak into BlankSlate.
-
-* Fixed typo in XmlMarkup class docs (from Martin Fowler).
-
-* Fixed test on private methods to differentiate between targetted and
-  untargetted private methods.
-
-* Removed legacy capture of @self in XmlBase (@self was used back when
-  we used instance eval).
-
-* Added additional tests for global functions (both direct and
-  included).
-
-* Several misc internal cleanups, including rearranging the source
-  code tree.
-
-<b>NOTE:</b> The escaping attribute values by default is different
-than in previous releases of Builder.  This makes version 2.0.x
-somewhat incompatible with the 1.x series of Builder.  If you use "&",
-"<", or ">" in attributes values, you may have to change your
-code. (Essentially you remove the manual escaping.  The new way is
-easier, believe me).
-
-== What is Builder?
-
-Builder::XmlMarkup is a library that allows easy programmatic creation
-of XML markup.  For example:
-
-  builder = Builder::XmlMarkup.new(:target=>STDOUT, :indent=>2)
-  builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-
-will generate:
-
-  <person>
-    <name>Jim</name>
-    <phone>555-1234</phone>
-  </person>
-
-== Availability
-
-The easiest way to get and install builder is via RubyGems ...
-
-  gem install builder    (you may need root/admin privileges)
-
-== Thanks
-
-* Martin Fowler for spotting some typos in the documentation.
-
--- Jim Weirich