fluid-work IRC Logs-2013-06-06

[11:57:55 CDT(-0500)] <colinclark> jvass and danaayotte: The new discovery tool wireframes and the ecosystem brainstorming/diagrams look really good. I'm very impressed!

[11:58:11 CDT(-0500)] <colinclark> These ones: http://wiki.fluidproject.org/display/fluid/Preference+Discovery+Tool+%28June%29 and http://wiki.fluidproject.org/display/fluid/Preference+Management+Ecosystem

[11:58:48 CDT(-0500)] <danaayotte> colinclark: glad you like them!

[12:04:33 CDT(-0500)] <jvass> (smile)

[12:59:16 CDT(-0500)] <anastasiac> yzen, I have a question about your solution to FLUID-5016

[12:59:35 CDT(-0500)] <yzen> anastasiac: sure

[12:59:54 CDT(-0500)] <anastasiac> does it implement some way for the 3rd parties to know when the use is actually available? does it take care of that issue somehow?

[13:00:06 CDT(-0500)] <anastasiac> use = UIE

[13:00:21 CDT(-0500)] <anastasiac> does my question make sense, yzen?

[13:03:10 CDT(-0500)] <yzen> anastasiac: in other words you are asking if the user is notified if the enhancer is available or not ?

[13:04:04 CDT(-0500)] <anastasiac> yzen, basically, yes - or whether or not the implementation makes that unnecessary. I'm thinking of a use case where the 3rd party app wants to hook up to UIE, but coincidentally happens to be created before UIE is created. How would that work?

[13:05:54 CDT(-0500)] <yzen> yes in this case it would fail atm

[13:06:38 CDT(-0500)] <anastasiac> yzen, any thoughts on how we could address this?

[13:07:04 CDT(-0500)] <yzen> how does the uie and uio relate?

[13:07:19 CDT(-0500)] <yzen> does uie need to exist fot uio to operate correctly ?

[13:07:38 CDT(-0500)] <anastasiac> yzen, I think so, but not vice-versa

[13:07:51 CDT(-0500)] <yzen> ys

[13:10:19 CDT(-0500)] <yzen> *thinking

[13:10:32 CDT(-0500)] <yzen> anastasiac, michelled: do you have any suggestions?

[13:10:39 CDT(-0500)] <anastasiac> it's a sticky problem

[13:10:57 CDT(-0500)] <anastasiac> I wonder if it needs a wider framework-based solution

[13:11:09 CDT(-0500)] <anastasiac> some kind of static-environment level event system?

[13:11:27 CDT(-0500)] <anastasiac> a way for component to communicate events to other components not within their component tree

[13:12:22 CDT(-0500)] <anastasiac> the problem is that I can't register a listener for staticEnvironment.uiEnhancer..onReady if staticEnvironment.uiEnhancer doesn't exist yet

[13:12:28 CDT(-0500)] <michelled> anastasiac: can you describe your use case?

[13:12:38 CDT(-0500)]

<anastasiac> and if I'm not the one creating UIE, I can't use "

