Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Devcards – Taking Interactivity to the Next Level

rigsomelight.com

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Devcards – Taking Interactivity to the Next Level

#11

Post by brucehauman »

ezisezis wrote: post #8
ezisezis wrote: post #3

Ever since I first talked to Bruce about this(and other Om/React users), I've thought that this type of approach could lend itself really well to visual image based regression testing. The other cool thing is that with Om you can serialize record Om state transactions. By doing this you could see how people are using specific components. Perhaps you could cycle through the last 10 users or the 10 most common interact…

To expound on this, what about having cards, ie single components, be linked to a graphical/interaction test CI-suite. I know this is sort of pie in the sky but it gets me thinking.

Actually, that's not pie in the sky, running selenium against a set of cards would work great. And may be an easier env to work in than the actual main app.

Re: Devcards – Taking Interactivity to the Next Level

#12

Post by drcode »

brucehauman wrote: post #10
drcode wrote: post #9

This approach has a lot of appeal- I am building lots of Om components that change over time, and things that change over time are hard to debug. With this approach, I could put in different devcards for snapshots in time for my components, and debug those in a static manner, and see them all in front of me at the same time. The one additional feature I'd like to see (or maybe it exists already, I just looked at the…

I have been working towards that. If you are still following the queue of messages that you mentioned a while back, then you could supply each card instance of your "program" with the list of messages that you need to get to the state you need. So you could make a loop to create the list of cards you want to look at.

I think I might make devcards part of my regular workflow.

It seems obvious now, seeing devcards, that the ease with which Om/React can render "snapshots" makes this the most sensible way to develop for Om.

Re: Devcards – Taking Interactivity to the Next Level

#14

Post by brucehauman »

KingMob wrote: post #13

Bruce, how does this compare with Chris Granger's plans for Aurora? And, have you considered making this a Light Table plugin?

I have only seen Chris's Strange Loop presentation. So I don't know much about his plans for Aurora. I do agree that the time is ripe for a visual programming language built in the browser.

I haven't looked into LT integration just yet. But I am open to that of course. Sounds like an absolutely great idea.

Devcards is still super new. And I hoping that people really think about what this means in their particular workflows and hopefully reintegrate knowledge back into Devcards.

Re: Devcards – Taking Interactivity to the Next Level

#15

Post by brucehauman »

drcode wrote: post #12
brucehauman wrote: post #10

Earlier quoted context omitted.

I have been working towards that. If you are still following the queue of messages that you mentioned a while back, then you could supply each card instance of your "program" with the list of messages that you need to get to the state you need. So you could make a loop to create the list of cards you want to look at.

I think I might make devcards part of my regular workflow. It seems obvious now, seeing devcards, that the ease with which Om/React can render "snapshots" makes this the most sensible way to develop for Om.

I'd love to hear what your experience is and/or see examples.

Re: Devcards – Taking Interactivity to the Next Level

#16

Post by KingMob »

brucehauman wrote: post #14
KingMob wrote: post #13

Bruce, how does this compare with Chris Granger's plans for Aurora? And, have you considered making this a Light Table plugin?

I have only seen Chris's Strange Loop presentation. So I don't know much about his plans for Aurora. I do agree that the time is ripe for a visual programming language built in the browser. I haven't looked into LT integration just yet. But I am open to that of course. Sounds like an absolutely great idea. Devcards is still super new. And I hoping that people really think about what this means in their particular wor…

Cool, thanks for making this, I'm going to try to check it out soon.

BTW, I assume you've seen Bret Victor's talks, but if not, you absolutely must, especially Inventing on Principle.

Post reply on HN