/
fluid-work IRC Logs-2013-09-16

fluid-work IRC Logs-2013-09-16

Owned by Fluid IRC Log Bot
Last updated: Sept 16, 2013

[08:10:50 CDT(-0500)] <Justin_o> jhung: good morning.. i commented on your pull request for GPII-207

[08:11:05 CDT(-0500)] <jhung> thanks Justin_o

[08:24:39 CDT(-0500)] <jhung> Justin_o: regarding GPII-207. The font should be there. https://github.com/fluid-project/prefsEditors/pull/47/files Try dumping cache? If in Firefox, you'll have to restart it.

[08:25:20 CDT(-0500)] <jhung> Justin_o: as for the drop shadow, it's fine on my side. The drop shadow should be present but without a blur on the tree logo.

[08:31:47 CDT(-0500)] <Justin_o> jhung: i mean that horizontal one that stretches the page width

[08:32:45 CDT(-0500)] <jhung> That horizontal bar Justin_o?

[08:33:31 CDT(-0500)] <Justin_o> jhung: the shaddow under the header

[08:33:36 CDT(-0500)] <Justin_o> header bar

[08:34:35 CDT(-0500)] <jhung> Justin_o: ok. got it.

[08:34:44 CDT(-0500)] <jhung> Justin_o: the font showing up for you in Low Contrast?

[08:46:10 CDT(-0500)] <Justin_o> jhung: the one used in the discovery panel doesn't look the same as the one in the body when in high contrast.. i cleared my cache and restarted firefox.. and it still looks the same

[08:56:26 CDT(-0500)] <jhung> there is no font change for High Contrast Justin_o. Just low contrast.

[08:57:39 CDT(-0500)] <Justin_o> jhung: sorry, meant low contrast

[09:22:07 CDT(-0500)] <Justin_o> jhung: merged your GPII-207 pull request

[09:22:53 CDT(-0500)] <jhung> thanks Justin_o

[11:47:20 CDT(-0500)] <Justin_o> cindyli: i've updated http://issues.fluidproject.org/browse/FLUID-5131 can you take a look at it when you have a chance and see if it makes sense

[11:47:37 CDT(-0500)] <cindyli> sure, thanks, Justin_o

[11:51:43 CDT(-0500)] <cindyli> Justin_o: the part one for the definition of one panel / multiple templates in the aux schema seems not enough. we can flesh it out when we go along

[11:52:40 CDT(-0500)] <Justin_o> cindyli: sounds good.. i think we'll probably need someway of identifying when we need to create the combined panel too

[11:53:15 CDT(-0500)] <cindyli> agree

[12:16:46 CDT(-0500)] <Justin_o> cindyli: was everything else okay with the FLUID-5131 jira?

[12:17:17 CDT(-0500)] <cindyli> yes, Justin_o, it looks great

[12:18:07 CDT(-0500)] <Justin_o> cindyli: thanks

[14:10:21 CDT(-0500)] <michelled> Justin_o: I just created this JIRA and put it fix for 1.5 http://issues.fluidproject.org/browse/FLUID-5135

[14:10:34 CDT(-0500)] <michelled> I think we should fix it since we just introduced it with our new demos

[14:11:09 CDT(-0500)] <Justin_o> michelled: okay

[14:11:37 CDT(-0500)] <Justin_o> michelled: not sure at the moment how to fix that because the cookie is on the same domain but we can take a look at it for sure

[14:12:23 CDT(-0500)] <michelled> Justin_o: the cookie name should probably be configurable if it isn't already

[14:35:41 CDT(-0500)] <Justin_o> michelled: that's true we could do that

[15:05:24 CDT(-0500)] <Bosmon> fluid-everyone: you may be interested that I have recently written up our demands block thinking as part of this GPII JIRA: http://issues.gpii.net/browse/GPII-209

[15:05:49 CDT(-0500)] <Bosmon> Since the GPII is the active project with by far the most demands blocks in circulation, our general purge will have to start there

[15:06:15 CDT(-0500)] <Bosmon> But in general, everyone should be put on notice to write no new demands blocks, and strive to get rid of existing ones : P

[15:07:30 CDT(-0500)] <colinclark> Demands blocks will end up being some kind of Fringe-esque anachronism

[15:07:44 CDT(-0500)] <colinclark> The future for another, parallel dimension

[15:08:00 CDT(-0500)] <colinclark> but oddly "eighteenth century" here in this one

