Permalink
Commits on Jun 7, 2009
Commits on May 28, 2009
  1. Prepped for 0.2.5 release.

    jnunemaker committed May 28, 2009
  2. Classes can now be strings instead of constants so you don't have to …

    …worry about class definition order (this was all for technicalpickles, enjoy!)
    jnunemaker committed May 28, 2009
Commits on May 27, 2009
  1. Removing debugging stuff

    committed May 27, 2009
  2. Merge branch 'newspecs'

    committed May 27, 2009
Commits on May 18, 2009
  1. Prepped for 0.2.4 release.

    jnunemaker committed May 18, 2009
Commits on Apr 30, 2009
Commits on Apr 16, 2009
  1. Updated issues links

    jnunemaker committed Apr 16, 2009
Commits on Jan 30, 2009
  1. Removed no longer needed libxml helpers.

    Prepped for 0.2.2 release.
    jnunemaker committed Jan 30, 2009
  2. updated history

    jnunemaker committed Jan 30, 2009
  3. Removed GC.start from .parse as it was causing significant performanc…

    …e issues.
    
    Setting the node to nil should be sufficient to mark it for garbage collection, which will run before the ruby program terminates.
    
    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    bkeepers committed with jnunemaker Jan 30, 2009
  4. Removed get_ prefix, it reminds me too much of Java

    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    bkeepers committed with jnunemaker Jan 30, 2009
  5. Type coercion

    When the :parser option is provided for an element mapping along
    with a non-primitive type, HappyMapper will attempt to coerce the
    value of the mapped node into the specified type by using the class
    method specified by :parser.
    
    If coercion requires access to the full node (including tags), use
    :raw => true to parse the full node instead of just the value.
    
    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    mojodna committed with jnunemaker Jan 29, 2009
  6. auto-detect root nodes

    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    mojodna committed with jnunemaker Jan 30, 2009
  7. Pass namespaces around to avoid storing state

    Attaching a namespace to an instance of an object causes it to be
    stateful, resulting in non-deterministic behavior when run against
    different documents in varying orders.
    
    When choosing a namespace to use, the order is:
    1 - via namespace in class defn
    2 - via :namespace in element defn
    
    This patch also removes some unnecessary initialization.
    
    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    mojodna committed with jnunemaker Jan 30, 2009
  8. Improved namespace support

    The previous namespace support did not handle documents containing multiply
    namespaced nodes.  It also made assumptions about the 'default' namespace
    when multiple prefixed namespaces were provided (with no implicit default).
    
    This patch allows namespaces to be set item-wide (via 'namespace <ns>' in
    the class) or on a per-element basis (via :namespace => <ns> on the
    element mapping).
    
    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    mojodna committed with jnunemaker Jan 29, 2009
  9. fixed warnings about use of XML::Parser

    Signed-off-by: John Nunemaker <nunemaker@gmail.com>
    mojodna committed with jnunemaker Jan 29, 2009
Commits on Jan 29, 2009
  1. updated todo

    jnunemaker committed Jan 29, 2009
  2. Prepped for 0.2.0 release.

    jnunemaker committed Jan 29, 2009
  3. Updated history

    jnunemaker committed Jan 29, 2009
  4. Added :root option to tag method. This allows setting an object as th…

    …e root element, which sets xpath to use / and sets single to true for this object.
    jnunemaker committed Jan 29, 2009
  5. Automatic handling of namespaces. Much thanks to Robert Lowrey for st…

    …arting this and providing me with a lot of research.
    jnunemaker committed Jan 29, 2009
  6. Removed double namespace checks as the test spec incorrectly had the …

    …namespace in the tag which caused the doubleage.
    jnunemaker committed Jan 29, 2009