fluid-work IRC Logs-2013-06-18

[08:02:43 CDT(-0500)] <Justin_o_> cindyli: i think i actually got the settings panels to pull in options form the schema

[08:02:49 CDT(-0500)] <Justin_o_> hopefully this time i did it right

[08:03:30 CDT(-0500)] <cindyli> congrats, Justin_o_

[08:03:50 CDT(-0500)] <Justin_o_> cindyli: thanks how are things going on your end

[08:04:35 CDT(-0500)] <cindyli> Justin_o_: creating the test case for the issue i have with fluid.addSourceGuardedListener

[08:05:24 CDT(-0500)] <Justin_o_> cindyli: okay

[08:05:35 CDT(-0500)] <Justin_o_> cindyli: let me know if you need any help.. i have time to pair up now

[08:06:47 CDT(-0500)] <cindyli> Justin_o_: anytime

[09:33:09 CDT(-0500)] <anastasiac> hi, Bosmon7, are you there?

[12:25:22 CDT(-0500)] <anastasiac> jhung, I'm looking at your icon font docs. Is IcoMoon actually downloadable? Or do I use the website app?

[12:26:00 CDT(-0500)] <jhung> You can get it as a browser app for Chrome anastasiac. Not sure if there are other implementations of it.

[12:26:28 CDT(-0500)] <anastasiac> can I just use the website app, running in Firefox? or do I have to get the Chrome app?

[12:29:57 CDT(-0500)] <anastasiac> jhung, should I be giving the icons a tag for a name, or is that not necessary?

[12:30:30 CDT(-0500)] <anastasiac> should I be enabling ligatures, jhung

[12:30:31 CDT(-0500)] <anastasiac> ?

[12:31:33 CDT(-0500)] <jhung> Don't enable ligatures. Check Base 64 and Metadata.

[12:32:10 CDT(-0500)] <jhung> For infusion, Ive been following this convention: "InfusionIcons-Uploader" as the font name. Prefix "InfusionIcons"

[12:32:18 CDT(-0500)] <jhung> I'll be sure to add that to the documentation.

[12:37:07 CDT(-0500)] <anastasiac> jhung, the classnames used in UIO start with "fl-", as is our custom. Was that specified in icoMoon, with the 'prefix' option?

[12:38:38 CDT(-0500)] <anastasiac> "fl-icon-..."

[12:39:06 CDT(-0500)] <jhung> anastasiac: I did a quick look, and the classname actually doesn't matter.

[12:39:35 CDT(-0500)] <jhung> it's just the classname IcoMoon will use in the example index,html and css file it generates.

[12:40:41 CDT(-0500)] <anastasiac> in uiOptions, a classname is used to set the content of the span to the relevant character e.g. .fl-uiOptions .fl-icon-big-a:before {

[12:40:42 CDT(-0500)] <anastasiac> content: "\e006";

[12:40:42 CDT(-0500)] <anastasiac> }

[12:40:48 CDT(-0500)] <jhung> in our markup, in the instances where I had to create a container for the icon, I used fl-icon.

[12:41:11 CDT(-0500)] <anastasiac> ok, so we don't use the classname generated by iconmoon

[12:41:15 CDT(-0500)] <jhung> yeah.

[12:41:42 CDT(-0500)] <jhung> Or you could as long as you put in our standard class prefix.

[14:04:18 CDT(-0500)] <mancoolgunda> hi

[14:06:22 CDT(-0500)] <mancoolgunda> I am running Chrome v.27 and Fluid Player is not working on it. It works well in FF and IE but on Chrome it shows a blank player. Any idea why is it happening?

[14:44:50 CDT(-0500)] <mancoolgunda> anastasiac: hi

[14:45:04 CDT(-0500)] <anastasiac> mancoolgunda, hi

[14:45:22 CDT(-0500)] <anastasiac> video player in chrome

[14:45:23 CDT(-0500)] <mancoolgunda> I had a small doubt regarding Fluid Player

[14:45:30 CDT(-0500)] <anastasiac> are you using the latest code from github?

[14:47:08 CDT(-0500)] <mancoolgunda> ok i'll just do a quick pull and check. I had another doubt.

[14:47:27 CDT(-0500)] <mancoolgunda> So is it necessary to have the same folder structure.

[14:48:50 CDT(-0500)] <anastasiac> mancoolgunda, can you give me a quick overview of what you're trying to accomplish?

[14:50:49 CDT(-0500)] <mancoolgunda> I was reading the docs and was trying to initialize the Fluid Player myself. I had to have the "html" folder outside the current directory to make the player work. The rest of the folders "js", "lib" "css", I had them inside the current working directory and I changed the code accordingly. But the "html" folder was what was causing the problem.

[14:50:56 CDT(-0500)] <mancoolgunda> Ok, so a part of my GSoC project is to integrate FluidPlayer into ATutor.

[14:51:02 CDT(-0500)] <anastasiac> right

[14:51:10 CDT(-0500)] <mancoolgunda> I was following the demos and trying to make things work.

[14:51:14 CDT(-0500)] <anastasiac> when you say "current working directory," what do you mean?

