[13:28] <gary_poster> bac, benji, gmb, mumble/kanban in 2
[13:29] <gmb> Yep
[13:46] <gary_poster> gmb, could you add me to https://qastaging.launchpad.net/~malone-alpha please?  db hasn't updated that yet I guess
[13:46] <gmb> gary_poster: Sure.
[13:46] <gary_poster> thank you
[13:47] <gmb> gary_poster: I've added you and made you an admin.
[13:48] <gary_poster> thank you again
[14:27]  * gmb -> afk for a bit
[16:28] <bac> hi gmb
[16:28] <gmb> Hi bac.
[16:28] <bac> gmb: 90 sec mumble?
[16:28] <gmb> bac: Sure.
[16:33] <bac> gmb: when mumbling you're super loud and blown out
[16:34] <gmb> Yeah, I think it's because I set up Mumble with the built-in-mic but I'm now using my iphone earbuds. I need to reconfigure it.
[16:34] <gmb> Thanks for the heads-up.
[16:49] <bac> hurrah, i'm making an accordion with no external assets.
[16:50] <benji> yay!
[19:07] <benji> bac: I'm in need of a task.  Anything I can help you with?
[19:08]  * bac thinks
[19:08] <benji> gary_poster: here's my first cut of a "how to access the webservice from JS" document: https://dev.launchpad.net/yellow/JavaScriptAPIAccessDraft
[19:08]  * gary_poster looks
[19:09] <bac> benji: i'm wrapping up my task to include the gallery stuff.  i need to write up a quick wiki article about it.  after i push the branch you may want to have a look around.  other than that i can't think of anything ATM.
[19:10] <gary_poster> benji, I'll think about it in a sec.  one comment as I read: some APIs are exposed via collections
[19:10] <gary_poster> and I think we hope to have more of those
[19:10] <benji> bac: ok, thanks anyway.  I'd be interested in any feedback you have on https://dev.launchpad.net/yellow/JavaScriptAPIAccessDraft.
[19:10] <gary_poster> finding out where those are/how to use them is something that I wouldn't know how to do systematically
[19:10] <gary_poster> other than stare at interfaces and their annotations
[19:10] <benji> gary_poster: I don't know how those work, so I didn't include them. :)
[19:10] <gary_poster> which may be the only answer
[19:11] <benji> well, I got an idea from reading the code, but I didn't want to lead anyone astray
[19:11] <gary_poster> heh, ok, makes sense benji.  since that's a known gray area rather than a yet-to-be-discovered gray area, I recommend highlighting it as something that exists but that isn't explained here yet.
[19:12] <benji> good idea
[19:14] <gary_poster> will get back to reading the doc, but here's one small useful thing to do: look at comment #6 on https://bugs.launchpad.net/launchpad/+bug/649252
[19:14] <_mup_> Bug #649252: No unsubscribe link in emails for non-verbose bug notifications <easy> <email> <lp-bugs> <story-better-bug-notification> <Launchpad itself:Triaged by yellow> < https://launchpad.net/bugs/649252 >
[19:15] <gary_poster> benji, you could do that pretty quickly, and move a card along in gmb's lane
[19:15]  * benji looks
[19:17] <gary_poster> benji, back to the draft: "The URI is the webservice entity URI, not a URI normal human-readable web page" I think maybe there is a helper to convert one to the other?  Maybe that was just a desire that someone expressed once rather than something we actually have...
[19:18] <benji> gary_poster: I'm not aware of a way and a cursory look at the JS client doesn't reveal one.
[19:18] <gary_poster> ok, benji :-/  must have been a desire then
[19:18] <benji> maybe you're thinking of the reverse; there is now a web_link attribute on most resources that points to a human-readable web page
[19:18] <gary_poster> huh
[19:19] <gary_poster> well, I was thinking what I said, but maybe I just misunderstood
[19:20] <gary_poster> benji, this is a good start, thank you.  How do you know what the success JSON will look like?  Or...is that saying that it will generally give you "instances" of webservice representations of server objects, and you can do...the usual things, whatever the usual things are, on those objects?
[19:21] <gary_poster> In general, that's the part I think you probably have an answer for that I still don't understand after reading
[19:23] <benji> gary_poster: Is your question: what does the JSON returned by retrieving a resource look like?
[19:24] <gary_poster> benji, well, what are those success callbacks supposed to do, benji.  If we are supposed to handle the JSON, then I want to know what the JSON looks like.  If the JSON is handled for us, then I don't care.  But generally, if I call a named operation, how do I know what to expect to do about it in the success callback?
[19:24] <gary_poster> heh, sorry for double
[19:25] <benji> I think you accidentally a word.  ;)
[19:25] <benji> the success callbacks get an object, the JSON attributes are mapped into object attributes.
[19:25] <benji> I tried to say that but may have failed.  I'll rewrite that bit.
[19:26] <gary_poster> but what are those objects?  You look in the WADL to find out?
[19:27] <benji> oh!  I don't know what you look at for them, I've just been looking at the JSON or HTML generated by them.  I'll see if there's something better than that and write it in.
[19:28] <gary_poster> cool
[19:34] <gary_poster> http://developer.yahoo.com/yui/articles/skinning/
[19:34] <gary_poster> http://developer.yahoo.com/yui/3/examples/slider/slider_skin.html
[20:34] <gary_poster> benji, moved things around so that your card could be in feature work 1 where it belongs.
[20:35] <benji> ok
[23:11] <gary_poster> night