fluid-work IRC Logs-2013-06-21

[07:19:35 CDT(-0500)] <Justin_o> jhung: hi, good morning. I'm not sure if you saw this, but i left a comment on your pull request yesterday

[07:37:20 CDT(-0500)] <jhung> yep I saw that Justin_o. I'm fine with that.

[07:39:27 CDT(-0500)] <jhung> Justin_o: I left a comment on http://issues.fluidproject.org/browse/FLUID-4996 - what do you think of my proposed solution?

[07:41:33 CDT(-0500)] <Justin_o> jhung: the idea sounds reasonable. Part of the current interaction is to hide it when you are in the edit mode, so we'll have to make sure that is still possible

[07:43:28 CDT(-0500)] <jhung> Justin_o: I wonder if this will require a quick wireframe / spec outlining the behaviour of the edit icon? This is new functionality in a way...

[07:47:09 CDT(-0500)] <Justin_o> jhung: hmm possibly.. i'm not sure what design resources we currently have detailing the interaction for it

[07:49:05 CDT(-0500)] <jhung> Justin_o: I was thinking maybe just a point-form list just so we know what's supposed to happen. (i.e. if the edit icon appears outside the text field, then it should appear dimmed and not disappear).

[07:49:44 CDT(-0500)] <Justin_o> jhung: sure

[07:50:05 CDT(-0500)] <jhung> I guess I've volunteered to do that.

[07:50:31 CDT(-0500)] <Justin_o> jhung: haha.. yes.. i think so

[07:52:40 CDT(-0500)] <jhung> Alright. I'll get to that this morning. Then I'm off to do the image conversion for FSS.

[07:53:02 CDT(-0500)] <Justin_o> jhung: cool.. also can you make that change to your pull request and i'll review and get it in

[07:58:54 CDT(-0500)] <Justin_o> cindyli: i'm thinking of this for the update to our schema http://pastie.org/8066377

[07:59:34 CDT(-0500)] <Justin_o> i still have to add a few more in, but those should be the same as before

[07:59:44 CDT(-0500)] <cindyli> it looks good, Justin_o

[08:00:51 CDT(-0500)] <jhung> sure Justin_o

[10:13:32 CDT(-0500)] <jhung> Justin_o: I've added a comment here re: inline edit icon http://issues.fluidproject.org/browse/FLUID-4996#comment-23676

[10:13:46 CDT(-0500)] <jhung> - by default the edit icon appears immediately to the right of the editable text field.

[10:13:46 CDT(-0500)] <jhung> - edit mode can be activated by selecting the icon or by selecting the text field.

[10:13:46 CDT(-0500)] <jhung> - the edit icon by default dims when edit field is activated

[10:13:46 CDT(-0500)] <jhung> - hovering over the edit icon will produce an outline

[10:13:47 CDT(-0500)] <jhung> Using CSS, the user will be able to:

[10:13:47 CDT(-0500)] <jhung> - position the edit icon to where ever they want

[10:13:48 CDT(-0500)] <jhung> - modify dim style or hide the icon all together when edit mode is activated

[10:24:08 CDT(-0500)] <Justin_o> jhung: sounds good

[10:52:51 CDT(-0500)] <Justin_o> cindyli: what do you think of this http://wiki.fluidproject.org/display/fluid/Schema+for+UIO+preferences

[10:53:11 CDT(-0500)] <Justin_o> maybe we should remove the "format" property from the Captions Language? what do you think?

[11:10:50 CDT(-0500)] <Justin_o> anastasiac: you might be interested in this, in terms of the new UIO api proposal

[11:10:51 CDT(-0500)] <Justin_o> http://issues.fluidproject.org/browse/FLUID-4907

[11:11:10 CDT(-0500)] <Justin_o> it's an example of how we might use the builder with uio.. and suggests an api for them

[11:48:27 CDT(-0500)] <jhung> heidiv: ping

[11:48:32 CDT(-0500)] <heidiv> jhung howdy!

[11:48:42 CDT(-0500)] <jhung> got a question for you.

[11:48:46 CDT(-0500)] <heidiv> shoot

[11:50:08 CDT(-0500)] <jhung> Different FSS themes have exclusive images (i.e. android and ios themes have special back buttons). Separate fonts be created for these themes, correct or should FSS have only 1 font for all themes?

