fluid-work IRC Logs-2011-08-11

[07:24:28 CDT(-0500)] <huslage> morning
[08:11:15 CDT(-0500)] <heidi__> hey Justin_o is the builder working? i'm getting "Cannot process input variables"
[08:12:27 CDT(-0500)] <heidi__> tho i see a "Cats!" reference so maybe Bosmon is working on it? (smile)
[08:15:47 CDT(-0500)] <Justin_o> heidi__: sounds like it's broken
[08:15:59 CDT(-0500)] <Justin_o> are you using builder.fluidproject.org
[08:16:02 CDT(-0500)] <Justin_o> or the nightly build
[08:16:13 CDT(-0500)] <heidi__> Justin_o http://build.fluidproject.org/infusionBuilder/html/InfusionBuilder.html
[08:16:36 CDT(-0500)] <Justin_o> heidi__: okay.. currently the nightly/hourly builds are all broken
[08:16:37 CDT(-0500)] <heidi__> i followed the link from http://build.fluidproject.org/
[08:16:46 CDT(-0500)] <Justin_o> for infusion stuff
[08:17:12 CDT(-0500)] <Justin_o> heidi__: colin is looking into it.. i think it's a pathing error in the build scripts
[08:17:31 CDT(-0500)] <heidi__> okay, so i should use http://builder.fluidproject.org/
[08:17:32 CDT(-0500)] <heidi__> ?
[08:17:39 CDT(-0500)] <heidi__> or maybe i'll just wait
[08:18:51 CDT(-0500)] <Justin_o> heidi__: what did you want it for?
[08:19:07 CDT(-0500)] <heidi__> Justin_o newest UIO for my wordpress
[08:20:55 CDT(-0500)] <Justin_o> heidi__: okay
[08:21:05 CDT(-0500)] <Justin_o> if you have a checkout, you can run it from the command line
[08:22:08 CDT(-0500)] <heidi__> Justin_o cool, i do. i just want UIO tho, not everything
[08:22:33 CDT(-0500)] <heidi__> perhaps there's a doc page for doing this
[08:22:36 CDT(-0500)] <Justin_o> heidi__: yep... you can do that to
[08:22:38 CDT(-0500)] <Justin_o> there is..
[08:22:41 CDT(-0500)] <Justin_o> let me find it for you
[08:23:04 CDT(-0500)] <Justin_o> heidi__: http://wiki.fluidproject.org/display/fluid/Custom+Infusion+Builds+With+Ant
[08:23:15 CDT(-0500)] <Justin_o> let me know if you need any help with that
[08:23:22 CDT(-0500)] <heidi__> cheers Justin_o
[08:33:05 CDT(-0500)] <heidi__> Justin_o i think my version of ant won't do it.
[08:33:34 CDT(-0500)] <heidi__> for generating the UIO themes
[08:48:49 CDT(-0500)] <Justin_o> heidi__: you can use the one that ships with it
[08:48:57 CDT(-0500)] <Justin_o> with infusion
[08:49:11 CDT(-0500)] <Justin_o> you just do something like ant -lib lib/rhino
[08:49:25 CDT(-0500)] <Justin_o> the exact command is in the readme in the build scripts directory
[08:59:12 CDT(-0500)] <heidi__> ah, ok
[09:04:50 CDT(-0500)] <colinclark> heidi__: You'll probably have to follow the instructions for getting the build scripts working
[09:04:54 CDT(-0500)] <colinclark> It's quite straightforward
[09:05:03 CDT(-0500)] <colinclark> In short, Apple ships a minimal version of Ant with Mac OS X
[09:05:08 CDT(-0500)] <colinclark> so you'll need to go download the full version
[09:05:12 CDT(-0500)] <colinclark> swap the default version with it
[09:05:18 CDT(-0500)] <colinclark> and then fetch a few extra things
[09:05:26 CDT(-0500)] <colinclark> then just follow the instructions
[09:05:33 CDT(-0500)] <colinclark> I recommend making a custom development build
[09:05:39 CDT(-0500)] <heidi__> i've updated my rhino with the version in the build... with the commands stated in the doc under "rhino" but still no luck... i'll have to read through all of this maybe
[09:05:39 CDT(-0500)] <colinclark> I can send you the command line arguments I used for FSSFive
[09:05:48 CDT(-0500)] <colinclark> heidi__: Yeah, Justin_o was wrong (tongue)
[09:05:51 CDT(-0500)] <colinclark> You need to upgrade Ant first
[09:05:53 CDT(-0500)] <colinclark> I mean, he was right
[09:05:55 CDT(-0500)] <colinclark> but it's not enough
[09:05:56 CDT(-0500)] <colinclark> (smile)
[09:06:06 CDT(-0500)] <colinclark> Follow the steps in the README or on the wiki
[09:06:07 CDT(-0500)] <colinclark> it's not hard
[09:06:15 CDT(-0500)] <colinclark> no rocket science or brain surgery required
[09:06:48 CDT(-0500)] <heidi__> k i'll get the full ant, thanks colinclark
[09:06:53 CDT(-0500)] <colinclark> np
[09:07:04 CDT(-0500)] <colinclark> I'll get the daily builder up and running, so we don't have to deal with stupid command lines
[09:07:11 CDT(-0500)] <colinclark> let me dig up the arguments I used for FSSFive, heidi__
[09:07:15 CDT(-0500)] <colinclark> should save you a bit of time
[09:07:31 CDT(-0500)] <heidi__> cool thanks
[09:07:35 CDT(-0500)] <heidi__> i used ant -lib lib/rhino customBuild -Dinclude="uiOptions, tableOfContents" -Djsfilename="InfusionUIO.js"
[09:08:23 CDT(-0500)] <colinclark> heidi__: That's pretty close
[09:08:29 CDT(-0500)] <colinclark> You don't need to specify tableOfContents
[09:08:35 CDT(-0500)] <colinclark> since it's a dependency of UIO
[09:08:40 CDT(-0500)] <heidi__> k
[09:08:54 CDT(-0500)] <colinclark> And if you want it unminified (for debugging), you'll need to also include -DnoMinify="true"
[09:09:01 CDT(-0500)] <colinclark> I built two separate versions, which I swapped between
[09:09:08 CDT(-0500)] <colinclark> a minified version for once everything was working great
[09:09:15 CDT(-0500)] <colinclark> since it's an awful lot faster to use minified scripts
[09:09:18 CDT(-0500)] <colinclark> but horrifying to debug
[09:09:32 CDT(-0500)] <heidi__> yeah and speed definitely a factor w UIO
[09:09:51 CDT(-0500)] <colinclark> we're on it
[09:10:19 CDT(-0500)] <colinclark> My working theory is that most of the sense of slowness is due to the thing unrolling itself and then rolling back up
[09:10:34 CDT(-0500)] <colinclark> most things should happen asynchronously in the iFrame without the user even really being aware of it
[09:10:44 CDT(-0500)] <colinclark> Justin_o: What did you think of Bosmon's post to the list about that issue?
[09:11:06 CDT(-0500)] <Justin_o> colinclark: i'm just writing up a reply as we speak
[09:11:08 CDT(-0500)] <Justin_o> (smile)
[09:11:08 CDT(-0500)] <colinclark> and, on an unrelated subject, do you have someone lined up to review and push your FLUID-4377 request, Justin_o?
[09:11:11 CDT(-0500)] <colinclark> cool
[09:11:30 CDT(-0500)] <Justin_o> colinclark: i asked michelle yesterday, but she may be too busy with parser stuff at the moment
[09:11:45 CDT(-0500)] <colinclark> yeah, she's right in the thick of it
[09:11:50 CDT(-0500)] <colinclark> I can try to take a look today
[09:11:55 CDT(-0500)] <colinclark> i'm stacking up a few reviews to do
[09:11:59 CDT(-0500)] <michelled> thanks colinclark
[09:13:52 CDT(-0500)] <heidi__> how's the intensive going ?
[09:14:13 CDT(-0500)] <michelled> great - Clayton is talking now
[09:14:25 CDT(-0500)] <heidi__> oh cool
[09:16:54 CDT(-0500)] <colinclark> yesterday was a lot of fun
[09:17:21 CDT(-0500)] <colinclark> jameswy had a really great format for our course taster about the User Experience Lab they'll be doing here in the Fluid community
[09:17:45 CDT(-0500)] <colinclark> it provided lots of opportunity for conversation amongst the students
[09:20:28 CDT(-0500)] <heidi__> colinclark bet it was cool. is there a blog for the intensive i can check out?
[09:21:37 CDT(-0500)] <colinclark> I'll have to check with Aileen, I know she's got a wiki page or something for the students
[09:21:53 CDT(-0500)] <colinclark> unfortunately the sessions haven't been recorded yet, but Bert is hoping to start videoing them
[09:22:26 CDT(-0500)] <heidi__> be cool to follow along if possible
[09:26:48 CDT(-0500)] <heidi__> btw, installing full ant did the trick
[10:58:39 CDT(-0500)] <heidi__> jameswy i'm up for a brainstorm sesh if that would help
[11:00:54 CDT(-0500)] <jameswy> heidi__: Awesomes. How about 1:30ish?
[11:01:00 CDT(-0500)] <heidi__> sounds good
[11:01:20 CDT(-0500)] <jameswy> anastasiac, michelled, Justin_o, jhung, and anyone else interested in some Floe ideastorming?
[11:01:37 CDT(-0500)] <jameswy> (timeboxed to about a half-hour)
[11:01:46 CDT(-0500)] <michelled> sounds good
[11:09:17 CDT(-0500)] <jhung> Jameswy: sure
[11:09:31 CDT(-0500)] <jhung> btw jameswy: here's the arc mouse design http://www.behance.net/gallery/Microsoft-Arc-Touch-Mouse/1770408
[12:17:08 CDT(-0500)] <Justin_o> fluid-everyone: some i'm working on FLUID-4370
[12:17:35 CDT(-0500)] <Justin_o> basically some of the text keeps the default colour instead of the theme colour, which makes for poor contrast when there is a dark background.
[12:17:47 CDT(-0500)] <colinclark> ok
[12:17:58 CDT(-0500)] <Justin_o> So the issue here is one of specificity
[12:18:16 CDT(-0500)] <Justin_o> if you test out the full with preview example, you can see that the text is all correct in the preview
[12:18:20 CDT(-0500)] <Justin_o> but not in uio itself
[12:18:40 CDT(-0500)] <jhung> hey colinclark. You have time t chat Decapod today?
[12:18:43 CDT(-0500)] <Justin_o> this is because the text in the preview is able to inherit the style set by the body
[12:18:50 CDT(-0500)] <colinclark> jhung: yep
[12:20:01 CDT(-0500)] <Justin_o> but in uio we set the colour for some of the text directly in the default theme, which has a higher specificity .. so even though !important was used, because inheritance has no specificity it loses out.
[12:20:35 CDT(-0500)] <jhung> Colinclark, we can do face 2 face or in the channel. Whatever works for you.
[12:20:45 CDT(-0500)] <colinclark> I'm easy. What's the topic?
[12:21:24 CDT(-0500)] <jhung> colinclark: just going over the observations I made on genpdf and see if there's any functionality missing we need to implement / request.
[12:21:30 CDT(-0500)] <colinclark> ok
[12:21:45 CDT(-0500)] <colinclark> i've got a meeting at 1:30 pm and another at 2 pm
[12:21:50 CDT(-0500)] <colinclark> how does 3 pm sound?
[12:21:56 CDT(-0500)] <colinclark> are you here long today?
[12:22:02 CDT(-0500)] <Justin_o> fluid-everyone: so we could make use of the universal selector "*" and set everything to have the specified colour. This would override any inheritance though, so for things that need to override the colour, we would have to specify each case
[12:22:08 CDT(-0500)] <jhung> Leaving 4:30p colinclark.
[12:22:13 CDT(-0500)] <colinclark> ok
[12:22:16 CDT(-0500)] <colinclark> let's do 3 pm
[12:22:23 CDT(-0500)] <jhung> sounds good.
[12:22:24 CDT(-0500)] <Justin_o> The only issue i'm having with that so far is with the select boxes
[12:26:25 CDT(-0500)] <colinclark> Justin_o: I can't quite tell if you have a proposal here, and if so, what its strengths and weaknesses are
[12:26:34 CDT(-0500)] <colinclark> I mean, I think you do
[12:26:38 CDT(-0500)] <colinclark> I'm just still not quite clear on it
[12:26:45 CDT(-0500)] <Justin_o> colinclark: neither am i (smile)
[12:26:50 CDT(-0500)] <colinclark> lol
[12:26:51 CDT(-0500)] <Justin_o> let me try to rephrase
[12:26:52 CDT(-0500)] <Justin_o> a bit
[12:27:31 CDT(-0500)] <Justin_o> So i guess what i'm proposing is that we use the universal selector "*"
[12:27:59 CDT(-0500)]