[15:08:15 CDT(-0500)] <Bosmon> Demands blocks === blimps

[15:08:22 CDT(-0500)] <Bosmon> THE AIR TRAVEL OF THE FUTURE

[15:08:27 CDT(-0500)] <colinclark> yes, exactly!

[15:47:44 CDT(-0500)] <colinclark> Bosmon: I can imagine we might not be too far from a line-length war

[15:47:50 CDT(-0500)] <colinclark> which you mentioned we have so far avoided (tongue)

[15:48:07 CDT(-0500)] <Bosmon> colinclark - so it seems, yes : P

[15:48:51 CDT(-0500)] <colinclark> Do you have any particular strategies for how you plan to avoid revisiting this particularly famous sort of bike shed?

[15:49:11 CDT(-0500)] <Bosmon> no plans, no

[15:53:07 CDT(-0500)] <Bosmon> In the past I believe we have, for better or worse, adopted the policy of "follow the guidelines of some well-known figure in the community" : P

[15:53:23 CDT(-0500)] <Bosmon> I argue though, that an 80 character line limit doesn't really make use of the facilities of the 21st century .....

[15:59:48 CDT(-0500)] <colinclark> I thought our bike shed policy was typically "find someone else's policy, so that everyone is equally unhappy and powerless" (tongue)

[16:09:25 CDT(-0500)] <colinclark> hey kasparnet and yzen, I have a quick question for you

[16:09:35 CDT(-0500)] <kasparnet> sure

[16:09:57 CDT(-0500)] <colinclark> I'm just writing up the architecture section for the next Preferences for Global Access "design deliverable"

[16:10:04 CDT(-0500)] <colinclark> PGA uses the same bizarre convention as Cloud4all

[16:10:14 CDT(-0500)] <colinclark> where "deliverable" should be translated as "long report"

[16:10:16 CDT(-0500)] <colinclark> (wink)

[16:10:31 CDT(-0500)] <colinclark> Anyway, yzen and I were talking before he left about Web Sockets

[16:10:54 CDT(-0500)] <colinclark> and I'm writing up a section about how a web-based application such as the PCP could communicate with a locally-installed Flow Manager

[16:11:15 CDT(-0500)] <colinclark> I remember back in San Diego we were talking about the need for a browser plugin

[16:11:35 CDT(-0500)] <colinclark> my experience with the Leap Motion controller, for example, suggests that it should be quite viable to do something without plugins using Web Sockets

[16:11:51 CDT(-0500)] <colinclark> Anyway, in San Diego I think we identified two main cases for "cross-world" communication

[16:11:57 CDT(-0500)] <yzen> colinclark: that'd be nice

[16:12:14 CDT(-0500)] <kasparnet> yeah, avoiding plugins would be great

[16:12:19 CDT(-0500)] <colinclark> The first case was for a preferences editor to say "Hey, Flow Manager, the user wants to change their preferences temporarily"

[16:12:25 CDT(-0500)] <colinclark> So this might the case of a preview

[16:12:36 CDT(-0500)] <colinclark> or it might be a "this session only" change to their settings

[16:13:08 CDT(-0500)] <colinclark> The second case we talked about was the case where a web-based Solution needed to know if some need or preference had already been satisfied by a local, desktop-based solution

[16:13:43 CDT(-0500)] <colinclark> I think it was to prevent the "4x larger text" problem in the case where a web app reads the same preference as the desktop, say for 2x the text size

[16:13:49 CDT(-0500)] <colinclark> is this all sounding familiar so far?

[16:13:54 CDT(-0500)] <yzen> colinclark: yep

[16:13:59 CDT(-0500)] <colinclark> Cool

[16:14:06 CDT(-0500)] <colinclark> Okay, so I think we're not quite ready yet to solve the second case

[16:14:15 CDT(-0500)] <colinclark> In terms of thinking through how this would actually happen

[16:14:27 CDT(-0500)] <colinclark> Do you know if we now have any kind of Flow Manager API for the first case?

[16:14:36 CDT(-0500)] <colinclark> I'm pressure Evgeni had something sketched out in a branch

[16:14:45 CDT(-0500)] <colinclark> but I'm guessing that never made its way into a pushable pull request?

[16:14:48 CDT(-0500)] <colinclark> or did it?

[16:17:17 CDT(-0500)] <yzen> colinclark: yes that's in his branch, never been reviewed formally

