2013/2/12 ckirkendall <ckirkend...@gmail.com> > I recently added support for xpath and custom selectors in addition to the > standard ccs3 selector. I added these to get around some of the > limitations of goog.dom.query and querySelector. I would be interested in > your specific use case to see if we can't provide a custom selector to > handle it.
My (rather unspecific) use case is: The same selector syntax (and semantics) for server- and client side. As soon as I've also fully ported the templating stuff: hopefully server and client templates from the same source. My syntax compiler is a straight port of enlive's state-machine-generator, so with enfocus' support for custom selectors, it might be feasible to offer enlive selectors in enfocus based on that port. If you are interested in that, let me know. I'll gladly share the code and experiences from porting, I just don't want to do a public release yet. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