<Justin_o> which would look something like .fl-theme-yellowBlack *

Unknown macro: { color}

[12:28:19 CDT(-0500)] <Justin_o> the issue with this is that it will destroy any inherited overrides
[12:28:25 CDT(-0500)] <Justin_o> for color
[12:28:31 CDT(-0500)] <Justin_o> so we would just have to be specific
[12:29:26 CDT(-0500)] <Justin_o> the only issue i'm currently seeing is that wit the "colour & contrast" drop down, it is overriding the themed options
[12:29:40 CDT(-0500)] <Justin_o> so you end of with all the text being yellow even if the background is yellow
[12:31:18 CDT(-0500)] <heidi__> Justin_o is the current UIO in trunk demonstrating the issue somehow? feel like i need to see what's currently happening
[12:31:32 CDT(-0500)] <Justin_o> heidi__: yes
[12:31:33 CDT(-0500)] <Justin_o> it is
[12:32:01 CDT(-0500)] <Justin_o> heidi__: just make sure that you are using the generated stylesheets
[12:32:15 CDT(-0500)] <Justin_o> you do this by running a build "ant generateUIOThemes"
[12:33:39 CDT(-0500)] <heidi__> Justin_o k got it. and the fat panel demo shows the prob or?
[12:33:57 CDT(-0500)] <Justin_o> heidi__: probably easier to look at the full with preview demo
[12:34:05 CDT(-0500)] <heidi__> ill look at the jira for 4370
[12:34:06 CDT(-0500)] <heidi__> ah ok
[12:36:17 CDT(-0500)] <heidi__> Justin_o it's 4370?
[12:37:05 CDT(-0500)] <heidi__> jameswy still 1.30 chat?
[12:37:35 CDT(-0500)] <jhung> heidi__: jameswy is at lunch still
[12:37:48 CDT(-0500)] <heidi__> thanks jhung
[12:37:52 CDT(-0500)] <jhung> np
[12:38:37 CDT(-0500)] <heidi__> Justin_o so it's that the description "Adds a table of contents to the top of the page" is grey text?
[12:38:50 CDT(-0500)] <heidi__> the icons are fine for me
[12:40:27 CDT(-0500)] <Justin_o> heidi__: yes
[12:40:37 CDT(-0500)] <Justin_o> the icons i think were fixed with something else
[12:40:43 CDT(-0500)] <Justin_o> but the text is still an issue
[12:40:45 CDT(-0500)] <heidi__> and the header text is fine too
[12:41:25 CDT(-0500)] <heidi__> Justin_o did you add paragraphs to the themes
[12:42:01 CDT(-0500)] <Justin_o> heidi__: no.. i haven't but there are only certain elements which specifically get the color property set
[12:42:13 CDT(-0500)] <Justin_o> which is why this issue has arisen
[12:42:33 CDT(-0500)] <Justin_o> sort of why i'm suggesting we use "*" otherwise we'd have to set it on all elements directly
[12:42:41 CDT(-0500)] <Justin_o> in order to win out
[12:43:33 CDT(-0500)] <heidi__> Justin_o and to over-ride the *, specificity would work?
[12:44:07 CDT(-0500)] <heidi__> how would i keep these paragraphs grey if that's what i wanted... a theme-specific style?
[12:44:30 CDT(-0500)] <Justin_o> heidi__: yes, basically * has a higher specificity.. inheritance has no specificity
[12:44:40 CDT(-0500)] <Justin_o> yes.. you'd need a theme specific style
[12:44:46 CDT(-0500)] <Justin_o> right now they are inheriting from the default theme
[12:44:56 CDT(-0500)] <Justin_o> sorry.. retaining the style set by the default theme
[12:45:00 CDT(-0500)] <heidi__> right
[12:45:29 CDT(-0500)] <heidi__> Justin_o what other things besides paragraphs is it not styling?
[12:46:57 CDT(-0500)] <Justin_o> nothing yet, but that doesn't mean there won't be more for an integrator (smile)
[12:47:02 CDT(-0500)] <heidi__> Justin_o adding .fl-theme-uio-hci p in addition to div and input seems reasonable
[12:47:22 CDT(-0500)] <Justin_o> so anything that we are currently relying on inheritence for, could be beaten out
[12:49:41 CDT(-0500)] <heidi__> Justin_o so what would be in the * { } style
[13:36:28 CDT(-0500)] <Justin_o> heidi__: want to pick up our FSS conversation
[13:41:43 CDT(-0500)] <heidi__> Justin_o yeah
[13:43:49 CDT(-0500)] <Justin_o> heidi__: so the universal selector declaration would looks something like the follwoing
[13:44:09 CDT(-0500)]