Unknown macro: {uiEnhancer"}

[13:12:56 CDT(-0500)] <anastasiac> yes, michelled, the use case is the VideoPlayer - e.g. the VideoPlayer wordpress plugin

[13:13:08 CDT(-0500)] <anastasiac> the base theme creates UIE, and the plugin created the videoplayer

[13:13:29 CDT(-0500)]

<anastasiac> so the VP IoC instantiation process doesn't have IoC access to

Unknown macro: {uiEnhancer}

[13:13:42 CDT(-0500)] <anastasiac> the UIE does get put into the static environment

[13:13:54 CDT(-0500)] <anastasiac> but there's no way for the VP to know for sure that it will be there in time

[13:14:00 CDT(-0500)] <anastasiac> and no way to "wait for it"

[13:14:16 CDT(-0500)] <anastasiac> so if VP is created before UIE, the hookup simply never happens

[13:14:28 CDT(-0500)] <anastasiac> does that make sense, michelled?

[13:14:54 CDT(-0500)] <michelled> yes, it does

[13:15:13 CDT(-0500)] <anastasiac> I could imagine other use cases such as a mash-up, or a portlet with the VP (or any other Infusion app)

[13:52:08 CDT(-0500)] <system64> Hey yzen!

[13:52:32 CDT(-0500)] <yzen> hey system64

[13:52:43 CDT(-0500)] <anastasiac> yzen, FYI, I've added a comment about this UIEnhancer creation timing to FLUID-5016

[13:52:49 CDT(-0500)] <yzen> anastasiac: thanks!

[13:53:13 CDT(-0500)] <anastasiac> Justin_o wondered if perhaps anything that might want a UIE should create it if it doesn't exist, and then the page enhancer would do the same.

[13:53:25 CDT(-0500)] <anastasiac> do you think something like that might work?

[13:53:50 CDT(-0500)] <system64> Still couldn't get the preference server running. I installed infusion and few dependencies

[13:54:33 CDT(-0500)] <yzen> system64: sorry to hear that, so what were the steps you undertook ?

[13:54:33 CDT(-0500)] <system64> When I do `node index` I get output as `function`.

[13:55:46 CDT(-0500)] <system64> Just separated preferenceServer module, and installed infusion, gpiiFramework and when modules from npm

[13:56:15 CDT(-0500)] <system64> I installed infusion from current master branch

[13:59:27 CDT(-0500)] <system64> yzen: Any other dependency I need to install?

[14:00:42 CDT(-0500)] <yzen> system64: so if you wanted something stand alone the safest way is to grab universal as a dependency itself

[14:00:53 CDT(-0500)] <yzen> https://github.com/GPII/NPGatheringTool/blob/master/package.json has an example of the working package.json with dependencies

[14:01:43 CDT(-0500)] <system64> yzen: I really have little idea about infusion module, could you tell me more about it? or if there is a wiki page about it.

[14:02:49 CDT(-0500)] <yzen> system64: unfortunately not really , since we are not yet publishing it to npm. This is however is it's package file https://github.com/fluid-project/infusion/blob/master/package.json

[14:03:12 CDT(-0500)] <system64> I did go through it (smile)

[14:03:34 CDT(-0500)] <yzen> system64: so in order to use the gpii frameowrk

[14:04:11 CDT(-0500)] <system64> How does infusion help us in backend?

[14:07:36 CDT(-0500)] <yzen> system64: we are taking advantage of the inversion of control on the server side which help us make the app more declarative over writing numerous functions/callbacks/etc

[14:07:40 CDT(-0500)] <yzen> so any ways

[14:07:51 CDT(-0500)] <yzen> check this thing out as well

[14:07:52 CDT(-0500)] <yzen> https://github.com/GPII/universal/blob/master/package.json

[14:09:29 CDT(-0500)] <yzen> dependencies there is all you'd need, and possibly even just a subset of it

[14:11:17 CDT(-0500)] <system64> yzen: I installed all the dependencies now, still getting `function` in my terminal when I do `node index.js`

[14:11:44 CDT(-0500)] <system64> I'm expecting it to fire http server on some port.

[14:13:35 CDT(-0500)]

<yzen> system64: so you might have logging disabled, so you wont see much, try making a request to a url that the pref server can handle and see what happens, e.g. localhost:8080/user/

Unknown macro: {token}

[14:16:00 CDT(-0500)] <system64> yzen: Don't think the server is running, is the port 8080 only?

[14:18:13 CDT(-0500)] <yzen> system64: when you are starting pref server are you doing it as described here https://github.com/GPII/universal/blob/master/gpii/node_modules/preferencesServer/README.md ?

[14:21:01 CDT(-0500)] <system64> I tried this `node node_modules/gpiiFramework/init.js configs`

[14:21:41 CDT(-0500)] <system64> inside pref Server directory, installed all modules there.

[14:29:47 CDT(-0500)] <yzen> system64: do you perhaps this stuff in github somewhere for me to take a look ?

[14:32:18 CDT(-0500)] <system64> I just installed the dependencies

[14:47:25 CDT(-0500)] <system64> yzen: Anything else I can try, I tried running server from universal repo still getting `function`.

[14:48:05 CDT(-0500)] <system64> yzen: Must be some issue with dependency, I think.

[14:53:15 CDT(-0500)] <yzen> system64: ill try going through the steps and see if i can document them for you

[14:54:10 CDT(-0500)] <system64> Thanks! yzen that would be really helpful (smile)

[15:16:46 CDT(-0500)] <mancoolgunda> hi

[15:17:11 CDT(-0500)] <mancoolgunda> I wanted to know where I can get the list of shortcuts available in FluidPlayer.

[15:17:19 CDT(-0500)] <mancoolgunda> Is it documented anywhere?

[15:17:46 CDT(-0500)] <mancoolgunda> I was going through this page : http://wiki.fluidproject.org/display/fluid/Video+Player_keyboard+shortcuts+summary

[15:23:45 CDT(-0500)] <anastasiac> hang on, mancoolgunda, let me dig that up

[15:25:03 CDT(-0500)] <anastasiac> mancoolgunda, we don't have a formal document describing the interactions yet, but we have the specification: http://wiki.fluidproject.org/display/fluid/%28Floe%29+video+player+interactions You should be able to find the information there. Let us know if you still have questions

[15:26:20 CDT(-0500)] <mancoolgunda> anastasiac: thanks a lot

[15:26:29 CDT(-0500)] <anastasiac> np

[15:29:07 CDT(-0500)] <yzen> fluid-everyone, colinclark: we have 2 names that we are trying to make a decision on: basic and starter. Some people do not like basic, because it sounds close to simple, and some do not like starter because it sounds incomplete. Do we have any other suggestions for names or can we can come to a decision with this names?

[15:29:30 CDT(-0500)] <colinclark> I think we need to just pick one (wink)

[15:29:58 CDT(-0500)] * jessm votes for basic

[15:30:07 CDT(-0500)] <colinclark> I don't think we've heard any showstoppers for either

[15:30:16 CDT(-0500)] <colinclark> nor any blazingly compelling arguments for either

[15:30:37 CDT(-0500)] <colinclark> We just need someone who feels like making a call

[15:30:42 CDT(-0500)] <colinclark> which I will do if you need me to

[15:30:49 CDT(-0500)] <colinclark> or anyone can do, too

[15:31:07 CDT(-0500)] <colinclark> up to you all

[15:31:20 CDT(-0500)] <yzen> i sort of made it already by putting it in my pull request (wink)

[15:31:48 CDT(-0500)] <avtar> yzen: when all else fails, just resort to using: bronze, silver, gold, platinum

[15:31:54 CDT(-0500)] <colinclark> lol

[15:32:13 CDT(-0500)] <michelled> bronzeActions

[15:32:23 CDT(-0500)] <colinclark> that suits me just fine, yzen

[15:32:53 CDT(-0500)] <yzen> sounds good, thanks colinclark

[15:33:17 CDT(-0500)] <colinclark> anyone feel strongly against yzen's choice?

[15:34:21 CDT(-0500)] <colinclark> that sounds like lazy consensus to me, yzen

[15:34:29 CDT(-0500)] <yzen> colinclark: cool

[15:39:29 CDT(-0500)] <jessm> yzen: send it to list

[15:39:48 CDT(-0500)] <colinclark> yes!

[15:40:33 CDT(-0500)] <colinclark> you can always remind them that if someone comes up with a brilliant alternative, there's still time before we cut 1.9 and it becomes a little harder to change