On Monday, June 23, 2014 11:59:45 AM UTC+10, David Della Costa wrote:
> > itself in the right absolute position if the window resizes).  Its
> 
> > not that you can't do this in OM, of course, but, as I understand it,
> 
> > you'd have to merge the window dimensions into the main atom, and
> 
> > meaning the "reusable" popup component would require that every
> 
> > app-state had these window dimensions at the same place (cursor).
> 
> > Feels a bit hacky to me.  (If I've lead you astray here, and there's
> 
> > a better way to create such a reusable component in OM, I hope
> 
> > someone will correct me.)
> 
> 
> 
> Each Om component has local component state, just as in React.  You
> 
> certainly don't have to merge everything into the global app data as you
> 
> describe, and UI concerns like this are exactly the use-case for local
> 
> state.  This is all described in the tutorials and docs.
> 
> 
> 
> https://github.com/swannodette/om/wiki/Documentation
> 

Yes, I've found myself crawling over those docs a few times.  :-)

So, if I understand you correctly ... to create a reusable, absolutely 
positioned popup component, you are suggesting something like this: 
   - in IDidMount, hook the window or <body> for "onresize" events
   - in IWillUnmount, unhook the listener on the way out. 
   - when a resize event comes through, use "setState!".  Does this trigger a 
re-render of the component? 

--
Mike


-- 
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.

Reply via email to