@sandbags hi, where are you looking the homepage? https://github.com/flexsurfer/re-frisk here is 0.3.1 the latest version with the fixed scroll, but i would recommended using external window debugger, because more features, i want to get rid of panel, it's only need for clojure/conj 🙂

@andre sorry i think i must have added the dependency earlier and only used it yesterday, then thought i’d added it yesterday when i ran lein ancient

My brain working hard not to make it my fault 🙂

When you say “use external debugger” I am not sure if you mean “use something else, not re-frisk” or “use the re-frisk in its own window” option

it's because my english, sorry, i mean use the re-frisk in its own window

there are more functionality for the reframe, events , and state export

@sandbags ^

@andre yep.. i have used the window and it’s cool, getting the events was a nice bonus

@andre thank you for making re-frisk … it’s handily replaced my crappy “debug view” in the app

glad to hear , thank you, in plan i whant to add re-frame effects and subscribtions lists

@andre one suggestion though, if you’ve a moment, if you can replace [Object Object] (I’m going from memory here) with something shorter it would help

I have some cases where i have maps with a lot of keys that are Clojure records that end up being represented [Object Object] and it takes up a lot of space visually when some short-hand would be better

yes, good idea, because there can be something like generated js functions body

It’s a pity I can’t make those records more useful… they are basically wrappers for an id

i'll create the task for enhancement

as a design choice i often question their value

but, yes, that would be useful thank you

@andre i can think of one instance in which the panel approach could be very useful: if you could “focus” the panel on a specific sub-tree of db and turn it into a kind of “watch"

then you just have the value you are interested in, right in your visual focus where you want it

@sandbags so , there are alot of data that changing, but you want only watch some current value?

yes

ok, understand

for example i track both date and a day delta. When I was testing the code that updated them together i would have loved to be able to focus on the matching part(s) of the data structure

https://github.com/flexsurfer/re-frisk/issues/16

https://github.com/flexsurfer/re-frisk/issues/15

sweet, thanks … i admire your discipline!

@sandbags

(re-frisk.core/add-data :mywatcher (reagent.ratom/make-reaction (fn [](:data @re-frame.db/app-db))))

you need just specify :mywatcher keyword and :data path in the app-db

i know it's not user friendly but maybe will be helpful

@andre thanks, i will try that out!

How do I get to the updated arguments in :component-did-update?

For example:

(fn [foo]
  (reagent/create-class
     {:component-did-mount
      #(side-effect! foo)
      :reagent-render (fn [foo] [:div#foo])}) 

This doesn’t work when the foo args are updated

(double post from #reagent)

I am having a problem and I think I know why but I’m not sure what to do about it. Within my app-state I have a map one of whose values refers to a component that will represent the “main view”. Events can change the main view by updating this. What I used to do was use a keyword and I had a case statement like (let [view (…)] (case view :foo [foo/foo-view] :bar [bar/bar-view])) and so on (in reality a little more complex but that was the essence of it). I didn’t like that so I decided what if I just stuff the symbol for the component into the db, now I can just do (let [view (…)] [view]) which works except that when I update the view code the view is reloaded but I am still looking at the old component output. I now think it may be related to how code re-loading works and having the symbol in a data-structure I am some-how hanging on to the ‘old' component function whereas referring to the symbol directly yields the output of the updated component function. Maybe... Anyone know for sure what is going on here? And can anyone suggest how I can dynamically switch views from the database without hard coding a lot of symbol lookup? Was thinking maybe of using :foo/foo-view and trying to turn that into a symbol at run-time. Would love to hear, how are other people solving this problem?

I’m wondering if the “resolve by name” approach is feasible in ClojureScript since it doesn’t have ns-resolve and I see suggestions the Closure compilers optimisations make it unworkable.

@sandbags I think what you want is store the symbol in the app-db like 'foo/fooview (note the quote) and when you take it out, resolve that symbol to the actual view

ah, of course… i am probably storing the actual JS function

wait... does cljs have resolve ?

I don’t think so as resolve is a short-hand for (ns-resolve *ns* …)

I found cljs.analyzer.api/resolve but the doc is 404...

hrmmm if i can’t use resolve i can’t use the symbol unless I am missing something obvious

i’m having a brain fade moment… how do I turn ‘foo/foo-view into foo/foo-view … it’s via ns-resolve right?

I believe so

sadly it looks like i might be back to my ugly case statements

that’s rather disappointing

but i am struggling to believe there is no more elegant solution to this…

@sandbags you can use a multimethod instead of case ... lets you declare the multimethod near where it is used, and define the render implementations wherever they belong

Ah so you mean I define a multi like main-view and a set of methods for each component view and use the keyword to switch on method

that’s nice!

@sandbags exactly - here's a compact example - https://www.refheap.com/124078

thank you, elegance achieved 🙂

awesome thanks for that

i would only use form-1 components with a multi-method though - i think you might find weirdness with form-2 or form-3 components

ah, that could be an issue

most of my views are form-(n>1)

and depend on subscriptions

remember that in re-frame 0.8 and above you can use subs efficiently in form-1 components... i think form-2 components are kinda obsolete now

form-2

oh

oh i do remember seeing some discussion of this

right, i guess i have some work to do

@sandbags have a look down the bottom of https://github.com/Day8/re-frame/issues/218 "It is now officially guaranteed that you can use subscribe in a Form-1 Reagent view function. This guarantee will officially be a part of the 0.9.0 release, but it already works in v0.8.0."

was the solution to using subs in form-1 simply to move them into the component function? Or was there other work you needed to do? (Essentially I am asking if I need to go look up where this was described or if the easy path is the right one)

ah, thank you 🙂

Oh cool, I love this multimethod solution~ 🙂 might refactor my code base...

yes i remember this issue now

@mccraigmccraig many thanks, again !

yw 🙂

works!

(not that i doubted you… but i doubted me!)

excellent, this is a really nice solution … i knew Clojure wouldn’t let me down 🙂

how would you choose between "passing down" data obtained from a subscription to a component and subscribing to the data in an underlying component directly? are there any non-obvious considerations?

I usually have the components subscribe directly because it could re-render seperately, if you pass data down, the whole thing would always re-render

on the other hand, this makes your components harder to decouple from your app, you'll need to write a stub for the subscribe/`dispatch` functions to test your component seperately.

@si14

Man, whoever gets these online is fast! Here's my talk from the Conj, only 2 hours from completion to youtube https://youtu.be/cDzjlx6otCU

@akiroz thanks a lot!