[16:17:27 CDT(-0500)] <colinclark> Ok

[16:17:41 CDT(-0500)] <colinclark> If you were to implement it, can you speculate super quickly on what it would look like, yzen?

[16:17:53 CDT(-0500)] <colinclark> I guess a

[16:18:01 CDT(-0500)] <colinclark> "preferencesChanged" POST request or something?

[16:19:42 CDT(-0500)] <yzen> colinclark: right so a POST with temp preferences

[16:19:50 CDT(-0500)] <yzen> i think evgeni had update

[16:19:56 CDT(-0500)] <yzen> so like /user/token/update

[16:20:19 CDT(-0500)] <colinclark> ok

[16:20:25 CDT(-0500)] <colinclark> seems reasonable enough

[16:20:36 CDT(-0500)] <yzen> colinclark: ya i like it too

[16:20:38 CDT(-0500)] <yzen> btw

[16:20:45 CDT(-0500)] <yzen> i was about to remove the /user/ part

[16:20:57 CDT(-0500)] <yzen> when kasparnet rightfully reminded that all user listeners would not work any more

[16:33:21 CDT(-0500)] <colinclark> They probably shouldn't have hardcoded URLs in them (tongue)

[16:33:35 CDT(-0500)] <colinclark> yzen: Could we expose the new one and deprecate the old one at some point?

[16:33:49 CDT(-0500)] <colinclark> (the new URL scheme, I mean)

[16:40:19 CDT(-0500)] <yzen> colinclark: yes for sure

[16:40:24 CDT(-0500)] <colinclark> cool

[16:40:51 CDT(-0500)] <colinclark> And then we can file a JIRA against the various user listeners, saying that they should provide parameterized Flow Manager URLs

[16:41:44 CDT(-0500)] <colinclark> In the future, I suspect we're going to want to have some kind of checksumming or something when the GPII starts up so that it does some basic sanity-checking of itself

[16:42:00 CDT(-0500)] <yzen> colinclark: ya that's a good idea

[17:10:46 CDT(-0500)] <kasparnet> hi avtar, I checked the DNS' and they seem to be pointing the right way

[17:11:02 CDT(-0500)] <kasparnet> how is access to the servers looking (for yura to run the servers)

[17:16:58 CDT(-0500)] <avtar> kasparnet: i'm tackling the nginx config at the moment

[17:18:31 CDT(-0500)] <avtar> i'll have all three components online within 1 - 2 hours

[17:20:01 CDT(-0500)] <avtar> if possible please confirm that you're able to run them locally using the code in the master branch and the instructions in the universal repository

[17:20:29 CDT(-0500)] <avtar> yzen or kasparnet ^

[17:23:02 CDT(-0500)] <kasparnet> avtar: cool! Yura will check that things work locally, etc

[17:23:36 CDT(-0500)] <kasparnet> avtar: also, I think that the components will run off the v0.2 branch, but I'll let yzen confirm that

[17:27:15 CDT(-0500)] <avtar> kasparnet: worrrd

[17:38:50 CDT(-0500)] <avtar> kasparnet: i'm not sure how late you or yzen are planning on being around

[17:39:12 CDT(-0500)] <yzen> avtar: how late is not late enough (smile) ?

[17:39:25 CDT(-0500)] <kasparnet> avtar: well, with the speed yura is reviewing pull requests, we're not gonna get to bed for another 8 hours

[17:39:28 CDT(-0500)] <kasparnet> (smile)

[17:39:51 CDT(-0500)] <avtar> but i skipped lunch today because that seemed like a good idea at the time so i think i need to find something to eat toute suite

[17:40:24 CDT(-0500)] <avtar> i'll log on from home in about 30 mins

[17:41:25 CDT(-0500)] <kasparnet> ok, sounds good

[17:41:25 CDT(-0500)] <avtar> but if you guys can confirm the requirements, deployment docs, branch info, etc then i can continue after linner

[17:41:34 CDT(-0500)] <kasparnet> cool

[17:41:37 CDT(-0500)] <kasparnet> thanks avtar

[17:41:55 CDT(-0500)] <avtar> either email me or i'll check the channel logs

[19:19:34 CDT(-0500)] <avtar> kasparnet, yzen: ping

[19:20:12 CDT(-0500)] <yzen> avtar: PONG (smile)

[19:20:44 CDT(-0500)] <avtar> just to confirm, i should be select the 1.2 branch for everything?

