Enlive Selector Syntax about enfocus HOT 10 CLOSED

I do plan on supporting enlive syntax but it is still a bit off. There is however hope. I have been working on parser for css3 selectors that would allow me to convert string selectors to enlive selectors. This is required for a compile time snippet feature I am adding in enfocus. It would also allow me to write wrappers for enlives' deftemplate and defsnippet and provide string base selectors for these.

from enfocus.

Ok, so right now, you're also duplicating defsnippet and deftemplate code when you need them on both ends?

from enfocus.

For my sites I am not using enlive, all rendering is happening on the
client side. So, I have not ran across this issue. That being said I can
certainly see the need for this. I may have something late next week for
you play with. It depends on how much time I get to work on things this
week.

CK

from enfocus.

Awesome :-)

Thank you once again for your work on producing a port of a great library. The domina branch looks interesting!

from enfocus.

Quick question on having shared source between enlive and enfocus
templates. While I can make the two look the same namespacing issues would
still keep them from being shared. The two sets of macros
generated different code so using them interchangeably would be difficult
unless you could swap out the namespace on the cljs compilation.

On Mon, Jul 23, 2012 at 9:57 AM, Creighton Kirkendall <[email protected]

wrote:

For my sites I am not using enlive, all rendering is happening on the
client side. So, I have not ran across this issue. That being said I can
certainly see the need for this. I may have something late next week for
you play with. It depends on how much time I get to work on things this
week.

CK

from enfocus.

Yes, I know.

I'm using cljsbuild's 'crossover' feature to add .cljs files from specific .clj namespaces. I'm pretty sure I can jimmy in some additional transformations to the code when this copying happens. Changing the namespace is, of course, trivial to do in this instance. And it's well worth the upfront investment!

Also, there are other options such as CLJX: https://github.com/lynaghk/cljx.

Shared templates can be incredibly handy... one example from our own wishlist: a websocket implementation where you have passive read-only clients receiving html from the server (using the server templates) as other read-write clients produce content (using client templates) and pushing just the data up.

For me, right now, it's all about being able to use the REPL in Emacs and midje/midje-mode :-)

from enfocus.

Nice! I had not seem cljx.

CK

from enfocus.

I took a slightly different route on this and decided to implement the enlive syntax first. I added support for basic enlive selectors. It does not support selector groups yet but supports almost all the enlive selector functions. Only one is not supported "has" because it isn't in the css selector spec.

To use pull and build from the domina-migration branch and add the following to your namespace declaration.

(:use [enfocus.enlive.syntax :only [attr= attr-starts attr-ends attr-contains ...]])

Hope this helps let me know if you run into any trouble I have not tested this as much as I would like yet.

from enfocus.

@robert-stuttaford were you able to test out the enlive syntax support I added?

from enfocus.

I was able to convert all my selector code to :symbols instead of "strings". All of my selectors are simple; tag or #id or .class. I didn't need to use enfocus.enlive.syntax at all.

It works 100%!

Thanks for this. It'll make using these templates with enlive that little bit easier. Of course, I'll still need to split out the defsnippet/deftemplate code from the defaction code, and make sure I'm not including any em/listen calls in my templates :-)

from enfocus.