Fork me on GitHub
#devcards
<
2016-08-10
>
timothypratley05:08:56

klispe would be pretty sweet 🙂

timothypratley05:08:48

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)

kauko06:08:40

So what exactly do you need devcards for?

timothypratley06:08:31

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

timothypratley06:08:51

^^ above is all in devcards

timothypratley06:08:59

Or maybe more to the point, for collecting cards?

timothypratley06:08:27

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

kauko08:08:56

Oh I meant for the slideshow thing

kauko08:08:25

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

kauko08:08:14

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

timothypratley13:08:36

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

timothypratley13:08:09

generally I just find devcards useful for everything clojurescript 🙂

timothypratley13:08:03

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

timothypratley13:08:19

http://g.recordit.co/poy3aiJqPx.gif sneak peek, nothing fancy, but fun to code