[19:21:24 CDT(-0500)] <yzen> avtar: 0.2

[19:21:29 CDT(-0500)] <yzen> so lets reca

[19:21:32 CDT(-0500)] <yzen> recap

[19:21:49 CDT(-0500)] <yzen> you only care about the universal repository

[19:21:50 CDT(-0500)] <avtar> 0.2 is what i meant

[19:21:54 CDT(-0500)] <avtar> really

[19:21:57 CDT(-0500)] <avtar> yes

[19:22:01 CDT(-0500)] <avtar> i love it

[19:22:16 CDT(-0500)] <yzen> so yes you need a v0.2 branch of universal

[19:22:24 CDT(-0500)] <yzen> now regarding the things we are deploying

[19:22:30 CDT(-0500)] <yzen> i realized we actually only need 2 thinkgs

[19:22:33 CDT(-0500)] <yzen> things

[19:22:38 CDT(-0500)] <yzen> the flow manager and the match maker

[19:22:47 CDT(-0500)] <yzen> we can forget about the ontology for the time being

[19:22:58 CDT(-0500)] <avtar> ok

[19:23:01 CDT(-0500)] <yzen> so once you clone v0.2

[19:23:06 CDT(-0500)] <yzen> you need to run nom install

[19:23:09 CDT(-0500)] <yzen> to get the right stuff

[19:23:19 CDT(-0500)] <avtar> yup

[19:23:32 CDT(-0500)] <avtar> and just use kettle instead of what's in the old docs?

[19:23:38 CDT(-0500)] <yzen> so yes

[19:23:46 CDT(-0500)] <yzen> 2 servers you are deploying are:

[19:23:53 CDT(-0500)] <yzen> FLOW MANAGER:

[19:23:57 CDT(-0500)] <avtar> SWEET

[19:24:18 CDT(-0500)] <yzen> NODE_ENV=cloudBased node node_modules/kettle/lib/init.js gpii/node_modules/flowManager/config

[19:24:30 CDT(-0500)] <avtar> oh

[19:24:31 CDT(-0500)] <avtar> wait

[19:25:26 CDT(-0500)] <yzen> and the

[19:25:31 CDT(-0500)] <yzen> MATCH MAKER:

[19:25:35 CDT(-0500)] <avtar> https://github.com/GPII/universal/blob/v0.2/gpii/node_modules/flowManager/configs/cloudBased.json#L16

[19:25:50 CDT(-0500)] <yzen> node node_modules/kettle/lib/init.js gpii/node_modules/matchMaker/configs

[19:25:50 CDT(-0500)] <avtar> just point that to MATCH MAKER instead of LOCALHOST

[19:25:51 CDT(-0500)] <avtar> ?

[19:26:01 CDT(-0500)] <yzen> yes

[19:26:03 CDT(-0500)] <avtar> ok

[19:26:05 CDT(-0500)] <yzen> so that s the thing

[19:26:14 CDT(-0500)] <yzen> we need to point to the real url

[19:26:17 CDT(-0500)] <yzen> is that ok ?

[19:27:06 CDT(-0500)] <avtar> and https://github.com/GPII/universal/blob/v0.2/gpii/node_modules/matchMaker/configs/production.json for MATCH MAKER?

[19:27:26 CDT(-0500)] <yzen> no

[19:27:37 CDT(-0500)] <yzen> so since we don't specify NODE_EV

[19:27:38 CDT(-0500)] <yzen> ENV

[19:27:45 CDT(-0500)] <yzen> it will be development by default

[19:27:47 CDT(-0500)] <yzen> which is what we want

[19:28:20 CDT(-0500)] <avtar> ok

[19:28:31 CDT(-0500)] <avtar> i won't fail you guys

[19:28:35 CDT(-0500)] <yzen> production would require a real ontology

[19:28:43 CDT(-0500)] <yzen> well it looks like I'm here for a couple of hours

[19:28:49 CDT(-0500)] <avtar> seriously?

[19:28:49 CDT(-0500)] <yzen> so i can try it (smile)

[19:28:52 CDT(-0500)] <avtar> ok

[19:28:56 CDT(-0500)] <yzen> like BOSSSSS

[19:29:00 CDT(-0500)] <yzen> like a

[19:29:05 CDT(-0500)] <avtar> a sleep deprived one

[19:29:33 CDT(-0500)] <yzen> in mother russia you deprive sleep

[19:29:57 CDT(-0500)] <avtar> or it deprives you

