Yeah, it would be a rather odd argument for someone to make that even though I wrote QueryPath and the QueryPath module, I have to remove QueryPath from the QueryPath module simply because it is separable from Drupal (and because I have released the non-Drupal part separately from the Drupal module). Matt On Fri, Mar 25, 2011 at 8:45 AM, Scott Reynen <scott@makedatamakesense.com> wrote:
On 3/24/11 10:58 PM, David Metzler wrote:
Regarding introspection..... Not quite true. I use print_r on simplexml objects all the time with dsm.
drupal_set_message('<pre>' . print_r($xml,1) .'</pre>');
Hmm. That's never worked for me, and the note on php.net suggests it doesn't work for others. But if it works for you, great. I do want to note, though, that dsm() is not a shorthand for drupal_set_message(); it's a completely different function in the devel module.
although it sounds like the drupal community is pretty "down" on its use.
For my part, I didn't mean to suggest I'm "down" on SimpleXML, rather that it may be working fine (though it sounds like it wasn't for Jeff) even if inspection suggests otherwise.
I'll start giving qp a look , but this community has frowned on bundling third party libraries with drupal contrib modules in the past.
Kevin O has already pointed out QueryPath is okay on licensing, but that's not enough to make it okay for Drupal.org. The policy against hosting third party work on Drupal.org goes beyond licensing concerns. See:
That said, QueryPath is _not_ third party. The maintainer of the module on Drupal.org is the lead developer of the QueryPath project at querypath.org. It's first party.
-- Scott Reynen MakeDataMakeSense.com