[15:29] <hatch> uiteam I still need two qa's and reviews https://github.com/juju/juju-gui/pull/664
[15:29] <kadams54> hatch: taking a look
[15:29] <hatch> thanks
[15:29] <rick_h_> Makyo: can you look at ^ as well please?
[15:29] <hatch> it needs a real env qa
[15:37] <Makyo> Sure
[15:41] <hatch> thanks guys
[15:49] <bac> hatch: you going to land a juju-gui branch soon? let me know when you do and :shipit:
[15:49] <hatch> bac: the doc one wasn't good enough?
[15:49] <hatch> or do we need another test?
[15:50] <bac> hatch: another, i didn't have the site setup for comingsoon to get built properly
[15:50] <hatch> ohh ok
[15:51] <hatch> one is getting qa's so hopefully that'll pass ok and it can be landed
[16:21] <kadams54> Makyo: are you QAing hatch's PR in a real env?
[16:21] <Makyo> Yeah
[16:22] <kadams54> I gave it a whirl but ran into problems. Trying to decide if I should try to wade through them or throw my hands up and just review.
[16:30] <hatch> kadams54: you should really just work in Ubuntu :)
[16:31] <kadams54> Some day
[16:34] <hatch> I made a small change to my tests and now they hang
[16:34] <hatch> :/
[16:38] <hatch> iphone users - can iphones auto sync photos to icloud?
[16:39] <teslanick> Yes
[16:40] <hatch> mom has an old iphone which she says no longer syncs to icloud
[16:40] <hatch> wanted to make sure it ever did ;)
[16:41] <teslanick> Pretty sure all my photos sync to icloud. Actually, it's all the images I put in my photo library, which is a pain. There are a few meme pictures in my "photo album" now. :|
[16:41] <hatch> haha
[16:43] <hatch> kadams54: did you push your branch? I dont' see it
[16:49] <kadams54> hatch: https://github.com/juju/juju-gui/pull/666
[16:49] <kadams54> PR#666 - ominous.
[16:50] <teslanick> HALLOWEEN WAS WEEKS AGO
[16:50] <hatch> well 666 is only ominous if you believe in the most recent religions and not the ones which the new ones were based on
[16:50] <hatch> (old roomie was a religious studies major) 
[16:50] <hatch> :P
[16:51]  * hatch <----- buzkillington
[16:52] <teslanick> Note that the real "number of the beast" or whatever is 616. The current "666" is a translation error.
[16:52] <hatch> oh interesting
[16:52]  * hatch gets 616 shirts made up for the emo kids
[16:57] <jrwren> 616 is a nearby areacode. grand rapids, I think.
[16:57] <hatch> are they all deamons?
[16:57] <teslanick> well there you go.
[16:57] <hatch> horns, red
[16:57] <hatch> you know the type
[17:01] <kadams54> hatch, Makyo: crap, sorry, just realized I pushed the wrong branch for that PR. Hold off on QA for a few minutes while I straighten things out.
[17:02] <hatch> kadams54: np I'm still reviewing huws 
[17:02] <hatch> yours got bumped ;)
[17:08] <rick_h_> hatch: you see http://www.fse.guru/2-years-with-angular ?
[17:08] <hatch> I have not
[17:08] <hatch> I will read it later though
[17:23] <hatch> kadams54: you pulled that PR down?
[17:24] <hatch> oh I thought you were just going to update it
[17:24] <hatch> :)
[17:24] <hatch> nm, ping when ready
[17:24] <kadams54> hatch: Yeah, https://github.com/juju/juju-gui/pull/667
[17:24] <hatch> cool 
[17:26] <hatch> kadams54: so the status bar seems a few pixels too high in it's little box 
[17:26] <kadams54> Makyo: ^ New PR ready for QA.
[17:26] <hatch> does it look like that to you too?
[17:26] <hatch> maybe it's just an illusion :)
[17:27] <kadams54> hatch: No, not particularly.
[17:27] <kadams54> FWIW, I didn't change any CSS for this - just shifted stuff around in the HTML.
[17:27] <kadams54> So visually the status bar is the same.
[17:27] <hatch> That add units header sure looks bad now haha
[17:29] <hatch> kadams54: so the scale up container element...it was missing before?
[17:29] <hatch> was it just working by chance?
[17:29] <kadams54> No, wasn't working by chance.
[17:30] <kadams54> The container element was a new div rather than an existing one.
[17:30] <kadams54> serviceOverview appended that div into its container, which guaranteed that it would always come first.
[17:30] <kadams54> Since I needed the status bar div to come first, I had to switch to having a pre-existing placeholder div which would be passed in as the container to scaleUp.
[17:31] <kadams54> hatch: Your gripes about the Add Unit header are worth mentioning to luca. I just double-checked the mocks attached to the bug and there's no header there. The status bar is almost merged with the scaleUp UI.
[17:32] <kadams54> hatch, luca: here's the mock: http://cl.ly/image/1C1c0i1k0Q2e
[17:32] <kadams54> And here's the current impl: http://cl.ly/image/2U3D3X0y0N3r
[17:32] <kadams54> I don't think it would be too hard to pull the header out as part of this branch.
[17:33] <hatch> well you now have 2 +1's so might as well just land it and we can follow-up late
[17:33] <hatch> r 
[17:33] <luca> kadams54: well, it’s positioned better at least :)
[17:34] <hatch> luca:  you'll have to take a look once it lands, the header kind of looks out of placed
[17:34] <hatch> it doesn't really look like it 'belongs' to anything
[17:35] <luca> kadams54: hatch Makyo we did come up with a new way of displaying this in Nuremberg
[17:35] <hatch> yeah? 
[17:35] <hatch> have any mocks to look ati?
[17:35] <luca> kadams54: hatch Makyo I haven’t wireframed it yet but we made some great improvements
[17:35] <hatch> ohh ok
[17:35] <kadams54> OK
[17:35] <hatch> I know it's been a tough problem to solve
[17:35] <luca> kadams54: hatch Makyo no…and I remember now that it was actually with Huw
[17:35] <luca> i’ll send my notes on it
[17:36] <hatch> huw was in nuremberg?
[17:36] <kadams54> luca, hatch: for what it's worth, here's how things would look if I just dropped the <h2>: http://cl.ly/image/470F3H3f1n1d
[17:36] <hatch> or are you thinking brussels?
[17:36] <hatch> heh name dropping destinations
[17:36] <hatch> :P
[17:36] <kadams54> I prefer that and it's a simple change, esp. if we're going to rework that shortly.
[17:37] <hatch> kadams54: need bigger shot
[17:37] <hatch> more context of the inspector :)
[17:37] <kadams54> http://cl.ly/image/293x1t170a24
[17:38] <hatch> yeah that's much nicer imho
[17:39] <hatch> kadams54: I also see your cache is broken again ;)
[17:39] <kadams54> Yes
[17:39] <kadams54> Eternally
[17:39] <hatch> and your fonts are way more bold
[17:39] <hatch> very odd...
[17:39] <kadams54> I wonder if that's just Chrome/Mac
[17:41] <kadams54> hatch, Makyo: pushed the dropped header.
[17:41] <luca> kadams54: hatch I have to run but I sent the info via peeps
[17:41] <kadams54> I gotta run for my doctor appt. but will get this landed and finish my other QA after.
[19:54] <hatch> rick_h_: I shared a vid on G+ this weekend about some really cool stuff coming in chrome wrt offline/app-like performance
[19:54] <hatch> a lot of which would really speed the gui up
[19:54] <rick_h_> hatch: yea, I have been meaning to look at it
[19:54] <kadams54> rick_h_: you asked me to QA a card in standup, but now I forget which one…
[19:55] <rick_h_> kadams54: I think we're ok. I think it was storefront and I looked at it and have questions/etc
[19:56] <kadams54> OK. Starting in on the switchboard integration.
[19:57] <teslanick> hatch: Is that serviceworker stuff?
[19:59] <rick_h_> man, the wind is trying to huff and puff and blow my house down
[19:59] <kadams54> rick_h_: yeah, it knocked my recycling over. My porch is a mess of plastic and cardboard right now.
[20:07] <hatch> teslanick: yup
[20:08] <hatch> uiteam - they are starting on my place so I may or may not get kicked offline :)
[20:08] <teslanick> This is pretty impressive - http://www.youtube.com/watch?v=px-J9Ghvcx4
[20:08] <kadams54> hatch: geez, is your fiber under perpetual construction?
[20:09] <hatch> kadams54: no this time it's new gas meter
[20:09] <hatch> and power meter
[20:09] <hatch> unless they run into issues
[20:09] <hatch> so...yeah
[20:09] <kadams54> Like cutting your fiber
[20:09] <kadams54> ;-)
[20:09] <hatch> teslanick: yeah that demo is awesome
[20:09] <hatch> kadams54: lol exactly
[20:09] <kadams54> teslanick, hatch: pretty sweet
[20:09] <hatch> teslanick: serviceworker - what appcache was supposed to be ;)
[20:10] <hatch> there is also some really cool manifest stuff wrt meta tags
[20:10] <hatch> so that we don't need to put 100 meta tags at the top of every page
[20:11] <jrwren> we have 50+mph winds right now. I'm amazed that I have power.
[20:11] <hatch> nice!
[20:11]  * hatch grabs kite - heads to Detroit
[20:12] <jrwren> its frame had better be made of something strong.
[20:12] <rick_h_> Wind
[20:12] <rick_h_> SW 28 mph gusting to 50 mph
[20:13] <hatch> bac: I'm about to shippit a branch
[20:13] <hatch> jrwren: no frame :)
[20:14] <hatch> jrwren: http://www.kittyhawk.com/wp-content/uploads/2012/02/L8G0244-e1328583281953-780x300.jpg
[20:14] <hatch> just a random pic 
[20:14] <hatch> it's like an airfoil - it uses the airflow to inflate 
[20:15] <jrwren> hatch: whoa, cool.
[20:15] <teslanick> hatch: It's almost like having a real programming language helps you solve problems more effectively
[20:16]  * teslanick glares at CSS.
[20:17] <kadams54> jrwren: yeah, it helps to realize that when hatch talks about a kite, he doesn't mean the one we all played with as kids :-)
[20:20] <bac> hatch: kadams54 beat you to it.  let's see if his updates comingsoon properly
[20:21] <hatch> kadams54: jrwren haha no, mine are 5 - 14m of area :)
[20:21] <kadams54> bac: ah yes… hatch was too slow :-)
[20:21] <hatch> lol
[20:22] <hatch> teslanick: haha yeah I've spent many a unable to sleep nights nerding out on how to make a better css :)
[20:22] <hatch> so far I've come up empty
[20:23] <teslanick> A simple "box model shader" API, written for JS, that uses the "top down" model that React uses.
[20:23] <teslanick> SOLVING THE PROBLEM ONCE AND FOR ALL
[20:24] <hatch> ok well there ARE solutions to the problem - just none that I think are any better
[20:50] <bac> uiteam: great, http://comingsoon.jujucharms.com/juju-ui/version.js is updated for kadams54-away recent landing
[20:51] <rick_h_> bac: woot ty much!
[20:51] <hatch> nice! good work bac
[20:53] <bac> hatch: your blog post is nice but my install was much simpler as i blew away os x
[20:53] <hatch> ohh ok
[20:54] <hatch> yeah for ppl with new apple hardware you definitely don't want to do that if you want things to work :)
[20:54] <hatch> maybe 16.04?
[20:54] <hatch> lol
[20:54] <hatch> I don't even know where to start to write drivers for the webcam
[20:55] <hatch> and I'd imagine there aren't many new MBP users who run ubuntu who are also driver authors :)
[20:55] <bac> hatch: i plan to close the lid and just ssh to it
[20:55] <bac> hatch: don't plan on it being my desktop
[20:55] <hatch> I have an oldish unused mac mini that i'd like to turn into my work machine - but I find I leave my desk and work around the house too much
[20:56] <hatch> so I'm thinking to think of a workflow that will make it less painful
[20:56] <hatch> working over ssh is too slow for me
[20:56] <rick_h_> it depends on the kind of work
[20:56] <rick_h_> browser work is a bit harder for sure
[20:56] <hatch> yeah - and I don't do any browser work ;)
[20:56] <rick_h_> :P
[20:57] <hatch> I was thinking some kind of an automatic rsync
[20:57] <rick_h_> ugh
[20:57] <hatch> so as soon as the machine boots it syncs the home directory
[20:58] <kadams54> bac: woot!
[21:00] <hatch> rick_h_: I was also thinking of running a parallels vm on the mini, and on my laptop so when I leave I can copy it over
[21:01] <hatch> but that's probably worse than rsync lol
[21:10] <hatch> ffs promises
[21:10] <hatch> that is all
[21:12] <teslanick> ur doin' it wrogn.
[21:12] <teslanick> ;)
[21:13] <hatch> lol
[21:20]  * jrwren sings promises promises.
[21:22] <teslanick> hatch: http://2014.jsconf.eu/speakers/james-coglan-practical-functional-programming-pick-two.html - We disagree about Promises, but I think this is worth a watch even if you're a Promiseskeptic.
[21:23] <rick_h_> hatch: just remember, it's all about the implementation :P
[21:23] <hatch> lol - hey I think promises are awesome - just not ones which implicitly throw() 
[21:23] <teslanick> Promiskeptik. Darn.
[21:29] <hatch> I am actually somewhat interested about promise + generator combo
[21:29] <hatch> would be nice for us and large complex imports
[21:30] <hatch> s/and/with
[21:30] <teslanick> How do you mean?
[21:33] <hatch> lemme find the video
[21:33] <hatch> one sec
[21:33] <hatch> https://www.youtube.com/watch?v=qbKWsbJ76-s
[21:33] <hatch> sorry it's long
[21:34] <hatch> well 31min
[21:34] <hatch> but it does a better job outlining what I'm talking about :)
[21:34] <teslanick> Oh yeah, promises + generators is great. I was mostly curious about the large/complex imports part.
[21:34] <teslanick> I wrote some code that implements core.async-style channels and blocks using promises + generators.
[21:34] <hatch> ohh when people drop a 20+ service with many machines and stuff onto tha canvas
[21:34] <hatch> and we need to parse it all out, and deploy it
[21:35] <teslanick> Aha
[21:35] <teslanick> And there's a lot of asynchrony there
[21:35] <hatch> well async and sync haha
[21:35] <hatch> it's a syncy mess
[21:36] <teslanick> Here's what I was fooling with - https://gist.github.com/nhusher/9511044
[21:37] <teslanick> Channels have three functions: put, take, and close.
[21:38] <hatch> interesting I'll have to take a look later
[21:38] <hatch> right now I"m fighting with tests failing when run with the rest of the suite
[21:39] <rick_h_> hatch: when the export thing is landed let me know. I think it might be worth doing a release update after that on the gui
[21:39] <teslanick> Rough. I'll leave you alone
[21:39] <rick_h_> hatch: if we can squeeze it in cool, else we'll wait for next release. We're |--| close to our weekly cycle so no problem either way
[21:40] <hatch> rick_h_: that's done
[21:40] <hatch> and landed
[21:40] <hatch> I'm fighting with the charmstore stuff
[21:40] <rick_h_> hatch: oh, crap ok 
[21:40] <hatch> apparently the tests faill dramatically when I try and remove the icon stuff from v3 because so many of the tests rely on that
[21:45] <rick_h_> lol
[21:45] <rick_h_> yea, there was a test helper to be used to mock it out
[22:31] <hatch> Makyo: I've now removed all of the old iconpath stuff https://github.com/juju/juju-gui/pull/662
[22:31] <hatch> 33 files changed...oy 
[22:45] <rick_h_> hatch: so why does that code go away vs just getting updated?
[22:46] <hatch> not sure I understand the question
[22:46] <hatch> why did I remove it from charmworld.js?
[22:46] <hatch> so that it would fall on its face hard if anyone tried to use it :0
[22:47] <rick_h_> hatch: so why did you have to touch all those points
[22:47] <hatch> because those old places use a stubbed version of apiv3
[22:47] <hatch> so it's now a stubbed version of apiv4
[22:47] <hatch> different method name
[22:47] <hatch> iconpath to getIconPath
[22:48] <rick_h_> ok, I see so it didn't go away just needed a lot of rewording
[22:48] <hatch> oh no it's gone
[22:48] <hatch> I deleted the iconpath method from charmworld.js
[22:49] <hatch> all the tests are converted to use the new method in the new api
[22:49] <hatch> and everything in the code now uses the apiv4 method
[22:49] <hatch> so any icons being fetched are being fetched from v4
[22:50] <hatch> which also means this branch cannot land until the next v4 api update
[22:50] <rick_h_> working on getting it through CI now
[22:50] <rick_h_> darn mojo CI got me with a failure for some reason
[22:50] <hatch> yeah no problem - I don't want to land this branch until after we cut the next release
[22:50] <hatch> just to be safe :)
[23:02] <hatch> kadams54: 662 is ready for its final review and qa - but it won't be landed until after we cut the next release
[23:02] <hatch> so probably wednesdayish
[23:03] <kadams54> ok