This looks great - my only peeve - you had to release this now I have
just finished my om app and moved onto the back end :).
On 2 March 2015 at 20:08, Daniel Woelfel dwwoel...@gmail.com wrote:
Om-i (pronounced Oh, my!) provides useful aggregate info about the
rendering performance of your Om
Phalanges, library for working with JavaScript keyboard events is now 0.1.5.
This release fixes a small problem under advanced mode compilation.
https://github.com/spellhouse/phalanges
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You
How difficult is it to move an existing project into a template like this?
--
Jonathon McKitrick
On Mon, Mar 2, 2015 at 8:43 AM, ducky rohit.aggar...@gmail.com wrote:
You can have a look here:
https://github.com/reagent-project/reagent-template
The reagent-template has a flag for
Here's what I'm currently trying and failing with:
(defn new-id
([]
(str container- (gensym)))
([id]
(str container- id)))
(defn new-node
[id]
(- (dommy/create-element div)
(dommy/set-attr! id id)))
(defn append-node
[node]
(dommy/append! (dommy/sel1 js/document :body)
You can have a look here:
https://github.com/reagent-project/reagent-template
The reagent-template has a flag for generating basic testing setup.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are
I suggest that you generate a project with testing using reagent-template and
then inspect its project.clj and the test folder to see whats needed.
It shouldn't be difficult to add the necessary things to your project.
--
Note that posts from new members are moderated - please be patient with
You are going to need to talk to David Nolen about that. He decided that this
should be handled in a separate issue than [1].
The implementation in shadow-build [2] (and my original patch) properly support
:refer but I currently do not have the time to create a revised issue/patch for
CLJS
On Monday, March 2, 2015 at 3:17:32 PM UTC-5, Daniel Woelfel wrote:
Om-i (pronounced Oh, my!) provides useful aggregate info about the
rendering performance of your Om components.
With a few lines of code, you can add meaningful performance instrumentation
to your Om app.
Setup
Om-i (pronounced Oh, my!) provides useful aggregate info about the rendering
performance of your Om components.
With a few lines of code, you can add meaningful performance instrumentation to
your Om app.
Setup information is in the README: https://github.com/PrecursorApp/om-i
You can see it
