Fork me on GitHub
#hyperfiddle
<
2018-08-07
>
dogenpunk02:08:49

Hi, can I have beta? (matthew at a domain called http://matthew-m-nelson.com)

Dustin Getz16:08:51

Schema editor fixed yesterday, gifs are not yet HTML5

Dustin Getz16:08:28

@dogenpunk Hi Matthew, sure thing, hopefully this weekend or early next week

dogenpunk16:08:44

Great, thanks!

Dustin Getz16:08:58

@dogenpunk where did you find us?

dogenpunk16:08:48

Either through a long night of googling for info on datomic, or @ericnormand’s newsletter

miridius19:08:22

Hi @dustingetz, I'm going through the hyperfiddle tutorial/playing around at the moment if you want to video conference

Dustin Getz20:08:04

@miridius i do but ˆam on my way out the door to a pitch event, ping me next time, thank you for thinking to ask

👍 4
miridius22:08:44

Is there a way to add variables into a fiddle's query? I'm trying to build a search page and I got as far as creating a results page which lists every entity in the DB, but not sure how to let the user filter those results and/or provide inputs to the query itself

miridius22:08:03

I thought about treating each search the user performs as a new entity and saving the query text to the DB, which might actually have some cool implications e.g. for looking up search history. But I was wondering if there's a more ephemeral way to collect user input. I guess another way to ask this is whether there's a way to have some front-end state that can be interacted with

miridius23:08:02

Is there any reason to avoid making lots of fiddles? E.g. if I make one fiddle for each thing that I would normally make a separate reagent component for - which means anything more than 5-10 lines of hiccup would go in its own fiddle

miridius23:08:13

sorry if some of these questions are stupid... I'm still wrapping my head around things a little 😉