<Justin_o> fl-theme-themeName *

Unknown macro: { color}

;


[13:44:20 CDT(-0500)] <Justin_o> we may also want to add the border and background colour too
[13:44:20 CDT(-0500)] <heidi__> so just txt color - what about bg?
[13:44:34 CDT(-0500)] <Justin_o> yes.. so we might want to do all of the colours, yes
[13:45:00 CDT(-0500)] <heidi__> Justin_o have you tried it out?
[13:45:17 CDT(-0500)] <Justin_o> heidi__: i tried with just colour, the only issue was in the select box
[13:45:34 CDT(-0500)] <heidi__> what happened?
[13:45:49 CDT(-0500)] <Justin_o> the "colour & contrast" options would have the current themes style, but the options background
[13:45:58 CDT(-0500)] <Justin_o> so you might have yellow text on a yellow background
[13:46:13 CDT(-0500)] <Justin_o> i think that's because they had the same specificity..
[13:48:45 CDT(-0500)] <heidi__> Justin_o adding bg color to the * style would fix it right
[13:49:28 CDT(-0500)] <Justin_o> heidi__: well.. sort of.. i just tried it out.. so it's basically the same problem
[13:49:40 CDT(-0500)] <Justin_o> since they have the same specificity which ever theme was added last wins
[13:49:56 CDT(-0500)] <Justin_o> so in some cases they are all the same as the current contrast theme.. sometimes they display like you'd want
[13:51:21 CDT(-0500)] <heidi__> hm, i'm confused
[13:52:17 CDT(-0500)] <Justin_o> heidi__: okay.. so for the options in the "colour & contrast" select box, they individually have the specific theme class added to them
[13:52:24 CDT(-0500)] <heidi__> gonna try it on my end. which theme did you add it to, all? the *
[13:52:30 CDT(-0500)] <Justin_o> so blackYellow will have fl-theme-blackYellow on the option element
[13:52:41 CDT(-0500)] <heidi__> k
[13:52:42 CDT(-0500)] <Justin_o> heidi__: yep.. i changed all of theme
[13:53:18 CDT(-0500)] <Justin_o> so i did something like .fl-theme-hci, .fl-theme-hci *
[13:53:26 CDT(-0500)] <Justin_o> now i'm trying to add the border-color to that too
[13:53:45 CDT(-0500)] <heidi__> Justin_o i think the theme affecting all of the drop down options is fine
[13:53:53 CDT(-0500)] <heidi__> in fact, i think it makes sense, right?
[13:54:16 CDT(-0500)] <Justin_o> heidi__: well which theme are you referring too?
[13:54:29 CDT(-0500)] <heidi__> whichever theme is selected by the user
[13:55:30 CDT(-0500)] <Justin_o> heidi__: that would be fine, but we'd have to remove the logic from uio that tries to assign the individual theme classes to each option
[13:56:06 CDT(-0500)] <Justin_o> heidi__: i'm okay with that for now, but we'd have to talk to james.. the select boxes aren't what he wants anyways, so i think it would be okay for now..
[13:56:16 CDT(-0500)] <heidi__> yeah they will change
[13:56:17 CDT(-0500)] <Justin_o> they will have to be properly done for 1.5 for sure though
[14:03:47 CDT(-0500)] <Bosmon> Hi Justin_o - you are still there (smile)
[14:04:17 CDT(-0500)] <Bosmon> I still can't really understand the situation from your description...
[14:04:23 CDT(-0500)] <Bosmon> since I don't understand what is meant by "it will have to calculate sizes when the content is hidden."
[14:04:26 CDT(-0500)] <Bosmon> Can you be more specific?
[14:04:51 CDT(-0500)] <Justin_o> Bosmon: Hello
[14:05:31 CDT(-0500)] <Justin_o> Bosmon: So UIO changes the font size and line spacing by first calculating what the default font size and line spacing are in pixels
[14:05:38 CDT(-0500)] <Justin_o> Bosmon: this is done by checking the computed style
[14:06:03 CDT(-0500)] <Bosmon> Can you be more specific? (smile)
[14:06:22 CDT(-0500)] <Justin_o> Bosmon: what we were experiencing in Firefox, it had display none specified... there were no values for the font size and line spacing
[14:07:45 CDT(-0500)] <Justin_o> so for example <body style="display:none;">Some content</body>, if we tried to get the computed styles for the font size and linespacing they would come back as NaN i believe
[14:08:26 CDT(-0500)] <Bosmon> Well, perhaps hiding the entire body is a step too far
[14:08:39 CDT(-0500)] <Bosmon> In my mail I put the display none onto just the sliding panel div
[14:08:43 CDT(-0500)] <Bosmon> And I don't seem to see any problems
[14:09:02 CDT(-0500)] <Bosmon> Also you want the "thumb tab" to be visible anyway
[14:09:17 CDT(-0500)] <Bosmon> The "Show/Hide" button
[14:09:30 CDT(-0500)] <Justin_o> Bosmon: that was just an example.. the display none was on the sliding panel
[14:09:32 CDT(-0500)] <Bosmon> Which body do you mean, anyhow?
[14:09:33 CDT(-0500)] <Bosmon> ok
[14:09:38 CDT(-0500)] <Justin_o> it puts it on itself when it closes
[14:09:42 CDT(-0500)] <Bosmon> Yes
[14:10:01 CDT(-0500)] <Justin_o> basically the entire iframe becomes invisible since it is inside of the panel
[14:10:12 CDT(-0500)] <Bosmon> Right
[14:10:39 CDT(-0500)] <Justin_o> so anyways.. it seems that from your tests and cindyli's changes, that for whatever reason this is no longer an issue
[14:10:53 CDT(-0500)] <Justin_o> so i think we could solve it just by instantiating the sliding panel first
[14:11:13 CDT(-0500)] <Justin_o> since it will close it's self by default
[14:11:46 CDT(-0500)] <Bosmon> I'm not sure it will close itself quickly enough
[14:12:21 CDT(-0500)] <Bosmon> The best way to be sure that flickering is completely absent would seem to be to alter the base markup
[14:12:57 CDT(-0500)] <Justin_o> Bosmon: we don't have total control over that markup though... it is just a demo after all
[14:13:19 CDT(-0500)] <Bosmon> We have control enough that we can instruct our users to make it hidden if they want flickering to be absent (tongue)
[14:13:45 CDT(-0500)] <Justin_o> Bosmon: also the sliding panel has the option to start open.. so that might be broken if you put display: none in the markup.. although it might be smart enough to call show on itself
[14:14:09 CDT(-0500)] <Bosmon> It doesn't look like it is smart enough to do that
[14:14:31 CDT(-0500)] <Bosmon> But I'll certainly experiement with creating it first - right now it is created on template load
[14:14:46 CDT(-0500)] <Bosmon> But I don't seem to see any dependency in its code on the contents
[14:14:53 CDT(-0500)] <Bosmon> So, I guess that sort of settles one issue
[14:15:03 CDT(-0500)] <Bosmon> So the next issue is the calculation of the iframe's height itself
[14:15:09 CDT(-0500)] <Justin_o> Bosmon: yep
[14:15:57 CDT(-0500)] <Justin_o> so if calculations are working when the iframe is closed, then we should be able to get it's window or document height.. although we'd have to look into the other world to find that out i'd guess
[14:16:20 CDT(-0500)] <Bosmon> Well, I think that's a different issue
[14:16:41 CDT(-0500)] <Bosmon> Just because we can get static CSS measurements doesn't mean we will get sensible values for the document height
[14:16:50 CDT(-0500)] <Justin_o> Bosmon: very true
[14:16:57 CDT(-0500)] <Justin_o> since it may not know how to lay itself out
[14:17:03 CDT(-0500)] <Bosmon> As I suggested in my mail, I think the only sound way to do this is to add "frequent calculations" whenever there is any significant DOM manipulation
[14:17:08 CDT(-0500)] <Bosmon> Since these may change the height in any case
[14:17:30 CDT(-0500)] <Bosmon> I ran into a problem, for example, on the content simplification demo, where the 4th panel I added was significantly higher then the other 3
[14:17:51 CDT(-0500)] <Bosmon> Luckily, I am a past master in dynamic iframe height calculations, as a result of my "boot camp" experiences in Sakai (tongue)
[14:18:06 CDT(-0500)] <Bosmon> Where ALL of the significant content was displayed in iframes all the time...
[14:18:26 CDT(-0500)] <Justin_o> Bosmon: glad you're working on it then (smile)
[14:18:43 CDT(-0500)] <Bosmon> So just to be clear - when you say, "the values came back as Nan"
[14:18:59 CDT(-0500)] <Bosmon> You're referring to the values which were found by the UIEnhancer instance which is on the INSIDE of the iframe?
[14:19:42 CDT(-0500)] <Justin_o> Bosmon: yes.. i can't quite remember if the computed style itself was NaN or if some internal calculation that was dependent on the computed style would result in NaN
[14:19:44 CDT(-0500)] <Bosmon> Yes, actually I can see these coming back as NaN now (smile)
[14:19:50 CDT(-0500)] <Bosmon> But the question is - why does it matter?
[14:19:59 CDT(-0500)] <Justin_o> I think we have to ask mozilla (smile)
[14:20:06 CDT(-0500)] <Justin_o> since it was working on other browsers
[14:20:20 CDT(-0500)] <Justin_o> but it makes sense in a way that it would have no height when it has display none
[14:20:34 CDT(-0500)] <Bosmon> Yes - but do we really care what the "inner enhancer" thinks, when it is not visible?
[14:20:50 CDT(-0500)] <Bosmon> It sorts itself out fine as soon as you show it, as far as I can see
[14:20:56 CDT(-0500)] <Justin_o> Bosmon: we could do it when it is visible, but then there would be flicker
[14:21:24 CDT(-0500)] <Justin_o> Bosmon: mike and I had got it to work all the time except on page load
[14:21:54 CDT(-0500)] <Bosmon> Perhaps we shouod Skype about this (tongue)
[14:21:56 CDT(-0500)] <Justin_o> so the first time you open the panel, if there were changes to the font size or line height, you would see it at the default then it would change to the set value
[14:21:57 CDT(-0500)] <Bosmon> Do you have a little time?
[14:22:00 CDT(-0500)] <Justin_o> sire
[14:22:02 CDT(-0500)] <Justin_o> sure
[14:22:15 CDT(-0500)] <Bosmon> Ok, just give me 5 mins and I will be right back...
[14:23:26 CDT(-0500)] <Justin_o> okay.. call me when you're ready
[14:25:11 CDT(-0500)] <Bosmon> ok
[14:35:19 CDT(-0500)] <Bosmon> Justin_o - testing on IE8 is worrying
[14:35:24 CDT(-0500)] <Bosmon> Produces this error: LOG: Thu Aug 11 13:33:48 MDT 2011: ASSERTION FAILED: Error instantiating component with name "fluid.uiOptions.textControls: selector ".contents() body .flc-uiOptions-text-controls" with name textControls returned no results in context [object HTMLIFrameElement]
[14:59:26 CDT(-0500)] <lahabana> heidi__: just seen your email
[14:59:41 CDT(-0500)] <heidi__> lahabana hey charly!
[15:00:16 CDT(-0500)] <lahabana> For firefox it's actually working but the event that enables the button doesn't seem to exist
[15:00:28 CDT(-0500)] <lahabana> if you click on the video it works
[15:00:55 CDT(-0500)] <lahabana> it's not only fullscreen version it's just that video I found is really really small
[15:01:37 CDT(-0500)] <lahabana> after for all the buttons layout I used the default jQuery UI styles
[15:02:11 CDT(-0500)] <heidi__> the player should probably still work well with videos of this size, don't you think?
[15:02:24 CDT(-0500)] <lahabana> yes
[15:02:36 CDT(-0500)] <lahabana> I said in my email that I was looking for ideas
[15:03:18 CDT(-0500)] <lahabana> thx for the auto rewinding etc I didn't thought about it and it's a really good idea
[15:04:23 CDT(-0500)] <heidi__> cool. do you have a strategy for getting things for firefox fixed?
[15:04:51 CDT(-0500)] <lahabana> yes I just didn't see it
[15:05:02 CDT(-0500)] <lahabana> there's 2 kind of events that I could use
[15:05:15 CDT(-0500)] <lahabana> canPlay and onmetadataloaded
[15:05:20 CDT(-0500)] <lahabana> or something of the kind
[15:05:31 CDT(-0500)] <lahabana> I think firefox doesn't have the canplay...
[15:06:11 CDT(-0500)] <heidi__> k
[15:06:35 CDT(-0500)] <heidi__> i wonder if moving the buttons below the progress bar would give you more room and flexibility for smaller videos
[15:06:46 CDT(-0500)] <heidi__> just looking again at http://wac.osu.edu/examples/jwpc/
[15:07:01 CDT(-0500)] <heidi__> also all that stuff should be below the video instead of over top
[15:07:37 CDT(-0500)] <lahabana> yes
[15:07:42 CDT(-0500)] <jhung> colinclark: http://wiki.fluidproject.org/display/fluid/Post+Decapod+0.4+examination+and+notes
[15:08:07 CDT(-0500)] <lahabana> I was hesitating in between making it disapear or put it underneath
[15:08:27 CDT(-0500)] <heidi__> lahabana cool. aesthetic stuff. it's good to see the "bones" of the player working well.
[15:09:12 CDT(-0500)] <lahabana> then for the fullscreen
[15:09:13 CDT(-0500)] <heidi__> and i was able to tab to/activate the buttons via keyboard which is great
[15:09:28 CDT(-0500)] <lahabana> yes and shortcuts work too
[15:09:35 CDT(-0500)] <lahabana> I didn't give them though (wink)
[15:09:43 CDT(-0500)] <lahabana> so for the fullscreen
[15:10:22 CDT(-0500)] <lahabana> The thing is that there's no "real" fullscreen currently (except safari)
[15:10:48 CDT(-0500)] <lahabana> so I just extend it to the whole screen
[15:12:13 CDT(-0500)] <lahabana> what I should do is put a background behind the video
[15:12:20 CDT(-0500)] <heidi__> lahabana ah, i see. we'll have to figure out a way to do that without overlapping other elements on the page
[15:12:22 CDT(-0500)] <lahabana> so you don't see it's over the rest
[15:12:34 CDT(-0500)] <lahabana> well it's fullscreen
[15:12:39 CDT(-0500)] <lahabana> so it's supposed too
[15:12:53 CDT(-0500)] <lahabana> no?
[15:13:51 CDT(-0500)] <heidi__> i think it could be 100% height but not overlap. the header would still be visible by scrolling up or something
[15:14:00 CDT(-0500)] <heidi__> not sure
[15:14:47 CDT(-0500)] <lahabana> that would be an odd fullscreen no?
[15:16:04 CDT(-0500)] <heidi__> lahabana since it's not true fullscreen anyway, i think we have some room to do whatever works best in this situation
[15:16:15 CDT(-0500)] <lahabana> ok
[15:18:23 CDT(-0500)] <lahabana> heidi__: last thing for the times it just looked like more coherent with the rest of the style
[15:18:47 CDT(-0500)] <lahabana> also you said there was no title on buttons there are...
[15:18:52 CDT(-0500)] <lahabana> no?
[15:18:56 CDT(-0500)] <heidi__> yep i noticed there were later, so ignore that bit
[15:19:11 CDT(-0500)] <heidi__> i think only buttons should look like buttons!
[15:19:53 CDT(-0500)] <lahabana> ok
[15:19:55 CDT(-0500)] <heidi__> but if you have a good reason for it, then it's your call.
[15:20:12 CDT(-0500)] <lahabana> ok
[15:53:16 CDT(-0500)] <heidi__> anastasiac are all of the fonts supposed to change when i choose a text style?
[15:53:58 CDT(-0500)] <anastasiac> heidi_, yes, and it seems that this page is revealing a bug in UIOptions :)
[15:54:03 CDT(-0500)] <heidi__> i get a weird scrollbar when i choose comic. it might be a fl-fix issue
[15:54:45 CDT(-0500)] <heidi__> fl-clearfix should do it
[15:54:53 CDT(-0500)] <heidi__> anyway, i'll play and make a list
[16:07:33 CDT(-0500)] <heidi__> anastasiac is james's UIO demo mockup somewhere on the wiki
[16:08:05 CDT(-0500)] <anastasiac> it's attached to the JIRA itself, heidi__
[16:08:16 CDT(-0500)] <heidi__> wewps, thanks