Clojurians Log v2

To be clear, it's rendering fine despite the warnings. The css transform just isn't being applied. I'm mainly just trying to do a sanity check that I'm getting the Om part right before I ask CSS people if it could be an issue with styling form elements in particular.

@sophiago looking at it briefly you’re passing a CLJS map instead of a JS object to slider

missing a #js

around line 34?

i'm getting several warnings around there, so suspect that's the problem.

yeah

also the apply call looks fishy to me

actually you shouldn’t need #js there

since you’re passing it to an Om component

you’re just not using the style prop you’re passing in slider ever though

so it’s normal the CSS transform is not being applied

should i be calling slider as a function literal inside apply? and also setting :transform as a prop?

probably

sorry I wasn’t clear on the apply stuff

is it not necessary?

I meant just:

(dom/div nil (slider ...))

ah ok

also, to be clear...i'm unsure whether a matrix transform will even work on this element...that's why i hate CSS 😛

i'm getting a runtime error just using ui as if it's a function call on line 25. but i believe you told me a while ago that's essentially how to use the defui macro works under the hood?

@sophiago you still need to create a factory for it

and the factory is what you’re supposed to call

ok, thanks. i was originally using a factory but didn't realize i needed to use one in order to modify props like this

@anmonteiro does the edited snippet above look correct to you?

trying to get some feedback from the css people on freenode about transforming form elements, but

apparently css isn't the issue here: https://jsfiddle.net/entuland/pLet0yb1/

so now back to what i'm doing wrong with Om 😞

@sophiago In om.next, isn't it just :key and not :react-key?

hello! I was trying to find examples of combining om.next and datascript.. I see the use of a DataScriptStore implementing some protocols here https://github.com/swannodette/om-datascript/blob/master/src/om_datascript/core.cljs (2 years old) which seems "more complete" but the current wiki shows a different strategy: https://github.com/omcljs/om/wiki/DataScript-Integration-Tutorial (and I heard somwhere that set-query! would not work with datascript as state). Anyone care to comment if there is a current ref. best practice? Anyone used either implementation in production? trying to gather knowledge about past experiences

I'm aware about some of the trade-offs.. to perhaps favour keeping Om.Next state simply as an atom of projected data.. Considering those trade-offs right now 🙂

@peeja: its possible to have multiple children of a component where some share idents.. not typically but certainly possible 🙂

Yeah, I guess that's true.

@matthavener Yes we use that approach all over our app

and your keyfn is some combination of ident + other stuff?

I believe Om.next set’s a default one, we haven’t had any problems just not setting it.