Charlie Savage wrote: >> In XMPP4R we're bound to the very intuitive REXML API because that's >> what XMPP4R is about: dealing with XML. I thought the only way out >> would be resembling it. That's why I have started REXML-dropin, a >> wrapper around libxml: >> http://github.com/astro/rexml-dropin/ > Curious how is progress on this? How big a patch would it be to the > libxml-ruby bindings? Should we integrate in your work, or leave it > separate.
It did its job for me and I was happy about the positive responses I received. But I saw no patches so far. If you manage to maintain the libxml API usage in it I hope it could catch more development activity in the libxml tree. So yes, please integrate if you feel comfortable with it. Stephan _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
