Fork me on GitHub
#ldnclj
<
2015-10-27
>
agile_geek07:10:50

@gjnoonan: alright. How’s things with you?

gjnoonan07:10:18

Aye not too bad

thomas09:10:19

I wached the devcard video the other day and was intrigued by it

thomas09:10:29

going to give it a try later this weel

agile_geek09:10:41

@thomas: I haven’t had time to look at it but I’d be interested to have your opinion on what and how to use it as this alludes me.

gjnoonan09:10:46

@agile_geek: I’d use it as a living breathing interactive style/component guide, Both as you’re developing a ui, seeing how your components are in different states, and after

agile_geek09:10:55

@gjnoonan: I worry about separation of production code and test/documentation code and in Bruce Hauman’s video it wasn’t clear to me how this is ensured?

thomas11:10:42

@agile_geek: I don't see that problem at all. We use our customers for testing all ready. lets make it a bit easier for them 😉

agile_geek11:10:59

@thomas: so you would expose the devcards UI to the customers?

thomas11:10:34

if it helps them with testing the product why not 😉

agile_geek11:10:01

@thomas: I suppose it would be useful for customers that want to opt in to providing feedback and if it could be hidden from most customer who don’t carer fair enough. Not sure how devcards UI works but suspect it’s tied into Figwheel and only displays through the Figwheel port so not sure how you switch it on for normal deployment. I think you can invoke it programmatically so I guess you could have ‘easter egg’ links/URLs that displayed it?

thomas11:10:17

@agile_geek: I suspect you misinterpreted my smilies... it was meant to be tongue-in-cheek

thomas11:10:01

but sometimes it feels like we do let our customer test our code