fluid-work IRC Logs-2011-06-22

Owned by Fluid IRC Log Bot
Last updated: Jun 22, 2011Version comment
16 min read

[08:17:21 CDT(-0500)] <huslage> morning
[08:29:44 CDT(-0500)] <lahabana> morning
[08:50:28 CDT(-0500)] <lahabana> hey guys I need somebody to help me clarify something
[08:50:42 CDT(-0500)] <lahabana> is anybody not busy atm?
[08:51:10 CDT(-0500)] <jessm> lahabana: you might ping someone in particular – but go ahead and ask your question, perhaps I can help direct you
[08:51:22 CDT(-0500)] <lahabana> ho ok sorry
[08:51:42 CDT(-0500)] <jessm> oh no worries, just wanted to make sure you got a reply!
[08:52:03 CDT(-0500)] <lahabana> well I'm working on something that from any type of caption files returns an object of the same shape
[08:52:13 CDT(-0500)] <lahabana> I was think of creating a subComponent
[08:52:36 CDT(-0500)] <lahabana> but every components is supposed to have interaction with the UI no?
[09:04:11 CDT(-0500)] <Justin_o> lahabana: not every component has to affect the ui directly
[09:04:22 CDT(-0500)] <lahabana> ho ok thx
[09:04:46 CDT(-0500)] <Justin_o> lahabana: there is a type of component called littleComponent which doesn't have a dom binder. so you don't have to pass in a container, just options
[09:04:48 CDT(-0500)] <lahabana> so I just do my subcomponent with no container
[09:05:03 CDT(-0500)] <lahabana> ho great
[09:05:16 CDT(-0500)] <lahabana> where can I get all the different types of components
[09:05:29 CDT(-0500)] <lahabana> I've searched in the doc but couldn't find it...
[09:05:37 CDT(-0500)] <Justin_o> lahabana: i'll see if i can find something, one second
[09:05:44 CDT(-0500)] <lahabana> cheers
[09:07:23 CDT(-0500)] <Justin_o> lahabana: i think you have started using our new IoC style yet, this doc is from that, but has some information for different component types that you can call directly. http://wiki.fluidproject.org/display/docs/Component+Grades
[09:07:38 CDT(-0500)] <Justin_o> although you can't do so with all component types
[09:08:13 CDT(-0500)] <lahabana> ok I'll be carefull then
[09:08:33 CDT(-0500)] <anastasiac> lahabana, I'm starting on a tutorial that explains the different component grades. Have a look, and let me know if you have any questions: http://wiki.fluidproject.org/display/docs/Getting+Started+Tutorial+%28in+development%29
[09:08:37 CDT(-0500)] <Justin_o> lahabana: here's a page about little component http://wiki.fluidproject.org/display/docs/fluid.initLittleComponent the lower portion of the page is more specific to the IoC style, but the top shows how you would call it directly
[09:09:04 CDT(-0500)] <lahabana> ok thx for eveything
[09:09:17 CDT(-0500)] <lahabana> I read all that and let you know if I've got any questions
[09:09:34 CDT(-0500)] <colinclark> lahabana: I haven't forgotten about your code
[09:09:43 CDT(-0500)] <colinclark> it's been a busy few days, but I'll take a look today
[09:09:48 CDT(-0500)] <lahabana> no probs
[09:09:53 CDT(-0500)] <lahabana> cheers
[09:10:35 CDT(-0500)] <Justin_o> colinclark: so we were talking yesterday about our a-grade support now that FF 5 is out
[09:10:46 CDT(-0500)] <colinclark> Justin_o: okay, yep
[09:11:00 CDT(-0500)] <Justin_o> colinclark: so yahoo put out a blog post about their GBS http://www.yuiblog.com/blog/2011/05/27/quick-gbs-status-update/
[09:11:16 CDT(-0500)] <Justin_o> basically they'll update it in Q2 sometime, which i figure we're in at the moment.. so any time now
[09:12:25 CDT(-0500)] <Justin_o> colinclark: I think we chatted about this one at the beginning of the month, but here's google's new stance for their web apps http://googleenterprise.blogspot.com/2011/06/our-plans-to-support-modern-browsers.html
[09:12:55 CDT(-0500)] <Justin_o> basically they will only support current and previous for Chrome, FF, IE and Safari, although they don't mention any details about which OS they will support
[09:14:26 CDT(-0500)] <Justin_o> colinclark: So i suppose we have a few options for what we do now... 1) keep going with our current a-grade and wait for yahoo to update 2) change to a more googlesque style
[09:14:32 CDT(-0500)] <Justin_o> 3) something else
[09:15:16 CDT(-0500)] <colinclark> Assuming we switched to the Google style, with an IE 6 exception, what impact would it have on our testing surface?
[09:15:16 CDT(-0500)] <Justin_o> if we go with option 2 we'll have to decide which OS's we'd like to support, for the time being we can take that from our current a-grade chart, but going forward this would be more work to decide
[09:16:14 CDT(-0500)] <Justin_o> colinclark: the other exception would be for only supporting the latest chrome i think too
[09:16:22 CDT(-0500)] <colinclark> right
[09:16:32 CDT(-0500)] <colinclark> since we couldn't even know what the previous Chrome is
[09:16:42 CDT(-0500)] <colinclark> only Google could possibly know (smile)
[09:17:01 CDT(-0500)] <Justin_o> if we keep the same configs as we have now.. so only testing chrome on xp for example.. we'll probably end up breaking about even with what we have now
[09:17:26 CDT(-0500)] <Justin_o> i guess the other exception would be not testing previous safari too.. we only do safari 5 at the moment i think
[09:18:32 CDT(-0500)] <Justin_o> we would basically just be replacing FF 3.6 with FF 5
[09:19:29 CDT(-0500)] <Justin_o> if we keep testing IE 7 on XP ( which would be the previous config) and replacing FF3.6 on xp with FF4 and FF5 we would be adding 1 extra configuration to test
[09:20:59 CDT(-0500)] <Justin_o> colinclark: with all these exceptions, there's no point in calling this googlesque.. this is really option 3.. do something else.. which is to say, replace FF3.6 with FF5
[09:21:20 CDT(-0500)] <Justin_o> if we release in the next couple of weeks though.. i wonder if it's to early to do that
[09:26:00 CDT(-0500)] <colinclark> It's a good question
[09:26:17 CDT(-0500)] <colinclark> I expect FF5 will eat FF4's market share very quickly
[09:26:35 CDT(-0500)] <colinclark> Perhaps less so for Firefox 3.6
[09:26:40 CDT(-0500)] <colinclark> but it's hard to know
[09:27:45 CDT(-0500)] <Justin_o> colinclark: i'm not so sure how it will all go.. FF4 had a big push, they sort of just snuck FF5 out and I'm not sure it will have a ton of stuff that will pull people off of FF4
[09:28:24 CDT(-0500)] <colinclark> Well, I assume that they expect it to propagate via updates in the browser, rather than people running off to download a new version
[09:28:45 CDT(-0500)] <Justin_o> colinclark: right.. did you get an update request from FF4 yet..
[09:28:52 CDT(-0500)] <Justin_o> ?
[09:29:22 CDT(-0500)] <colinclark> The problem is that I'm running a beta channel browser
[09:29:23 CDT(-0500)] <colinclark> so yes
[09:29:26 CDT(-0500)] <Justin_o> (smile)
[09:29:29 CDT(-0500)] <colinclark> but that doesn't count
[09:29:48 CDT(-0500)] <Justin_o> colinclark: i haven't in my stable version, my beta one did update though
[09:30:56 CDT(-0500)] <Justin_o> colinclark: okay.. so i went to the about page and it pushed me to FF5
[09:31:08 CDT(-0500)] <Justin_o> which has now ruined my FF 4 install (sad)
[09:31:11 CDT(-0500)] <colinclark> eek
[09:31:17 CDT(-0500)] <colinclark> it did it automatically?
[09:31:26 CDT(-0500)] <Justin_o> colinclark: sort of...
[09:31:41 CDT(-0500)] <Justin_o> it did ask me to download, but I don't think it told me the version
[09:31:55 CDT(-0500)] <Justin_o> so i figured it would just be some FF4 intermediate update..
[09:33:30 CDT(-0500)] <colinclark> lahabana: I guess it depends on the purpose of the caption tracks
[09:33:33 CDT(-0500)] <lahabana> colinclark: cause changing caption will be really quick if they are already loaded but is that really usefull as much people will just choose their caption and won't change
[09:33:43 CDT(-0500)] <colinclark> If you've got a series of captions, say in different languages, they're relatively exclusive of each other
[09:34:15 CDT(-0500)] <lahabana> yes what I mean by caption file is the captions for the whole video
[09:34:15 CDT(-0500)] <colinclark> whereas in other cases you may have multiple caption tracks to manage different types of caption layouts, additional information, etc.
[09:34:25 CDT(-0500)] <lahabana> so captions can differ by language or format
[09:34:49 CDT(-0500)] <lahabana> like?
[09:35:32 CDT(-0500)] <lahabana> u mean that more than one caption track would be player a the time?
[09:35:59 CDT(-0500)] <lahabana> *displayer
[09:36:42 CDT(-0500)] <colinclark> lahabana: Yes, it's quite possible
[09:36:55 CDT(-0500)] <colinclark> heidi: CapScribe on the desktop used to support multiple caption tracks at once, right?
[09:37:11 CDT(-0500)] <heidi> colinclark yep
[09:37:16 CDT(-0500)] <heidi> captions and subtitles
[09:37:56 CDT(-0500)] <heidi> i think you could also put in images as well
[09:38:00 CDT(-0500)] <lahabana> ho ok
[09:38:06 CDT(-0500)] <lahabana> I didn't consider that
[09:38:34 CDT(-0500)] <heidi> and i think plans for a second video track as well, but don't think it was working (for sign languages for ex)
[09:39:06 CDT(-0500)] <heidi> and definitely audio descriptions
[09:39:35 CDT(-0500)] <lahabana> yes I had consider audi description
[09:39:49 CDT(-0500)] <heidi> that's why instead of calling something a "caption" we called it a "clip" because a clip could contain text, images, video... caption is just text
[09:40:06 CDT(-0500)] <lahabana> ok
[09:40:30 CDT(-0500)] <heidi> also my understanding is that a "caption" is in the same language as the video whereas "subtitle" are in another language
[09:40:40 CDT(-0500)] <lahabana> ho ok
[09:40:46 CDT(-0500)] <lahabana> I didn't know that difference
[09:41:23 CDT(-0500)] <colinclark> It's more subtle than that, heidi and lahabana
[09:41:30 CDT(-0500)] <heidi> tho i think subtitle can include both captions and a subtitle... hehe... that's how i use the terms anyway
[09:41:33 CDT(-0500)] <colinclark> Let me see if I can dig up a good link
[09:41:45 CDT(-0500)] <colinclark> but the key differences between captions and subtitles relate to what's being described
[09:42:02 CDT(-0500)] <colinclark> So, as an example, a caption track will describe a change in speakers
[09:42:16 CDT(-0500)] <colinclark> For example, if Heidi and Charly were talking on a video
[09:42:22 CDT(-0500)] <colinclark> and suddenly Heidi started talking
[09:42:26 CDT(-0500)] <colinclark> the caption track would notate that
[09:42:33 CDT(-0500)] <colinclark> Whereas subtitles just contain the spoken dialogue
[09:42:39 CDT(-0500)] <heidi> really?
[09:42:44 CDT(-0500)] <colinclark> Another key different is the description of sounds and sound effects
[09:42:44 CDT(-0500)] <lahabana> ok I see
[09:42:45 CDT(-0500)] <colinclark> music
[09:42:46 CDT(-0500)] <colinclark> other details
[09:43:26 CDT(-0500)] <lahabana> ok so what is named "subtitles for hearing impaired" on dvds are captions if I get it right?
[09:43:53 CDT(-0500)] <heidi> caption is a kind of subtitle that is same-language as video, is my understanding
[09:44:05 CDT(-0500)] <heidi> so yes
[09:44:12 CDT(-0500)] <colinclark> heidi: As I say, there's more to it than that... those differences are really key
[09:44:16 CDT(-0500)] <colinclark> in terms of the notation of speaker changes
[09:44:26 CDT(-0500)] <colinclark> sounds
[09:44:27 CDT(-0500)] <colinclark> etc.
[09:44:29 CDT(-0500)] <colinclark> This is a nice quick overview: http://screenfont.ca/learn/
[09:44:46 CDT(-0500)] <heidi> for sure. i didn't know translations didn't incl that. or are you saying a translation can be a caption if it includes that stuff?
[09:44:56 CDT(-0500)] <colinclark> Typically subtitles don't
[09:44:57 CDT(-0500)] <heidi> i always thought caption = same lang
[09:45:09 CDT(-0500)] <colinclark> they just narrate the spoken dialogue
[09:45:48 CDT(-0500)] <heidi> semantics aside lahabana, all of these features are definitely things to keep in mind (wink)
[09:46:00 CDT(-0500)] <colinclark> totally (smile)
[09:46:03 CDT(-0500)] <lahabana> yes (smile)
[09:46:30 CDT(-0500)] <heidi> lahbana it's so awesome you're working on this for our video player. going well?
[09:46:57 CDT(-0500)] <lahabana> sorry? I don't understand what you just said ...
[09:47:12 CDT(-0500)] <heidi> lahabana how is the caption work going?
[09:47:18 CDT(-0500)] <lahabana> Work is going well if that's what you meant
[09:47:24 CDT(-0500)] <heidi> (smile)
[09:47:47 CDT(-0500)] <lahabana> slowly I'm really trying to extract everything and having a good view of what to do and how
[09:48:08 CDT(-0500)] <lahabana> that's a really big piece (smile)
[09:49:23 CDT(-0500)] <lahabana> heidi: I was think for the different format supported to fetch them and create an object
[09:49:39 CDT(-0500)] <lahabana> so the actual use of them would always be the same
[09:49:44 CDT(-0500)] <lahabana> what do you of that?
[09:50:10 CDT(-0500)] <lahabana> the thing I'm affraid of is to end up with something slow
[09:51:26 CDT(-0500)] <lahabana> as exporting it to a new format will require to read them a first time before being able to use them
[09:51:31 CDT(-0500)] <heidi> lahabana did you take a look at the caption conversion service i emailed awhile back?
[09:51:44 CDT(-0500)] <heidi> are you thinking of doing something similar with fluid components?
[09:52:09 CDT(-0500)] <lahabana> just remembered u sent them ...
[09:52:13 CDT(-0500)] <lahabana> thx for the reminder
[09:52:25 CDT(-0500)] <lahabana> I read them but forgot them (smile)
[09:52:36 CDT(-0500)] <heidi> np - it was created by another student, using php objects
[09:52:48 CDT(-0500)] <heidi> our video player could likely make use of it
[09:53:02 CDT(-0500)] <lahabana> well now that you reminded me about that it's gonna be of great use
[09:53:05 CDT(-0500)] <heidi> lahabana also check out universal subtitles if you haven't yet
[09:53:21 CDT(-0500)] <lahabana> yes I checked it
[09:53:41 CDT(-0500)] <lahabana> it's true that the caption conversion would be much better if it was done server side
[09:54:43 CDT(-0500)] <heidi> lahabana yes some other software we worked on in the past (opencaps.idrc.ocad.ca) used it and it worked well
[09:54:47 CDT(-0500)] <lahabana> so I'll just have to modify the ajax query to send the type with the link
[09:54:58 CDT(-0500)] <heidi> hm, huslage thoughts on that url? opencaps.idrc.ocad.ca ... think that's right
[09:55:08 CDT(-0500)] <heidi> getting "server not found"
[09:55:11 CDT(-0500)] <huslage> sexc
[09:55:12 CDT(-0500)] <huslage> sec
[09:55:29 CDT(-0500)] <heidi> lahabana yep you would change the arguments sent via the url
[09:55:36 CDT(-0500)] <lahabana> http://opencaps.idrc.ocad.ca/site/ ?
[09:56:01 CDT(-0500)] <jhung> mlam: you did some work on Uploader, right?
[09:56:01 CDT(-0500)] <huslage> works for me heidi
[09:56:14 CDT(-0500)] <mlam> yes, i did
[09:56:34 CDT(-0500)] <lahabana> heidi: for me too
[09:56:48 CDT(-0500)] <heidi> strange it's loading now - good stuff
[09:56:49 CDT(-0500)] <jhung> mlam: when you're free, I'd like your help with a bug related to FLUID-962 (long filename bug).
[09:58:01 CDT(-0500)] <heidi> lahabana this was an web based caption editor i worked on a couple years ago. the conversion service was used, and accepted my own json caption format as well, which i think the video player also uses right colinclark ... json
[09:58:27 CDT(-0500)] <colinclark> yep
[09:58:28 CDT(-0500)] <lahabana> yes currently it's a json
[09:58:42 CDT(-0500)] <lahabana> looks like that: {"inTime":"00:00:04.203","outTime":"00:00:05.498","caption_text":"Hi, I'm Anastasia. \n","textStyles":{"text-align":"center"}},
[09:58:50 CDT(-0500)] <heidi> lahbana yes so the caption service will accept this native format then
[09:59:03 CDT(-0500)] <lahabana> ok that's great
[09:59:17 CDT(-0500)] <lahabana> I'll put that in place for the conversion then
[09:59:28 CDT(-0500)] <colinclark> I think a big interest of ours should be to handle a handful of the most prominent caption formats out in the wild
[09:59:34 CDT(-0500)] <heidi> lahabana what did you think of universal subtitles
[09:59:48 CDT(-0500)] <lahabana> well I think it's a really great idea
[09:59:57 CDT(-0500)] <lahabana> however really lacks of doc (smile)
[09:59:58 CDT(-0500)] <heidi> did you try adding it to the vid player?
[10:00:21 CDT(-0500)] <lahabana> not yet
[10:01:02 CDT(-0500)] <lahabana> focusing on the normal thing ftm and will deal with universal subtitles in a bit
[10:01:25 CDT(-0500)] <mlam> Sure , jhung
[10:03:24 CDT(-0500)] <lahabana> so the format currently used in the videoPlayer is JSON openCaps yes?
[10:04:40 CDT(-0500)] <heidi> lahabana same format yes
[10:04:54 CDT(-0500)] <lahabana> ok thx just checking I had the right name (smile)
[10:13:53 CDT(-0500)] <jhung> anastasiac: Are you working on Fluid-4287 (updating HC/HCI themes to use icons/widgets)?
[10:14:23 CDT(-0500)] <anastasiac> jhung, I'm done for now - I've posted a pull request. The work is in a branch of my github repo
[10:15:37 CDT(-0500)] <jhung> anastasiac: you may need to help walk me through that. I've never dealt with a pull request before.
[10:16:24 CDT(-0500)] <anastasiac> ah. Well, the first step is to look at the pull request, and the diffs, and do a code review - decide if the changes are good
[10:19:23 CDT(-0500)] <anastasiac> jhung: https://github.com/fluid-project/infusion/pull/82
[10:20:58 CDT(-0500)] <jhung> anastasiac: yep. Going through that now.
[10:26:20 CDT(-0500)] <jhung> anastasiac: okay. I want to pull down your branch to take a look at the changes in a browser. I added your repo and fetched.
[10:26:45 CDT(-0500)] <jhung> what should I do next, create my own branch and merge yours into mine?
[10:30:09 CDT(-0500)] <cindyli> Justin_o: is this the standup room: http://connect.ocad.ca/fluid-work
[10:30:46 CDT(-0500)] <Justin_o> cindyli: i think so, we're still getting setup over here, we should be on soon
[10:31:47 CDT(-0500)] <cindyli> thanks, Justin_o
[10:56:59 CDT(-0500)] <huslage> sorry i missed standup. was heads down again and didn't see the time. happens that 11:30 is pretty productive for me, so i get lost.
[10:57:24 CDT(-0500)] <huslage> I'm working with colinclark and jessm on rationalizing what services live where in our network.
[11:13:51 CDT(-0500)] <colinclark> lahabana and heidi: Here's a blog post from someone who is playing around with ARIA live regions for doing audio descriptions
[11:13:53 CDT(-0500)] <colinclark> http://accessibility.oit.ncsu.edu/blog/2011/06/14/html-5-video-text-tracks-and-audio-descriptions-made-easy-or-at-least-easier/
[11:14:00 CDT(-0500)] <colinclark> It's an interesting idea
[11:14:08 CDT(-0500)] <colinclark> not really viable in reality, but interesting
[11:14:26 CDT(-0500)] <colinclark> since we know that users other than those with screen readers might still benefit from audio descriptions
[11:17:29 CDT(-0500)] <colinclark> but it's a nice web variation on the stuff Charles has been experimenting with in terms of converting captions to audio using a text to speech engine
[11:17:37 CDT(-0500)] <colinclark> one more reason why we need a TTS API in the browser
[11:17:58 CDT(-0500)] <lahabana> ok I'll have a look
[11:19:29 CDT(-0500)] <lahabana> colinclark: I've been experimenting the php module that heidi gave me it's working well with a few tests I've done. I'll commit that in a bit to my FLUID-4297 branch
[11:19:49 CDT(-0500)] <colinclark> lahabana: What are you doing with the module, in particular?
[11:20:01 CDT(-0500)] <heidi> neat colin, thanks for the link
[11:21:27 CDT(-0500)] <lahabana> well I give him my captions in different formats than JSONcc and it converts them to it
[11:21:50 CDT(-0500)] <lahabana> so that the parser in Js can display them
[11:22:42 CDT(-0500)] <Justin_o> yura_: I have an IoC question
[11:23:04 CDT(-0500)] <Justin_o> for an invoker, can i use a demands block to replace it but not with a named function but with a resolved function
[11:23:13 CDT(-0500)] <lahabana> the idea is to have the parser only for JSONcc
[11:23:38 CDT(-0500)] <yura_> Justin_o: you mean with something of type function ?
[11:23:44 CDT(-0500)] <Justin_o> yura_: yes
[11:23:54 CDT(-0500)] <Justin_o> actually it's not an invoker, it's a subComponent
[11:23:59 CDT(-0500)] <yura_> Justin_o: I don't thing so
[11:24:04 CDT(-0500)] <Justin_o> ;(
[11:49:34 CDT(-0500)] <Justin_o> cindyli, heidi: wondering if you could provide some information about the testSize and lineSpacing settins in uiOptions
[11:49:51 CDT(-0500)] <heidi> sure what's up?
[11:50:19 CDT(-0500)] <Justin_o> wondering how under-the-hood the those are set.. i think they are styles injected into the page
[11:50:23 CDT(-0500)] <Justin_o> is that correct?
[11:50:28 CDT(-0500)] <cindyli> yes, Justin_o
[11:50:31 CDT(-0500)] <heidi> yep i think they are put inline on body
[11:50:42 CDT(-0500)] <Justin_o> cindyli: are they set in px?
[11:50:42 CDT(-0500)] <cindyli> by setting container.css("font-size", "...")
[11:50:54 CDT(-0500)] <cindyli> font size is in px, line spacing in em
[11:52:05 CDT(-0500)] <Justin_o> cindyli: what is the reason why we have to look at the computed style and set inline styles.. over using classes..
[11:54:22 CDT(-0500)] <heidi> jhung are you able to take a peak at my 4230 with IE7 sometime? i think something's up but need to confirm with a 'real' install
[11:54:44 CDT(-0500)] <cindyli> Justin_o: i think one reason is that we cannot predict what the original font size/line spacing would be, so hard to determine the css classes. If one px/em maps to one css class, many classes would be required.
[11:55:24 CDT(-0500)] <Justin_o> I was thinking a class per multiplier level
[11:55:38 CDT(-0500)] <jhung> heidi: sure. I can check using the test machine. Do you have it served somewhere?
[11:55:48 CDT(-0500)] <heidi> jhung it's just on github
[11:56:11 CDT(-0500)] <cindyli> Justin_o: is that possible with css class?
[11:56:47 CDT(-0500)] <jhung> heidi: k. i'll grab that then.
[11:56:56 CDT(-0500)] <cindyli> Justin_o: i think css class must specify in px or em which is the computed number of original_size * muliplication_factor
[11:58:22 CDT(-0500)] <Justin_o> cindyli: i think ems behave like multipliers themselves
[11:58:42 CDT(-0500)] <Justin_o> based on the parent element's size
[11:58:52 CDT(-0500)] <Justin_o> i guess in our case that would be the default from the <html> element
[12:09:48 CDT(-0500)] <cindyli> Justin_o: default is a special case, what if the user's page has its own size defined?
[12:11:11 CDT(-0500)] <cindyli> Justin_o: for instance, if customized size == 1.4em, mutiplier is set to 2, ui options needs to apply 2.8em
[12:15:16 CDT(-0500)] <jhung> heidi: ok. I'm up and running now. What am I looking for?
[12:17:41 CDT(-0500)] <heidi> how's it look?
[12:20:48 CDT(-0500)] <jhung> The fat panel looks weird.
[12:20:54 CDT(-0500)] <mlam> cindyli: I think as you said, we can't predict the original size font, so even when the fat panel first opens, the sizing may be off.
[12:21:02 CDT(-0500)] <jhung> like it's floating left and right.
[12:21:03 CDT(-0500)] <heidi> jhung yep. can you figure out what's happening?
[12:21:05 CDT(-0500)] <heidi> yeah
[12:21:09 CDT(-0500)] <heidi> okay same as mine then
[12:21:53 CDT(-0500)] <jhung> heidi, I can take a look.
[12:23:36 CDT(-0500)] <cindyli> mlam: why "the sizing may be off" at the first open? ui enhancer is not instantiated? once ui enhancer is instantiated, it should set the sizing based on saved settings
[12:23:52 CDT(-0500)] <cindyli> mlam: no soccer today?
[12:25:10 CDT(-0500)] <mlam> cindyli: no soccer today.
[12:25:18 CDT(-0500)] <cindyli> oh, no
[12:25:52 CDT(-0500)] <heidi> jhung looking good on other browsers ya?
[12:26:20 CDT(-0500)] <jhung> heidi iE8, FF3.6 look fine.
[12:26:28 CDT(-0500)] <heidi> great
[12:26:38 CDT(-0500)] <heidi> will have to wait till it's on a server to try chrome
[12:26:59 CDT(-0500)] <mlam> cindyli: I think the main problem is when the panel is hidden. it takes a bit of time to calculate the initial size of the font before adjusting all the settings on the Fat panel, so there's not a smooth transition. Is there an elegant way of making the initial font size always available?
[12:27:35 CDT(-0500)] <cindyli> mlam: right
[12:28:11 CDT(-0500)] <cindyli> mlam: as the iframe is initially in hidden state, ui enhancer may not be able to find the original sizes
[12:28:14 CDT(-0500)] <jhung> heidi: IE6 looks about the same as IE7, but the icons are also messed up because of PNG alpha channel.
[12:28:23 CDT(-0500)] <mlam> cindyli: yes, that's right
[12:28:32 CDT(-0500)] <heidi> jhung right, and we're not fixing that right?
[12:28:44 CDT(-0500)] <jhung> heidi: yeah.
[12:28:55 CDT(-0500)] <mlam> cindyli: do you see any way around this?
[12:29:02 CDT(-0500)] <heidi> jhung so if we figure out the floating in ie7, that hsould help ie 6 too
[12:29:04 CDT(-0500)] <cindyli> mlam: thinking
[12:29:17 CDT(-0500)] <jhung> heidi: yeah, I hope so.
[12:29:47 CDT(-0500)] <jhung> heidi: I can help take a look once I push out some changes to anastasiac's pull request.
[12:29:54 CDT(-0500)] <heidi> jhung awesome, thanks
[12:31:02 CDT(-0500)] <cindyli> mlam: what if we open up the "detection of the original sizes + setting the computed size" into a public named function, you explicitly call this function at panel open.
[12:31:49 CDT(-0500)] <mlam> I think the panel has to be fully opened before the original size can even be calculated
[12:33:43 CDT(-0500)] <cindyli> mlam: ic
[12:36:10 CDT(-0500)] <cindyli> mlam: no, panel may not need to be fully opened. the size detection is on uiEnhancer.container, which is <body>. Once the <body> is in place, the sizes are detectable.
[12:39:26 CDT(-0500)] <cindyli> mlam: we can do a simple test. i think in michelled's refactorred ui enhancer, she has already opened up the functions of size detection on font and line spacing. u can try calling one of these functions at panel open to see if the size can be fetched.
[12:40:35 CDT(-0500)] <mlam> cindyli: I'll give it a shot.
[12:40:50 CDT(-0500)] <cindyli> ok. thanks, mlam
[13:12:27 CDT(-0500)] <jhung> anastasiac: I just pushed out some changes for FLUID-4287.
[13:13:15 CDT(-0500)] <anastasiac> jhung, your changes are now part of the pull request, so we're good to fo
[13:13:17 CDT(-0500)] <anastasiac> go
[13:13:44 CDT(-0500)] <jhung> excellent anastasiac. I'll loook at pull request #82 now
[13:13:54 CDT(-0500)] <jhung> #81 rather
[13:14:17 CDT(-0500)] <anastasiac> thanks
[13:44:10 CDT(-0500)] <colinclark> Looks like a reasonable Git client is emerging for the Mac: http://mac.github.com/
[13:44:31 CDT(-0500)] <michelled_> fluid-everyone: who wants to be skyped into the dev meeting?
[13:44:48 CDT(-0500)] <michelled_> fluid-everyone: if you come in person there's lunch today!
[13:44:56 CDT(-0500)] <huslage> making me sad
[13:45:09 CDT(-0500)] <heidi> michelled_ me please
[13:46:01 CDT(-0500)] <michelled_> heidi: you online?
[13:46:18 CDT(-0500)] <heidi> michelled_ yep but i do't see you
[13:47:21 CDT(-0500)] <michelled_> cindyli: you joining us?
[13:49:38 CDT(-0500)] <cindyli> sure, michelled_
[13:49:54 CDT(-0500)] <michelled_> are you on skype?
[13:50:09 CDT(-0500)] <cindyli> logging in
[13:51:02 CDT(-0500)] <cindyli> michelled_: now i'm on
[14:44:55 CDT(-0500)] <colinclark> Justin_o: Just as we were debating which version of Firefox to support for this Infusion release, @shaver wrote this tweet:
[14:44:58 CDT(-0500)] <colinclark> "We just released the second security update to Firefox 4; it's called Firefox 5."
[14:48:57 CDT(-0500)] <huslage> lol
[14:59:38 CDT(-0500)] <michelled_> kasper: colinclark's comment above might be interesting to you
[15:01:08 CDT(-0500)] <jessm> anyone know where colin is?
[15:01:31 CDT(-0500)] <jessm> Justin_o: ^
[15:02:53 CDT(-0500)] <jessm> michelled_: ^
[15:03:59 CDT(-0500)] <michelled_> he's meeting with us (smile)
[15:04:11 CDT(-0500)] <jessm> doh – say one word to him --> buckets
[15:13:00 CDT(-0500)] <jessm> michelled_: any reply?
[15:25:43 CDT(-0500)] <kasper> michelled_: thanks! (though I think it's too late for us to change) - seeing the minimal difference in behavior (bug wise) between 3.6 and 4, collectionspace will hopefully be running well under FF5 too though
[15:26:06 CDT(-0500)] <michelled_> that's my guess kasper
[19:50:25 CDT(-0500)] <huslage> https://github.com/blog/878-announcing-github-for-mac