[12:03:15 CDT(-0500)] <jhung> Justin_o: ah there you are. I was asking heidiv this, but wondering if you had any thoughts?

[12:03:19 CDT(-0500)] <jhung> Different FSS themes have exclusive images (i.e. android and ios themes have special back buttons). Separate fonts be created for these themes, correct or should FSS have only 1 font for all themes?

[12:04:11 CDT(-0500)] <heidiv> jhung i would lean toward per-theme. i feel like some FSS stuff w images is dated and can be replaced by straight css

[12:04:19 CDT(-0500)] <Justin_o> jhung: that's an interesting question and might depend on what we think the future of FSS is

[12:04:26 CDT(-0500)] <Justin_o> meaning are we going to be adding more themes

[12:04:46 CDT(-0500)] <Justin_o> if so we might want things to be more modular as we won't want to be updating the font file all the time, but if not.. then a single file might be easier to use

[12:04:56 CDT(-0500)] <Justin_o> colinclark: do you have any thoughts on FSS

[12:05:37 CDT(-0500)] <Justin_o> heidiv: that's a good point too… as long as those updates work across our supported browsers that would be a better approach that carrying around the images

[12:06:10 CDT(-0500)] <heidiv> for ex. i think fss has images for "the left side of a button" and the "right side of a button" … now i'm guessing we'd just want css styling.

[12:06:25 CDT(-0500)] <heidiv> v.s make the left side of a button a font icon

[12:06:35 CDT(-0500)] <heidiv> jhung am i right about that being in FSS?

[12:06:39 CDT(-0500)] <jhung> yep

[12:06:48 CDT(-0500)] <heidiv> yeah… any other stuff like that in there?

[12:07:02 CDT(-0500)] <heidiv> any actual icons?

[12:07:31 CDT(-0500)] <jhung> There are some actual icons, but majority are those button borders you described heidiv

[12:08:00 CDT(-0500)] <heidiv> maybe we should leave those be imgs for now and just tackle the icons for font icon update

[12:08:12 CDT(-0500)] <heidiv> and make a jira for replacing button borders w css

[12:08:25 CDT(-0500)] <jhung> Sounds good heidiv. I'll file a jira.

[12:09:06 CDT(-0500)] <jhung> As for font icon conversion, we'll go with separate icon files per them if theme requires it.

[12:19:52 CDT(-0500)] <vjoanna> hey jhung, i just read through the inline edit change you're thinking - i really like it! one question, do you mean the edit icon will appear to the right of the edit text or to the right of the whole text field?

[12:20:47 CDT(-0500)] <jhung> right of the whole text field by default vjoanna. But they can reposition that using CSS if they wish.

[12:22:23 CDT(-0500)] <colinclark> my thoughts about the FSS, Justin_o, are a bit like my thoughts on the Renderer

[12:22:43 CDT(-0500)] <colinclark>

[12:25:45 CDT(-0500)] <vjoanna> jhung: what do you think if by default it's positioned to the left of the whole text field? i'm worried that if it's a long text field there might be some disconnect between the edit text and the icon? unless we have some styling to visually group them

[12:31:13 CDT(-0500)] <jhung> vjoanna: You think there would be a disconnect? I think there may be enough visual cues (hover effects, focus styling etc) to reinforce an editable field. It also seems a bit unconventional to have the edit icon appear before the text that is editable, no? Most implementations I've seen have it at the "end" of the text.

[12:32:43 CDT(-0500)] <heidiv> thinking of a form field, w some feilds editable and some not - the left icon on some would misalign the input boxes… might be weird?

[12:33:12 CDT(-0500)] <heidiv> not sure how popular a use case that would be

[12:39:53 CDT(-0500)] <vjoanna> jhung: yeah, i think you're right - the convention seems to be on the right.. i took a closer look at the demo, the blue underline it has would probably be enough to indicate that it belongs the icon and text belong together

[12:42:20 CDT(-0500)] <jhung> vjoanna: agreed. I think as long as we have enough cues to indicate the field is editable and that the icon belongs to that field, I think it should be okay.

[12:47:36 CDT(-0500)] <Justin_o> colinclark: okay… i'll keep that in mind

