[00:00] <huwshimi> hatch: We've had the anchor div conversation so many times...
[00:00] <hatch> huwshimi when it makes sense yes
[00:00] <hatch> but in this case, it doesn't :)
[00:01] <huwshimi> hatch: Why not? This is a navigation item...
[00:01] <rick_h_> what's the case here? Is it going to viewNavigate?
[00:01] <hatch> because pjax is such a bucket full of issues since we don't use it
[00:01] <hatch> rick_h_ it probably will end up doing something along those lines
[00:02] <rick_h_> huwshimi: hatch actually, these tokens shouldn't nagivate on their own. THey should fire events that the machine view panel dispatches
[00:02] <rick_h_> this is part of why I like dumb widgets, it helps break down the questions of too-intelligent UI components
[00:02] <huwshimi> rick_h_: They currently do fire an event
[00:02] <hatch> huwshimi if you REALLY don't want to switch then you need to change all the event handlers to use e.halt()
[00:02] <hatch> because we need to basically stop anything and everything that makes them anchors else they will break the app in weird and fun ways
[00:03] <rick_h_> huwshimi: ok, yea. If it makes sense to appear clickable, I'm fine as long as there's a direct test that the event does not propogate
[00:03] <rick_h_> we've been bit by it before
[00:03] <hatch> oh...except the pointer....that's the only <a> related thing that needs to stay
[00:03] <hatch> so...many...times
[00:03] <hatch> I'd rather not have them at all
[00:03] <rick_h_> hatch: alt text? I guess you can alt text anything
[00:03] <rick_h_> I kept thinking there was something else
[00:03] <rick_h_> oh, tab/selectable
[00:03] <huwshimi> hatch: And make it tab-able. 
[00:03] <rick_h_> it breaks that UI badly
[00:04] <hatch> tab select is never going to work with the app anyways
[00:04] <rick_h_> I'm not 100% sure how much we NEED it here though as it's not really a form and I'm not sure how you'd select into the space to expect a good tab experience
[00:04] <hatch> we'd need to somehow maintain a tabindex order across all "widgets"
[00:04] <hatch> I've thought about it
[00:04] <hatch> it's possible
[00:05] <hatch> maybe for V5 :P
[00:05] <rick_h_> hatch: huwshimi I'd vote implementers choice noting the need for explicit stop test if the implementer chooses to go on with <a> 
[00:05] <rick_h_> hatch: lol
[00:05] <hatch> ok ok I'll settle for a test checking to make sure the event does not bubble outside of it's container
[00:05] <rick_h_> sound acceptable huwshimi ?
[00:06]  * hatch says that like he has some kind of authority in the matter
[00:06] <hatch> lol
[00:06] <rick_h_> hatch: well I'm saying 'vote'
[00:06] <rick_h_> we can make it a friday card, we've been down the road before and we've done both in the code base. 
[00:06] <rick_h_> I don't know either is 'wrong' but we've been bit and need safety checks
[00:07] <hatch> nope, actually huwshimi is correct in using it imho, but we don't use pjax....but we have pjax....so it's just a bug trap heh
[00:07] <hatch> maybe one of these days the yui guys will split router up so we can use only the parts we want
[00:07] <hatch> it's been on the books for a long time though
[00:07] <rick_h_> yea, and our app is a bit unique
[00:07] <rick_h_> it's not your standard CRUD app
[00:08] <hatch> we probably could do pjax with this new state stuff
[00:08] <rick_h_> create our own mold wheeee
[00:08] <hatch> haha
[00:08] <rick_h_> yea, if we could start over we could do things a bit diff for sure
[00:09] <hatch> 2.0.0 total greenfield? 
[00:09] <hatch> lol
[00:09] <rick_h_> lol
[00:09] <rick_h_> oh the lines of rewritten code
[00:09] <rick_h_> isn't the rule 'never rewrite' though?
[00:09] <hatch> honestly though once we get this state stuff done, the only real 'legacy' stuff is the double dispatch
[00:09] <rick_h_> I know I've fought that rule on my bookmark app a few times
[00:10] <rick_h_> hatch: yea, and mocha and the awful test setup
[00:10] <hatch> lol....that doesn't exist
[00:10] <rick_h_> next up...combo loader :P
[00:10] <hatch> haha
[00:10] <rick_h_> let's set our sights on the really hard fun changes :P
[00:10]  * hatch waits for design to add fullscreen back in
[00:10] <hatch> lol
[00:11] <hatch> I think the new state stuff will make it easier to do when they do though lol
[00:12]  * hatch turns off code brain
[00:12] <hatch> I think urls are making me bitter
[00:12] <rick_h_> hatch: all good, almost through
[00:12] <hatch> yeah maybe watching tv tonight I'll finish the tests
[00:12] <hatch> the code is all done and about 1/2 of the tests
[11:02] <rick_h_> mmorning
[11:04] <frankban> hi rick_h_ 
[11:16] <frankban> rick_h_: quickstart 1.3.1 is out, Robie should work on that today
[11:17] <rick_h_> frankban: awesome, thanks for the quick turn around on that. PPA-land here we come! :)
[11:17] <frankban> :-)
[11:17] <rick_h_> frankban: I've got maas and OSX support for quickstart on the list of topics/work items for the next cycle
[11:17] <rick_h_> frankban: let me know if there's anything else we should look at trying to do. I can't recall anything off the top of my head
[11:20] <frankban> rick_h_: we have some "nice to have" fixes, i.e.: bug 1292167, bug 1302382, bug 1255635 and bug 1287876
[11:20] <_mup_> Bug #1292167: apt-http-proxy needs to be documented <docs> <hs-arm64> <juju-core:Triaged by thumper> <juju-core docs:Fix Released by sinzui> <juju-quickstart:Triaged> <https://launchpad.net/bugs/1292167>
[11:20] <_mup_> Bug #1302382: Support lxc-clone in local provider <juju-quickstart:Triaged> <https://launchpad.net/bugs/1302382>
[11:20] <_mup_> Bug #1255635: Allow passing constraints to juju <juju-quickstart:Triaged> <https://launchpad.net/bugs/1255635>
[11:20] <_mup_> Bug #1287876: support optional extra config for bundle deployments <juju-quickstart:Triaged> <https://launchpad.net/bugs/1287876>
[11:21] <frankban> but maas and osx are more high priority
[11:21] <rick_h_> frankban: cool, some some maintenance time would be cool
[11:21] <rick_h_> but as far as bullet features for the planning it looks like those two
[11:22] <frankban> rick_h_: for maas, we'd need an infrastructure where to test it. for osx, I think we'll need some brew hacking
[11:22] <rick_h_> frankban: yep, I started a conversation with someone from server yesterday about maas
[11:22] <rick_h_> frankban: it sounds like it works in a vm world 
[11:22] <rick_h_> frankban: and he's going to send me some notes on some hardware suggestions
[11:22] <frankban> cool
[11:23] <rick_h_> frankban: I was thinking of getting 3 or 4 intel nucs to setup a GUI test lab
[11:23] <frankban> rick_h_: so, my understanding is that "maas support" for quickstart means "supporting the creation of maas entries in the envs.yaml", and not "support deploying maas", right?
[11:23] <rick_h_> frankban: http://marcoceppi.com/2012/05/juju-maas-virtualbox/ 
[11:24] <marcoceppi> rick_h_: frankban I really need to amend that post
[11:24] <rick_h_> frankban: its: 1) support it as a configurable provider 2) support deploying the gui to it 3) support deploying bundles
[11:24] <rick_h_> marcoceppi: cool, yea we're going to be trying to cut our teeth on maas so looking into the beginner stuff atm
[11:25] <marcoceppi> rick_h_: that's not the way to go
[11:25] <rick_h_> marcoceppi: heh ok good to know
[11:25] <marcoceppi> rick_h_: virt-manager + maas is way better experience
[11:25] <marcoceppi> I've got a blog post written up about it
[11:25] <frankban> rick_h_: ok, so you already have a maas, and quickstart allows you to configure a juju environment on your maas provider, bootstrap juju, deploy the GUI and bundles
[11:25] <marcoceppi> but not finished
[11:26] <rick_h_> frankban: yep, that's the goal anyway. I've got a note to 'investigate what's required to implement' 
[11:26] <rick_h_> frankban: and maas does have an api so there might be a stretch goal or two when we get in there. 
[11:26] <rick_h_> frankban: we might need to do things like use the api to make sure you've got unallocated nodes or the like
[11:27] <rick_h_> since you can't bring up new machines you don't have/etc
[11:29] <frankban> rick_h_: I see, so we need at least one node for bootstrap node + GUI and a machine for each unit in the bundle (assuming they are not co-located,in which case we would need to also parse the bundle)
[11:29] <frankban> marcoceppi: sounds great, looking forward to reading that article
[11:30] <rick_h_> frankban: that's my understanding of maas at the moment. It's a very vague understanding though I'll admit :)
[11:53]  * frankban lunches
[14:03] <frankban> rick_h_: re local icons in service blocks. This might require some changes on the guiserver in order to handle the case the local charm does not include an icon.svg, right?
[14:04] <frankban> rick_h_: in that case, a 404 is returned and the block would display a broken image I guess
[14:09] <rick_h_> frankban: I thought we could have hte files in the charm model
[14:09] <rick_h_> frankban: and only request it form the guiserver if we already know the charm has one
[14:10] <frankban> rick_h_: where in the code files are currently populated?
[14:11] <rick_h_> frankban: looking
[14:11] <rick_h_> frankban: for the stuff we get from charmworld there's a files attr from the apio
[14:11] <rick_h_> frankban: if we don't fill that during our unzip of the local charm we can add it? hatch do you recall when you worked on the unzip stuff around charms?
[14:13] <frankban> rick_h_: I am not sure we unzip the files when uploading local charms, and even in that case, we need to handle local charms deployed from outside the GUI, or after a refresh
[14:13] <rick_h_> frankban: true
[14:14] <rick_h_> frankban: ok, well in the case that the guiserver can't find a charm icon, it can redirect to manange. It's got solid urls for the default and the category icons
[14:14] <rick_h_> hate to duplicate that, but worst case it can 302 to the right url
[14:14] <rick_h_> does the guiserver know the charm's config for the charmworld url?
[14:14] <rick_h_> the root hostname and all that?
[14:15] <frankban> looking
[14:15] <frankban> rick_h_: the charm passes the charmworld url to the gui server, yes
[14:17] <rick_h_> frankban: ok, so the default icon is always /static/img/charm_160.svg
[14:17] <rick_h_> frankban: and we've got category one's as well, but not sure if we have that data
[14:18] <rick_h_> as that's going to be metadata.yaml info for the charm in question
[14:18] <rick_h_> frankban: what do you think of just "if no icon found, 302 to charmworld's default"?
[14:18] <frankban> rick_h_: we can start by just redirecting to the default icon
[14:18] <frankban> yeah
[14:19] <rick_h_> frankban: oh, doesn't the api send the file list? 
[14:19] <frankban> rick_h_: so, if 404 on the gui server, just redirect to charmworldURL://static/img/charm_160.svg
[14:19] <frankban> rick_h_: yes
[14:19] <rick_h_> frankban: I recall we had a / that would give us the list of files?
[14:19] <frankban> it does
[14:19] <frankban> rick_h_: yes
[14:19] <rick_h_> so we can popualte the file list on reaload/etc...but it's not automatic/delta/etc so it's an extra call already
[14:20] <frankban> rick_h_: yes, it's an HTTPS call, not a WebSocket one
[14:20] <rick_h_> sorry, thinking this through...had in my head we'd have the same files: [somelist] on models like we do from charmworld
[14:20] <frankban> rick_h_: so, it's not in the delta
[14:20] <frankban> rick_h_: yes, we have that list returned as JSON by a GET call to /charms/?url=charmURL
[14:20] <rick_h_> hmm, ok well let's do this for now due to the demo urgency, but I'd like to revisit and see if perhaps we should try to do something with that data on local charms 
[14:21] <hatch> sorry I missed the ding....
[14:21] <frankban> rick_h_: we'll need that data for the README
[14:21] <rick_h_> maybe there's some way (annotations?) or something we can shoe-horn this into place to be better long term
[14:21] <rick_h_> frankban: right, but the readme loads async anyway so it's not as big a deal
[14:22] <rick_h_> it's not as painful to get a spinny wheel and get 'no readme found' 
[14:22] <hatch> ok I don't understand the question
[14:22] <frankban> rick_h_: exactly, the icon is instead just a source reference, a path to a file somewhere
[14:22] <rick_h_> frankban: ok, I'm adding a card in the backlog to revisit the files list some more, but for demo we can just hard code 302 to charmworld from the gui's config
[14:23] <rick_h_> in case they run a local charmworld instance or something for offline-ness
[14:23] <rick_h_> hatch: all good, frankban got me straight. There were bigger issues than I had in my head at the moment
[14:23] <hatch> oh ok cool
[14:23]  * rick_h_ puffs some more air up in that head to make more room
[14:23] <hatch> haha
[14:23] <hatch> last night I got wifi working on ubuntu, and they fixed the shutdown bug
[14:24] <rick_h_> woot
[14:24] <hatch> now the only real 'deal breaker' is that it burns through the battery in about 1.5h
[14:24] <hatch> lol
[14:24] <hatch> on idle, osx 7, ubuntu 1.5
[14:24] <hatch> something isn't quiiiiite right there
[14:24] <hatch> lol
[14:28]  * bac is back.  survived first encounter with PR health care system.
[14:29] <rick_h_> bac: whoa, hope all is well
[14:31] <hatch> is it cheap there or still way overpriced?
[14:32] <bac> seems about the same as US.  but they don't want to mess with our insurance, even though they are listed in the BCBS network.
[14:33] <hatch> I saw a really interesting show which outlined why the US healthcare is so expensive vs others even taking govt subsidies out of the equation. It came down to each office being it's own instead of negotiating in a large group to purchase things
[14:33] <bac> SHUT UP!  WE HAVE THE BEST HEALTHCARE SYSTEM IN THE WORLD, MAYBE THE UNIVERSE.
[14:33] <bac> i know, i heard it on tv
[14:34] <hatch> lol
[14:34] <bac> don't mind those pesky "outcome" metrics.
[14:35] <hatch> if it makes you feel any better ours spend $27M to learn how to do lean....and then they claimed that it woudln't work....
[14:35] <hatch> *facedesk*
[14:36] <hatch> no that wasn't extreme enough
[14:36] <hatch> *facefloor*
[14:38] <bac> rick_h_: that ES book must've been something in the original Polish.  the English translation is a head-scratcher at times.  but, everyone says it is the best available, so i'm happy to have it.
[14:39] <hatch> heh
[14:39] <rick_h_> bac: hah
[14:39] <bac> i guess "editor" is not a job description at those pulp houses
[14:40] <rick_h_> yea, I mean it at least got my head around ES better 
[14:40] <bac> rick_h_: did you send away for the free code samples?
[14:40] <rick_h_> but yea, sometimes tough to read
[14:40] <rick_h_> bac: no, the book had enough in the book for me to figure out commands to run to help debug stuff
[14:40] <bac> cool
[14:50] <rick_h_> jujugui call in 10 kanban please
[15:00] <hatch__> kadams54 call
[15:00] <kadams54> Yup
[15:10] <lazyPower> rick_h_: so, i have it on good authority you know of a magical flag that allows me to view icons in the GUI that dont come from the charm store
[15:10] <rick_h_> lazyPower: ssssh I'm not telling anyone
[15:10] <lazyPower> oh
[15:10] <lazyPower> so
[15:10] <rick_h_> lazyPower: it doens't work atm
[15:10] <hatch> lol
[15:10] <rick_h_> and we're working on local charms getting icons right now for high priority stuff that should be done be Wed
[15:10] <lazyPower> i have it on good authority this flag doesn't exist, and i will poke at you for additional details of said non-functioning freature
[15:11] <lazyPower> ;)
[15:11] <rick_h_> lazyPower: I started the feature, but it doesn't work and have not had a chance to follow up the feature as it's been a slack time thing and I don't know what slack is
[15:11] <rick_h_> lazyPower: but it's something we want to do, and one day will do, and until they jorge can throw rocks at me
[15:12] <rick_h_> local charms will work this week though
[15:12] <lazyPower> I understand the feeling all to well my friend. I'll resync after release, its got a good application during the review process
[15:12] <lazyPower> xdg-open and dragging it over the canvas doesn't really give a good overview of how it looks
[15:12] <rick_h_> lazyPower: well, if it's a local after this week you can just drag a zip of it over in a live env :)
[15:12] <lazyPower> and we're getting some really *gnarly* icons... complete with neon color schemes. its like an 80's dance party in the queue.
[15:13] <rick_h_> which you need for review anyway I assume?
[15:13] <lazyPower> i do the repository flag +  local: prefix. No zipping here 
[15:14] <rick_h_> lazyPower: well, we can change that :)
[15:38] <bac> jujugui: trying to build charm-tools i'm seeing pip die with SSL errors trying to fetch bzr from launchpad.  i suspect it is due to the re-keying, fallout from the OpenSSL problem.  just a fyi in case you see similar.
[15:38] <rick_h_> bac: rgr thanks for the heads up
[15:38] <hatch> rick_h_ ok updated
[15:48] <hatch> kadams54 I'm going to hop on getting huw's branch landed
[16:10] <hatch> hmmm rick_h_  how do you pull down someone elses branch and then update the PR?
[16:10] <hatch> I tried my usual method but no luck...
[16:10] <hatch> do you need to clone their repo?
[16:11] <hatch> lazyPower there has been an update to http://askubuntu.com/questions/445025/cannot-deploy-local-charms-after-juju-upgrade I think it's a bug that he is experiencing...it  should work...
[16:13] <hatch> Makyo in Ubuntu my laptop sounds like your system76, 1000000% fan speed lol
[16:13] <lazyPower> hatch: Error: storm not found in charm store
[16:13] <Makyo> Yikes :)
[16:13] <lazyPower> interesting - i cant charm get it
[16:13] <hatch> lazyPower he is deploying a local charm...
[16:14] <lazyPower> needs more info, di dhe write it? did he branch maarten ecctors charm? whats his repository layout look like?
[16:14] <lazyPower> i've deployed from local repo using 1.18.x for the last 2 days without issue - so i'm pondering on vectors of failure
[16:15] <hatch> ahh, well the error message seems to show that he is using an old version of juju....if he actually is using that command
[16:15] <hatch> so it is confusing
[16:16] <lazyPower> theres a series mismatch on that too
[16:16] <lazyPower> does precise now download the saucy package?
[16:16] <Makyo> hatch, got a second for a hangout?
[16:16] <hatch> Makyo you bet, link?
[16:16] <Makyo> One se
[16:16] <Makyo> c
[16:17] <Makyo> G+ is slooooow
[16:17] <hatch> oo 19 forks of the juju-gui
[16:17] <hatch> a couple I dont' recognize...
[16:18] <Makyo> hatch, https://plus.google.com/hangouts/_/7ecpj2bofe2256ukgemgsuge24?hl=en
[16:25] <hatch> crap CI hung again
[16:27] <hatch> jujugui does anyone know how to update someone elses PR?
[16:27] <rick_h_> hatch: take it over
[16:27] <rick_h_> git qa-pr, change it, push to your origin
[16:28] <hatch> oh push it to my origin
[16:28] <hatch> ok cool
[16:29] <hatch> hmm there was some way to update the actual PR
[16:29] <hatch> now I have to create a new PR....which is fine I suppose
[16:29] <hatch> I know you've done it before....just don't know how haha
[16:32] <hatch> ok new pr created
[16:33] <hatch> rick_h_ I know you're busy but if you could try and squeeze some time to look at my branch so I can move onto the next step that would be awesome......(whatever the next step is...)
[16:34] <rick_h_> wil to hatch 
[16:34] <rick_h_> next step is statecontroller dispatcher stuff
[16:36] <hatch> oh ok, new card..
[16:36] <rick_h_> hatch: yea, more of the old card work, tag unsched
[16:48] <hatch> ugh CI!!!!!
[16:49] <rick_h_> hatch: did it hang?
[16:49] <rick_h_> hatch: off my call if you want to chat still
[16:49] <hatch> twice now, the first time was a sauce labs hang, the second time was ERADDRINUSE
[16:49] <rick_h_> hatch: ah, I've got ot kill it then sec
[16:49] <hatch> oh...ok it's running the next tests now
[16:49] <rick_h_> it's supposed to kill it but seems not to
[16:49] <hatch> sure we can chat about this state controller, I've got a few ideas
[16:50] <rick_h_> hatch: k, linky
[16:50] <hatch> https://plus.google.com/hangouts/_/7ecpitdd3kur5rdfi9bkaqgbms?hl=en
[17:16] <rick_h_> jujugui going afk for food stuffs biab
[17:19] <lazyPower> hatch: confirmed its a bug in 1.18
[17:19] <hatch> todaso
[17:20] <hatch> lazyPower ever seen trailer park boys?
[17:21] <lazyPower> only bubbles vs the bible salesman
[17:21] <hatch> lol
[17:22] <hatch> ahhh such a good series
[17:36] <lazyPower> hatch: https://bugs.launchpad.net/juju-core/+bug/1303880
[17:36] <_mup_> Bug #1303880: After upgrade to 1.18, can not deploy local charms <juju-core:Triaged> <https://launchpad.net/bugs/1303880>
[17:37] <hatch> ouch that's a doozie 
[17:45] <lazyPower> hatch: workaround is to add series to the deployment
[17:45] <lazyPower> juju deploy --repository=$SOMEPATH local:precise/mysql for example
[17:46] <hatch> ahhh - woops I totally missed that in his command
[17:46] <hatch> I always use the series....I didn't know it was optional heh
[17:48] <hatch> I should answer the question and steal the points
[17:48] <hatch> mohohahaha
[17:50] <rick_h_> lazyPower: isn't that related to the work on the charm store and prep for charms declaring series?
[17:50] <rick_h_> e.g. not really a 1.18 thing but a charm store thing (is that pulled out yet?P
[17:50] <rick_h_> )
[17:53] <lazyPower> rick_h_: http://askubuntu.com/questions/445025/cannot-deploy-local-charms-after-juju-upgrade/445101#445101
[17:53] <_mup_> Bug #445101: package openoffice.org-filter-binfilter (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 <apport-package> <i386> <openoffice.org (Ubuntu):New> <https://launchpad.net/bugs/445101>
[17:53] <lazyPower> _mup_: you have failed me for the last time *forcechoke*
[17:53] <rick_h_> lazyPower: gotcha cool
[18:00] <lazyPower> rick_h_: yeah it doesn't appear to be. A mistaken landing of the new CS code - should be an easy fix. That or a doc update to clear up the ambiguous url bits. I assume that behavior is coming back, but i dont really know.
[18:01] <rick_h_> lazyPower: yea, there was supposed to be some default logic in teh store to handle it I think. Maybe a bug in that, or the updated store didn't get deployed to prod yet
[18:01] <rick_h_> lazyPower: it'd be something to talk to casey about
[18:01] <lazyPower> Right. Marco and sinzui and natefinch are on it. I dont want to dogpile him :)
[18:01] <rick_h_> yep all good
[18:02] <rick_h_> I was just responding to the idea of 'big bug in 1.18' as I kind of thuoght it was almost expected behaviour, but I'm not up on the latest/greatest of what made 1.18 and what did not
[18:04] <hatch> rick_h_ I copied the state object wholesale
[18:04] <rick_h_> hatch: yea, noticed
[18:04] <hatch> so it's all the same code as before which I'll remove/replace as needed
[18:04] <rick_h_> sorry, I dived in to review everything in green and started to go "this isn't right"
[18:05] <rick_h_> hatch: all good, I'm to the good parts now
[18:05] <hatch> sounds good
[18:20] <rick_h_> hatch: looks like one big miss in the branch atm. I'll keep going but I'm not repeating it for each instance. Let me know if we need to chat on it
[18:20] <rick_h_> hatch: or if the comment makes sense
[18:20] <hatch> hmm ok checking
[18:24] <rick_h_> hatch: aside from that looks great!
[18:24] <rick_h_> <3 the tests
[18:32] <hatch> rick_h_ comments replied
[18:32] <rick_h_> hatch: looking
[18:40] <rick_h_> hatch: it seems I thought our conversation went off a different way. 
[18:40] <rick_h_> hatch: call? 
[18:41] <rick_h_> hatch: I fear that this is going to break once we do chamge objects as a change to sectionA will have to know to touch section B. You'll end up rendering both which I thought we agreed not to do
[18:42] <hatch> sure
[18:42] <hatch> sec ill make a link
[18:42] <hatch> https://plus.google.com/hangouts/_/7acpim020konevo66n5lf10fqs?hl=en
[18:49]  * Makyo ducks out to appointment, will propose shortly after.
[18:52] <kadams54> #1 peeve: spending time debugging a one character typo
[18:52] <kadams54> destory != destroy
[19:12] <hatch> haha yeah that does suck
[19:12] <hatch> *caugh*typescript*caugh*
[20:22] <hatch> rick_h_ still around?
[20:22] <rick_h_> hatch: yep
[20:22] <rick_h_> call in 10
[20:22] <rick_h_> what's up?
[20:22] <hatch> https://gist.github.com/hatched/10185566
[20:23] <rick_h_> ooh, purdy
[20:23] <rick_h_> <3
[20:23] <rick_h_> happy with it?
[20:23] <hatch> excellent, I'll finish it up
[20:23] <hatch> yup
[20:23] <hatch> much better
[20:23] <hatch> thx
[20:23] <rick_h_> cool, thank you for the clean up, much nicer to read imo
[20:24] <hatch> yeah - I think I like this api design too, it could also be _addToSection('a', 'charmbrowser', this._parseCharmUrl()) but I think the explicit vars is nice
[20:24] <rick_h_> yep
[20:25] <hatch> wish js had real named params
[20:25] <hatch> but oh well
[20:25] <hatch> this works
[20:25] <rick_h_> and works well
[20:25] <rick_h_> so all good
[20:29] <kadams54> jujugui heading out to take a sunshine break. Will be back in a bit.
[20:29] <rick_h_> kadams54: have fun
[20:29] <kadams54> Solar powered coding
[20:29] <rick_h_> woot
[20:30] <hatch> haha
[20:30] <hatch> it's still way to dirty/dusty out for outsideness here
[20:30] <hatch> in a week or so I -may- be able to start washing things
[20:30] <rick_h_> I want to hire a street cleaner to come by
[20:30] <rick_h_> it's a mess out
[20:31] <hatch> yeah - we live pretty close to a high traffic road so the salt/grime settles in the snow and when it all melts then it leaves a gross film over everything
[21:09] <hatch> 3PM, it's mewzaq time!
[21:23] <hatch> hmm lots of edge cases being exposed now
[21:30] <hatch> jujugui do we have a method somewhere for building a nested object? leaving values which currently exist alone?
[21:31] <hatch> ex) var a = { b: {g:{}}}; someMethod('a.b.c.d'); ?
[21:54] <hatch> in case anyone is wondering Y.namespace.call(rootObject, 'path.to.create'); works like a charm
[21:54] <hatch> and those darn urls are finished
[21:54] <hatch> landing that branch finally!
[22:13] <Makyo> That's cool, hatch.  A little magical, maybe, but neat.
[22:14] <hatch> Makyo yeah the key is right here http://yuilibrary.com/yui/docs/api/files/yui_js_yui.js.html#l1375
[22:14] <Makyo> Awesome
[22:15] <Makyo> While I'm at it, I have the inspector stuff working as we discussed, but have been puzzling over tests for a bit.
[22:15] <Makyo> There don't seem to be many tests for _deployCallbackHandler, so I'm starting from scratch.
[22:16] <hatch> hmm darn
[22:16] <Makyo> Or, well, any.
[22:17] <Makyo> But I'll get it proposed tonight with at least the test for what I've written.
[22:17] <Makyo> I think that's an artifact of the move to inspectors.
[22:17] <Makyo> i.e. the rest of the functionality is tested in a more functional/less unit type of testing
[22:18] <Makyo> The problems of testing async code, I guess.
[22:18] <hatch> ahh - I think that's old code too
[22:18] <hatch> man we really need a better test suite heh
[22:18] <Makyo> Yeah. The file is new, so blame is off, but it's obviously been moved from other locations, since it's some of the original notification code.
[22:19] <hatch> maybe for xmas 2014 we'll be able to give ourselves a new test suite haha
[22:19] <hatch> ahh yeah
[22:19] <hatch> this looks amazing
[22:19] <hatch> https://www.indiegogo.com/projects/healbe-gobe-the-only-way-to-automatically-measure-calorie-intake
[22:19] <hatch> if it's real/works.....
[22:20] <Makyo> Rock on!
[22:20] <hatch> I'm super tempted to pick one up....
[22:21] <Makyo> A friend of mine is all jaded about the quantified self movement.
[22:21] <hatch> yeah? I think it's so darn cool
[22:21] <Makyo> He works at Mozilla, but used to work at Linden Labs on Secondlife, so he's jaded about quite a bit.
[22:21] <hatch> I want to be able to query all my vitals in a db lol
[22:21] <hatch> rofl
[22:21] <Makyo> He was recently railing on http://www.factmag.com/2014/03/28/lightwave-wristband-tells-djs-if-the-crowd-are-having-a-good-time-and-is-a-stupid-stupid-idea/
[22:22] <hatch> I never did understand secondlife
[22:22] <hatch> lol! 
[22:23] <hatch> they could use that to see how much E is being sold....lol!
[22:23] <Makyo> It's such a bitter article :D
[22:23] <hatch>  (warning: contains strong Electric Daisy Carnival vibes):
[22:23] <hatch> haha
[22:25] <Makyo> Not quite sure what to make of Fact. I found http://www.factmag.com/2014/04/07/stream-eric-holms-astonishing-new-subtext-album-andoya/ through it, which is ridiculous, and somehow also awesome.
[22:25]  * Makyo anyway, back to work.
[22:26] <hatch> liiiistening
[22:26] <Makyo> If you're into ambient, the albums linked to early on are also great.
[22:26] <Makyo> Sort of...Stars Of The Lid does drums.
[22:26] <hatch> annnnd nope!
[22:26] <Makyo> Hahaha
[22:27] <hatch> maybe if I was just chillin out, but I don't do that often
[22:27] <Makyo> No, you don't :)
[22:28] <hatch> rick_h_ also my horizontal two finger scroll works in Ubuntu....(you mentioned you had issues with that) so maybe you should do a update/upgrade and it may work now
[23:04] <huwshimi> Morning
[23:22] <hatch> morning huwshimi 
[23:22] <hatch> your branch has been landed
[23:22] <hatch> we weren't sure where you left off last night 
[23:25] <huwshimi> hatch: Ah, great, thanks :)
[23:26] <hatch> make sure you update the board so we know which card we can't take in the morning :)