Thanks for your feedback!
> As with the previous point this falls out the fact that we just use React DOM
> components directly. I'm not just not interested in providing something
> different over React's DOM bits.
That makes sense. What is somewhat surprising is that
React.DOM.h1({}, "Many", "words"); and
React.DOM.h1({}, ["Many", "word"]); both work, whereas
(om.dom/h1 #js {} "Many" "words") works, but
(om.dom/h1 #js {} ["Many" "words"]) does not
This may have something to do with your prior point about avoiding cljs->js
conversions, I don't know. Maybe both this and options-as-js-object could be
solved if the DOM functions were macros instead?
> On a related note, the build/build-all differences seem unnecessary to me,
> and personally, I would prefer a polymorphic build for the same reasons.
>
> This is mostly because of argument order issues. I don't feel strongly about
> it and no one has proposed how they might be unified.
build has [f cursor m] and build-all has [f xs m]. Is it possible to tell a
list of cursors from a cursor that is a list?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.