[13:44:26 CDT(-0500)] <colinclark> thealphanerd: It looks like you're not alone in experimenting with asm.js and Emscripten for audio: https://gist.github.com/automata/5832104

[13:44:34 CDT(-0500)] <colinclark> This is a guy named Vilson Vieria

[13:44:57 CDT(-0500)] <thealphanerd> HA

[13:45:00 CDT(-0500)] <thealphanerd> that's a buddy of mine

[13:45:23 CDT(-0500)] <colinclark> http://lists.w3.org/Archives/Public/public-audio/2013AprJun/0610.html

[13:45:39 CDT(-0500)] <colinclark> So are you done with your experiments at this point?

[13:45:46 CDT(-0500)] <colinclark> Or do you have a plan to finish the work at some point?

[13:46:02 CDT(-0500)] <thealphanerd> talking to him right now

[13:46:08 CDT(-0500)] <thealphanerd> I plan to keep working on it

[13:46:15 CDT(-0500)] <thealphanerd> was moving last week

[13:46:17 CDT(-0500)] <thealphanerd> and first week of work

[13:46:26 CDT(-0500)] <thealphanerd> but plan on getting back in to the swing of it soon

[13:46:34 CDT(-0500)] <thealphanerd> julius said we should be testing an impulse in to freeverb

[13:46:48 CDT(-0500)] <thealphanerd> so we can do not just performance tests, but get a feeling for how the algorithms sound

[13:46:54 CDT(-0500)] <thealphanerd> he is really excited to see benchmarks

[13:48:21 CDT(-0500)] <colinclark> Ah, that's interesting

[13:48:36 CDT(-0500)] <colinclark> He wants to see if there is some kind of loss of fidelity?

[14:00:16 CDT(-0500)] <thealphanerd> it is pretty funny that he is doing it… we were also both doing osc in the browser

[14:00:21 CDT(-0500)] <thealphanerd> we have similar thought pattens

[14:10:06 CDT(-0500)] <colinclark> that's really great, thealphanerd

[14:13:05 CDT(-0500)] <thealphanerd> we're talking about it in #ccrma if you want to pop in

[14:13:11 CDT(-0500)] <thealphanerd> vilson might help with the project now

[14:13:16 CDT(-0500)] <thealphanerd> thanks for pointing that out

[14:13:19 CDT(-0500)] <thealphanerd> such a funny small world

[14:42:41 CDT(-0500)] <mancoolgunda> anastasiac: hi

[14:42:51 CDT(-0500)] <anastasiac> mancoolgunda, hi

[14:44:14 CDT(-0500)] <mancoolgunda> I was going through the builder page and I was wondering if I selected all options and created a build, would that resolve all issues? I mean can that be considered a master build including everything that Fluid Player as well ATutor needs?

[14:44:39 CDT(-0500)] <mancoolgunda> Actually I remember trying that out, and it was still giving me videoPlayer function not defined.

[14:45:16 CDT(-0500)] <anastasiac> Well, if you include everything, you're probably including some stuff that ATutor doesn't need. Did you check with greggy to see what ATutor needs?

[14:45:57 CDT(-0500)] <mancoolgunda> yes I am talking to cindyli in the atutor channel, right now about this.

[14:47:06 CDT(-0500)] <anastasiac> well, I would recommend only including what's necessary for ATutor and for VideoPlayer. But that should be enough

[14:47:18 CDT(-0500)] <mancoolgunda> ok.

[14:47:52 CDT(-0500)] <mancoolgunda> by the way, which module is needed for video Player to function. I mean on the builder page is there any module which includes the video Player functions?

[14:48:15 CDT(-0500)] <anastasiac> ah, good question

[14:48:27 CDT(-0500)] <anastasiac> I'll double-check the video player's requirements

[14:48:33 CDT(-0500)] <mancoolgunda> sure.

[14:49:32 CDT(-0500)] <anastasiac> mancoolgunda, the list of requirement for video player is: enhancement, uiOptions, progress, tooltip, jQueryScrollToPlugin

[14:50:23 CDT(-0500)] <mancoolgunda> cool, I just got the list of modules on which ATutor is dependent as well. Will create a custom build

[14:50:29 CDT(-0500)] <anastasiac> perfect