Fork me on GitHub
#re-frame
<
2016-12-05
>
andre11:12:57

is there any re-frame code template for intellij?

andre11:12:09

for example regfx, regdb, regsub, regcfx, it will be very helpful

tord11:12:06

I'm doing front-end work for the first time in a while. Since the cljs ecosystem moves so fast, I have to ask: What's the state of the art recommended way to use re-frame with devcards these days?

sandbags11:12:43

I seem to be having strange occasional issues with caching of old versions of components. Reloading the page doesn’t seem to help. I can’t quite figure out what is going on.

andre11:12:58

try hot reload

sandbags11:12:57

hot reload, you intrigue me

sandbags11:12:05

can’t seem to find that in the docs

sandbags11:12:23

how does that work?

andre11:12:29

clear cache in chrome ^)

sandbags11:12:33

in this case lein clean & a restart did fix it

sandbags11:12:50

thought i had missed some neat re-frame thing 🙂

sandbags11:12:57

i wonder what triggers this

andre11:12:27

i have issues with the cache too, in the last versions of Chrome

andre11:12:01

so, i just do hot reload every time

sandbags11:12:06

Ah, good to know its not just me

sandbags11:12:16

btw… it would be useful to be able to change the re-frisk font

sandbags11:12:36

also, when an event is not selected to hide the event section and expand the db section

sandbags11:12:39

to fit more stuff on

sandbags11:12:15

oh that’s weird, the re-frisk tree handles have stopped working

sandbags11:12:55

re-opened the window and they’re fine… not sure what happened

andre12:12:20

i've this issue on the mac in chrome in the full screen mode

andre12:12:44

i don't know what is it

sandbags12:12:05

Oh well… the things we put up with in this modern age

sandbags14:12:02

hrmm… the caching problem seems to be pretty bad… i updated to Chrome 55 yesterday i wonder if that’s what triggered it

sandbags14:12:14

using ctrl+reload seems to fix it but wtf...

pesterhazy14:12:02

@sandbags try a different browser; if the sale version disappears, it's probably browser caching

pesterhazy14:12:20

oh didn't notice the last messages

si1415:12:06

congratulations to the re-frame team, you are doing a wonderful job

cmal16:12:32

Amazing! I've just found the docs and learned so much from that.

cmal16:12:10

What an amazing thing I could imagine, if one day I could join such a team and learn from those huge people.

sandbags17:12:10

@andre is there any way a plugin could be implemented for re-frisk that could make more sense of [object Object] on a case-by-case basis?

sandbags17:12:57

i know we talked briefly about making it more readable, but I am wondering (in my case they are all a particular kind of record) if there’s a way to make them more useful

sandbags17:12:41

i should probably see if i can grok the re-frisk source code

sandbags18:12:07

this caching thing is starting to get quite irritating

sandbags18:12:44

Okay not sure of the best way to think about this. User arrives at a view ‘A'. 30s later the view should change automatically to another view ‘B’. So dispatch an event 30s after the first view is rendered. What I’m not sure about is where the call to setTimeout (nothing cljs specific here) should be made. Should it be an Effect of the event handler for the event that set the view to A? It sounds right when I say it out loud.

sandbags18:12:09

oh dispatch-later is already there !

andre18:12:24

i was thinking about this too, And I decided that the view makes the action, instead of the user, so i call setTimeout in the view's state

sandbags18:12:49

i thought about that… it seemed counter to the component as pure-function theme

andre18:12:48

about [object Object] this functionality inside data-frisk-reagent library wich re-frisk is using, there are a lot of work where, i thinking to fork it

sandbags18:12:22

is it nasty in there?

sandbags18:12:00

Hrmm… what to do when your :dispatch-later doesn’t...

sandbags18:12:25

okay so different puzzle: view is presented user can either advance to the next view with a button or, after time-out, the view is advanced automatically. I’m not sure if I should be thinking about how to cancel the dispatch-later or whether I should be dispatching an event that checks if the view is already advanced an nop’s if it is.

sandbags18:12:57

i guess the latter is probably easiest...