On Saturday, April 7, 2012 2:24:21 PM UTC-7, r0man wrote:
>
> Why do you think it is impossible to have the same API in Clojure
> and ClojureScript?
>
For instance, hiccup.core/html and hiccup.core/h cannot live in the same
namespace in ClojureScript if hiccup.core/html is going to be a macro, an
Hi Evan,
I think Hiccup is a also a good starting point for this. In fact
99% of the port is already working. The last thing I struggle
with is actually only cosmetics, like carrying over the meta data
with the arglist and documentation.
Why do you think it is impossible to have the same API in C
I think crate is about the closest that you're going to be able to get to
hiccup in practice. ClojureScript macros are written in Clojure, and thus
have to come from separate namespaces from the rest of the ClojureScript
code. So, it is not possible to just port hiccup to ClojureScript on a
v
Hi Chris,
yes I have seen crate. But I wanted something where I can share
the same view code and use it on the client and the server and
use the same api. I also think Hiccup's aproach to generate html
strings at compile time is quite nice. That way the
deconstruction of [:div#id.class] stuff can
Have you seen Crate?
http://github.com/ibdknox/crate
On Apr 7, 1:18 pm, r0man wrote:
> Hello ClojureScripters,
>
> I started to port the Hiccup library to ClojureScript. The goal
> is to have a port of Hiccup that has exactly the same api. This
> would make it possible to write views once (provi
Hello ClojureScripters,
I started to port the Hiccup library to ClojureScript. The goal
is to have a port of Hiccup that has exactly the same api. This
would make it possible to write views once (provided no platform
specific code is used), and run them on the server with Clojure
and on the client
