fluid-work IRC Logs-2011-03-16

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

[09:55:25 CDT(-0500)] <jhung> I have an inline edit question. The default behaviour of Inline Edit is the "Simple" inline edit?
[09:56:31 CDT(-0500)] <jhung> The reason I ask is because I'm looking at both the Inline Edit API docs and the Simple Inline Edit docs and don't see any real obvious differences. Am I missing something?
[09:56:54 CDT(-0500)] <anastasiac> jhung, default is simple
[09:57:03 CDT(-0500)] * anastasiac looks at the docs
[09:58:01 CDT(-0500)] <anastasiac> jhung, agreed, they are pretty redundant
[09:58:23 CDT(-0500)] <anastasiac> we'll need to clean that up!
[09:58:29 CDT(-0500)] <anastasiac> probably deprecate one of the pages
[09:58:57 CDT(-0500)] <jhung> yeah. The only thing I see that's different is the use of multiple inline edits.
[10:04:37 CDT(-0500)] <mlam> colinclark: I was able to reproduce what you were experiencing with IE8/XP. the Uploader.html just doesn't load properly. I'm getting a message with an error in Fluid.js
[10:04:49 CDT(-0500)] <colinclark> eek
[10:04:56 CDT(-0500)] <colinclark> what is it?
[10:05:49 CDT(-0500)] <mlam> it's not giving me much. The line is pointing to a line in fluid.fail
[10:06:12 CDT(-0500)] <colinclark> Stick a breakpoint in on that line, and then have a look at the stack trace
[10:07:57 CDT(-0500)] <mlam> colinclark: Error invoking global function: fluid.uploader.progressiveStrategy could not be located
[10:08:24 CDT(-0500)] <colinclark> Interesting
[10:08:43 CDT(-0500)] <colinclark> Can you look a bit deeper and see if you can figure it out?
[10:08:56 CDT(-0500)] <colinclark> It's not ringing any bells for me
[10:10:51 CDT(-0500)] <mlam> ok
[11:37:49 CDT(-0500)] <colinclark> Hey Justin_o I have a quick question if you have a second
[11:38:06 CDT(-0500)] <Justin_o> colinclark: sure
[11:38:22 CDT(-0500)] <colinclark> I'm confused about one of the issues we fixed for 1.3.1...
[11:38:25 CDT(-0500)] <colinclark> The Layout Reorderer
[11:38:32 CDT(-0500)] <Justin_o> colinclark: okay
[11:38:37 CDT(-0500)] <colinclark> I thought the idea was to fix all the extra tab stops
[11:38:41 CDT(-0500)] <colinclark> I'm just playing with the demo
[11:38:44 CDT(-0500)] <colinclark> Here
[11:38:45 CDT(-0500)] <colinclark> http://fluidproject.org/releases/1.3.1/demos/reorderer/layoutReorderer/html/layoutReorderer.html
[11:39:09 CDT(-0500)] <colinclark> But I seem to be able to focus all these inner containers with the tab key
[11:39:12 CDT(-0500)] <Justin_o> colinclark: hmm.. i'm pretty sure we did fix tht
[11:39:17 CDT(-0500)] <Justin_o> looks like it might have regressed
[11:39:30 CDT(-0500)] <colinclark> That's the release demo
[11:39:35 CDT(-0500)] <Justin_o> (sad)
[11:39:48 CDT(-0500)] <colinclark> Ah, you know what?
[11:39:53 CDT(-0500)] <colinclark> I think this might be the FF4 issue
[11:40:04 CDT(-0500)] <Justin_o> colinclark: yes.. i was just going to say that
[11:40:19 CDT(-0500)] <Justin_o> i just tested it in Safari and it's good
[11:40:38 CDT(-0500)] <Justin_o> well.. that's sort of good
[11:41:03 CDT(-0500)] <colinclark> Yeah, .demo-layoutReorderer-module-content has overflow set to auto
[11:41:05 CDT(-0500)] <colinclark> (sad)
[11:41:07 CDT(-0500)] <colinclark> This bug sucks
[11:41:16 CDT(-0500)] <colinclark> Okay
[11:41:34 CDT(-0500)] <Justin_o> guess it's not getting fixed for FF 4 final release eh
[11:41:37 CDT(-0500)] <colinclark> Nope
[11:41:40 CDT(-0500)] <colinclark> but it will be fixed for 5
[11:41:50 CDT(-0500)] <colinclark> David Bolter's been doing a really nice job of working on it
[11:41:51 CDT(-0500)] <Justin_o> that's good.. hopefully it will be out soon
[11:42:04 CDT(-0500)] <colinclark> If anyone is looking for bite-sized bugs, I think we should take a look at our use of overflow and see if we can remove it from certain demos
[11:42:14 CDT(-0500)] <colinclark> at least until FF5 comes out
[11:42:24 CDT(-0500)] <Justin_o> colinclark: fl-fix sets overflow to auto
[11:42:34 CDT(-0500)] <Justin_o> so it is part of our clearing strategy at the moment
[11:42:38 CDT(-0500)] <colinclark> Right
[11:42:39 CDT(-0500)] <Justin_o> for floated elements
[11:42:42 CDT(-0500)] <colinclark> How about with the new clear fixes?
[11:42:46 CDT(-0500)] <colinclark> Do they do the same?
[11:46:14 CDT(-0500)] <Justin_o> colinclark: no they don't use overflow
[11:46:22 CDT(-0500)] <colinclark> Okay, that's interesting
[11:46:31 CDT(-0500)] <colinclark> so if anything, 1.4 will improve this situation
[11:46:43 CDT(-0500)] <Justin_o> colinclark: if we change it (smile)
[11:46:52 CDT(-0500)] <colinclark> I guess we'll chat about that at the dev meeting, too?
[11:47:12 CDT(-0500)] <Justin_o> i'm leaning now towards keeping fl-fix and adding in another clearfix solution as well.. none of them seem to be perfect
[11:47:24 CDT(-0500)] <Justin_o> yes.. we can chat at the dev meeting about that too
[13:33:21 CDT(-0500)] <michelled> fluid-everyone: anyone want to be skyped into the dev meeting?
[16:00:05 CDT(-0500)] <Justin_o> colinclark: just read Bosmon's e-mail about jslint
[16:00:12 CDT(-0500)] <Justin_o> what are you thoughts about removing the jslint comments?
[16:10:31 CDT(-0500)] <colinclark> removing your jslint comments from the top of files?
[16:16:10 CDT(-0500)] <Justin_o> colinclark: yes.. i think Bosmon was recommending that we do that when his forked version of jslint is in place
[16:16:32 CDT(-0500)] <colinclark> I don't think that makes much sense
[16:16:47 CDT(-0500)] <colinclark> In that the comments are useful for command line or Node-hosted versions of JSLint
[16:16:56 CDT(-0500)] <colinclark> I think I must have missed that part
[16:17:00 CDT(-0500)] <colinclark> What was the rationale?
[16:17:54 CDT(-0500)] <Justin_o> colinclark: i don't think any was provided other than that we have the handy fluidic parts button in his forked jslint
[16:18:18 CDT(-0500)] <colinclark> Handy, but unnecessary, it seems (smile)
[16:20:54 CDT(-0500)] <Justin_o> I guess they both might be useful.. I think one of his previous arguments is that it's a lot of work to maintain if we change the options
[16:22:35 CDT(-0500)] <Justin_o> colinclark: ^
[16:22:58 CDT(-0500)] <colinclark> That's true
[16:23:14 CDT(-0500)] <colinclark> but it's comparable to what we end up doing to manage things like version updates
[16:23:17 CDT(-0500)] <colinclark> and it's self documenting
[16:23:25 CDT(-0500)] <colinclark> I dunno--do you have a personal preference, Justin_o?
[16:24:05 CDT(-0500)] <Justin_o> colinclark: not really.. either way we will have to probably update them all, since we'll either have to remove them or add the new options that Bosmon has implemented
[16:33:30 CDT(-0500)] <Justin_o> i suppose if it causes a problem with the official jslint then we shouldn't have the comments
[16:33:44 CDT(-0500)] <Justin_o> we can test that out after the fork goes live i guess