[14:56:32 CDT(-0500)] <mancoolgunda> I have "player.html" which has the code to initialize the video player. Inside the same folder I have "js" "lib" "css" "images" and have modified the code accordingly. But I was still giving me an error and it was html folder not being placed correctly. I needed to have the html folder in one layer above the folder in which "player.html" resided.

[14:57:55 CDT(-0500)] <anastasiac> hm. that's odd. What exactly is inside your player.html file? Is it the javascript that calls "fluid.videoPlayer(…)" ?

[14:58:19 CDT(-0500)] <mancoolgunda> videoPlayer_template

[14:58:36 CDT(-0500)] <mancoolgunda> videoPlayer_template.html

[14:58:46 CDT(-0500)] <anastasiac> on, no

[14:58:56 CDT(-0500)] <anastasiac> you shouldn't be doing anything with that file

[14:59:13 CDT(-0500)] <anastasiac> the video player code will inject that html into the div where you want a video player to be

[14:59:27 CDT(-0500)] <anastasiac> does that make any sense?

[15:01:41 CDT(-0500)] <mancoolgunda> so I need to have such a hierarchy. www/html, www/fluidplayer/myplayer.html, www/fluidplayer/js and so on. I wanted to know if I could have the html folder also as part of the same directory and get things working. Is this not possible.

[15:01:42 CDT(-0500)] <mancoolgunda> ?

[15:03:25 CDT(-0500)] <anastasiac> mancoolgunda, the html folder should be in the same place as the js and css folders. This is how it should work. Your myplayer.html should contain a single <div> where you want the player to appear, and the javascript code. Does that make sense?

[15:03:57 CDT(-0500)] <mancoolgunda> ya, ok

[15:04:48 CDT(-0500)] <anastasiac> Is that what you've got in your myplayer.html, mancoolgunda?

[15:05:51 CDT(-0500)]

[15:06:33 CDT(-0500)] <mancoolgunda> I will do one thing. I will put it on the server so that you can quickly take a look at it. Do you have a few minutes?

[15:06:45 CDT(-0500)] <anastasiac> yes, send me a link

[15:06:52 CDT(-0500)] <mancoolgunda> cool, 2 mins.

[15:12:06 CDT(-0500)] <system64> Afternoon michelled!

[15:12:23 CDT(-0500)] <michelled> hi system64

[15:12:28 CDT(-0500)] <michelled> how are things going?

[15:14:35 CDT(-0500)] <system64> Had been trying to understand WebRTC API last few days, finally understood the signalling process today. And got 2 person video call working

[15:15:54 CDT(-0500)] <michelled> wow - that's great system64

[15:16:02 CDT(-0500)] <michelled> is the code somewhere we can see it?

[15:16:36 CDT(-0500)] <system64> The code still needs some work, but I'll push it to github today.

[15:17:24 CDT(-0500)] <system64> Do you think I should use a library for video conferencing?

[15:17:59 CDT(-0500)] <michelled> what libraries were you considering?

[15:18:12 CDT(-0500)] <system64> simplewebrtc.js was the one I wrote in my proposal.

[15:18:32 CDT(-0500)] <system64> Then there is easyWebRTC and webRTC.io

[15:18:55 CDT(-0500)] <system64> The API is very new, so its difficult to take call.

[15:20:29 CDT(-0500)] <system64> If we try to do it from scratch, we can also have chat and file sharing using WebRTC data channels. Not sure if any of these libraries have support for DataChannels.

[15:21:50 CDT(-0500)] <system64> Using DataChannels API would mean the communication would be peer to peer and the data won't be travelling through server.

[15:22:04 CDT(-0500)] <michelled> I think it makes sense to start by using simplewebrtc and build your system in a way that you can make a call later if you need something more complex or home built

[15:22:31 CDT(-0500)] <michelled> it's always good to develop in a way where pieces can be easily swapped out

[15:23:40 CDT(-0500)] <system64> Thanks, will try to keep that in mind.

[15:24:44 CDT(-0500)] <system64> michelled: Will this component be integrated into Infusion in future?

[15:25:19 CDT(-0500)] <michelled> possibly - although there has been some conversation around separating components from the framework

[15:26:13 CDT(-0500)] <michelled> so it might live in a separate repo like the infusion video player does

[15:28:36 CDT(-0500)] <system64> Using this component will require integration with backend, so it might be little different from other components.

[15:30:29 CDT(-0500)] <michelled> true

[15:30:42 CDT(-0500)] <system64> I'm going to be working on this component next few weeks now. Will start working on the component tomorrow.

[15:30:46 CDT(-0500)] <michelled> I guess the text to speech demo uses an back end, but we expect to eventually not require that

[15:31:22 CDT(-0500)] <michelled> that's great system64 - get your work into github as soon as you can so I can see what you're doing

[15:31:43 CDT(-0500)] <system64> Sure, thats the first thing tomorrow.

[15:32:04 CDT(-0500)] <michelled> great

[15:33:51 CDT(-0500)] <system64> I spent few days to understand the API. Always nice to understand things before using libraries

[15:34:24 CDT(-0500)] <system64> Any suggestions on the component name?

[15:37:29 CDT(-0500)] <michelled> hmmmm, I'm not sure - what were you thinking?

[15:42:27 CDT(-0500)] <system64> Not sure myself, fluid.webrtc maybe?

[15:46:30 CDT(-0500)] <michelled> that'll do for now