Make the HTML-parser exchangable about enlive HOT 7 CLOSED

This would be great for porting enlive over to ClojureScript. (@cgrand, do you know if anyone's tried enlive + clojurescript yet?)

from enlive.

Any developments on this?

from enlive.

@robertpfeiffer could you show a more elaborate example of an alternative HTML parser?

from enlive.

@ifesdjeen being implicitly tied to TagSoup is no good.
The real problem is the implicit reference to html-resource. *ml-resource fns do two things: get the resource and parse it. These two should be cleanly "decomplected" and composable: pluggable way to get resources (eg full-fledged http agent) and pluggable parsers.

from enlive.

I see the point, right. I've seen at least 2 more tickets/discussions about pluggable backends and stuff.
I'll try to throw in some prototype, it sounds like something possible.

from enlive.

The hardest part is API design, not implementation. So example code is
enough of a prototype to me. Don't wade time on a working prototype.

Le vendredi 11 janvier 2013, Alex P a écrit :

I see the point, right. I've seen at least 2 more tickets/discussions
about pluggable backends and stuff.
I'll try to throw in some prototype, it sounds like something possible.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-12141180.

On Clojure http://clj-me.cgrand.net/
Clojure Programming http://clojurebook.com
Training, Consulting & Contracting http://lambdanext.eu/

from enlive.

Ok, pluggable parsers are on the main branch now. See https://groups.google.com/d/topic/enlive-clj/snlJmmi5M7k/discussion

from enlive.