[20:28:48 CDT(-0500)] <sgithens> jhernandez yzen : Thanks!

[20:28:58 CDT(-0500)] <yzen> sgithens: BAM

[20:32:03 CDT(-0500)] <jhernandez> sgithens: thanks to you!!

[20:32:08 CDT(-0500)] <jhernandez> (wink)

[20:32:45 CDT(-0500)] <sgithens> jhernandez: I'm sure that source dir change is fine, I just haven't gotten a chance to do a full build from scratch on it yet.

[20:34:01 CDT(-0500)] <jhernandez> sgithens: well, is fine, but it sometimes doesn't works the first time and I'm not sure why

[20:34:32 CDT(-0500)] <jhernandez> sometimes you need to run source ./prebuild.sh again and then the build ends successfully

[20:34:56 CDT(-0500)] <sgithens> hmm

[20:35:27 CDT(-0500)] <sgithens> Mother Bellarussia would never go for that.

[20:35:47 CDT(-0500)] <jhernandez> xDDD

[20:38:48 CDT(-0500)] <jhernandez> sgithens: btw, I wrote the installation instructions: http://wiki.gpii.net/index.php/Core_(real-time)_Framework_v0.2_-_Installation_Instructions#Android_Installation_Instructions

[20:39:35 CDT(-0500)] <jhernandez> it's pretty similar than the instructions it's already in README.md

[20:40:53 CDT(-0500)] <sgithens> awesome!

[20:41:09 CDT(-0500)] <sgithens> I sort of wish we had a way of including some of our github readme's in the wiki

[20:41:26 CDT(-0500)] <sgithens> it's something I complain about, about once a year, and then forget about

[20:41:42 CDT(-0500)] <kasparnet> ping avtar

[20:42:09 CDT(-0500)] <kasparnet> sgithens: hey dude!!

[20:42:11 CDT(-0500)] <jhernandez> sgithens: sure, it would be nice to have it

[20:42:23 CDT(-0500)] <kasparnet> sgithens: we miss you down here

[20:42:25 CDT(-0500)] <sgithens> KASPARNET!

[20:42:27 CDT(-0500)] <avtar> kasparnet: hi hi

[20:42:29 CDT(-0500)] <sgithens> I miss you guys

[20:42:37 CDT(-0500)] <sgithens> I am really tired of working on this thing

[20:42:48 CDT(-0500)] <sgithens> I can't wait till it's done

[20:43:08 CDT(-0500)] <sgithens> why is putting something into production the first time ever so damn hard

[20:44:04 CDT(-0500)] <kasparnet> sgithens: yeah, I know... even cutting the fucking v0.2 has been horrific, and that's so far from something production worthy

[20:44:12 CDT(-0500)] <jhernandez> sgithens: evil reviewers maybe?

[20:44:14 CDT(-0500)] <jhernandez> (tongue)

[20:44:28 CDT(-0500)] <sgithens> haha

[20:44:42 CDT(-0500)] <kasparnet> jhernandez: cough BOSMON cough

[20:44:43 CDT(-0500)] <sgithens> the server side flow manager github notifications have been pretty epic

[20:44:59 CDT(-0500)] <Bosmon> kasparnet !!!!!!

[20:45:00 CDT(-0500)] <kasparnet> avtar: do you have an ETA on the flowmanager stuff

[20:45:04 CDT(-0500)] <Bosmon> DAMMN YYYOUUU!!!!

[20:45:08 CDT(-0500)] <jhernandez> xDDDD

[20:45:27 CDT(-0500)] <kasparnet> we're closing in on 4 hours till we gotta get up again (smile)

[20:45:39 CDT(-0500)] <avtar> kasparnet: yes, 30 mins

[20:45:42 CDT(-0500)] <kasparnet> Bosmon: (tongue)

[20:47:25 CDT(-0500)] <yzen> 15(smile) ?

[20:47:33 CDT(-0500)] * jhernandez goes to sleep ... I'm sorry for you kasparnet and yzen (tongue)

[21:14:12 CDT(-0500)] <yzen> avtar: going to sleep ill check it tomorrow if that's ok

[21:14:38 CDT(-0500)] <avtar> yzen: sure

[21:14:45 CDT(-0500)] <yzen> ok

[21:14:47 CDT(-0500)] <avtar> i'll send out an email with details

[21:15:02 CDT(-0500)] <yzen> thanks