Devcards aims to provide a visual REPL experience for ClojureScript
timothypratley 2016-08-10T05:56:56.000166Z

klispe would be pretty sweet 🙂

timothypratley 2016-08-10T05:57:48.000167Z

I've taken to wrapping my cards in an example macro which IMO pleasantly shows the code as well as the card (but it isn't editable, klisp or similar would make that dream real)

kauko 2016-08-10T06:06:40.000173Z

So what exactly do you need devcards for?

timothypratley 2016-08-10T06:12:31.000174Z

Hmmm not sure I understand the question... for developing! 🙂 and showing people stuff 🙂

timothypratley 2016-08-10T06:12:51.000175Z

^^ above is all in devcards

timothypratley 2016-08-10T06:14:59.000176Z

Or maybe more to the point, for collecting cards?

timothypratley 2016-08-10T06:16:27.000177Z

(I'm probably not following what you mean 😞 )

kauko 2016-08-10T08:50:56.000178Z

Oh I meant for the slideshow thing

kauko 2016-08-10T08:52:25.000179Z

If you want slides - which basically means a component that can take its contents and the next slide as some kind of config / parameter - I don't really see what devcards adds

kauko 2016-08-10T08:54:14.000180Z

Devcards is designed for rendering (react) components you've defined somewhere else, giving them different kinds of arguments, and seeing history and how the arguments change when the component is manipulated

timothypratley 2016-08-10T13:50:36.000182Z

@kauko oh gotcha. Right now I'm updating some docs for reanimated and working on a series of animated scenes for a youtube video

timothypratley 2016-08-10T13:51:09.000183Z

generally I just find devcards useful for everything clojurescript 🙂

timothypratley 2016-08-10T13:52:03.000184Z

I like being able to intermingle components and cards in the same file, and have it all get sorted out in the wash.

timothypratley 2016-08-10T13:54:19.000185Z sneak peek, nothing fancy, but fun to code