fluid-work IRC Logs-2009-01-29
[07:23:47 EST(-0500)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[08:14:47 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[08:50:39 EST(-0500)] * phiggins_ (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[09:26:32 EST(-0500)] * apetro (n=apetro@12.164.139.7) has joined #fluid-work
[09:27:20 EST(-0500)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:29:35 EST(-0500)] * anastasiac (n=team@142.150.154.235) has joined #fluid-work
[10:07:15 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has joined #fluid-work
[10:57:46 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[11:17:58 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[11:44:18 EST(-0500)] * laurelw (n=laurel@dsl-207-112-65-164.tor.primus.ca) has joined #fluid-work
[11:59:12 EST(-0500)] * Bosmon (n=Antranig@ginger.caret.cam.ac.uk) has joined #fluid-work
[12:00:10 EST(-0500)] <Bosmon> Gah
[12:00:25 EST(-0500)] <Bosmon> It has somehow become very hard to get in here... since the IRC server no longer gives notification messages
[12:00:33 EST(-0500)] <Bosmon> Do we even have a topic?
[12:08:51 EST(-0500)] <Bosmon> Am i here?
[12:09:17 EST(-0500)] <Justin_o> Bosmon: you are here and i don't see a topic either
[12:09:54 EST(-0500)] * jrnorman (n=john@ginger.caret.cam.ac.uk) has joined #fluid-work
[12:12:54 EST(-0500)] * ecochran (n=ecochran@dhcp-169-229-212-43.LIPS.Berkeley.EDU) has joined #fluid-work
[12:14:29 EST(-0500)] * jrnorman (n=john@ginger.caret.cam.ac.uk) has joined #fluid-work
[12:14:40 EST(-0500)] * Topic is 'The Topic that is no Topic' set by Bosmon on 2009-01-29 12:14:40 EST(-0500)
[12:15:06 EST(-0500)] * EricDalquist (n=dalquist@128.104.17.46) has joined #fluid-work
[12:15:13 EST(-0500)] <Bosmon> So, we have a couple of "issues of the day"
[12:17:34 EST(-0500)] <Bosmon> There is http://issues.fluidproject.org/browse/FLUID-2173 - I am struggling to replicate the issue on my machine
[12:17:45 EST(-0500)] <Bosmon> I did see it once, but it seems easier to produce on Macs
[12:18:01 EST(-0500)] <Bosmon> I made a test case to try to demonstrate it, but noone seems to see it fail
[12:18:34 EST(-0500)] <Bosmon> Then there is http://issues.fluidproject.org/browse/FLUID-2174
[12:22:26 EST(-0500)] <Justin_o> how are you coming on that one
[12:25:56 EST(-0500)] <Bosmon> Oh yes, well I guess the reason I came in the channel was to ask people where they thought this "demo" stuff should live
[12:26:10 EST(-0500)] <Bosmon> It is a set of test data/layout material, that it seems to make sense to be shared between the automated and manual tests
[12:26:19 EST(-0500)] <Bosmon> But it's hard to think, in this case, which area it should live in...
[12:37:09 EST(-0500)] <anastasiac> so Bosmon and I were just re-examining FLUID-2117, the use of the 'shorthand' notation in specifying subcomponents in parent component default structure
[12:37:33 EST(-0500)] <anastasiac> on Jan 13, we had concluded that it doesn't scale well, and decided we should remove it
[12:37:53 EST(-0500)] <Bosmon> It is hard to tell whether we had some discussion after the Jan 13th chat log, or whether I simply didn't see the chat at the time
[12:38:10 EST(-0500)] <anastasiac> true
[12:38:13 EST(-0500)] <Bosmon> But my memory of how the issue was left doesn't agree with how the issue is written up
[12:38:27 EST(-0500)] <anastasiac> I don't remember a more recent discussion, but maybe you had it with colinclark or michelled
[12:38:39 EST(-0500)] <Bosmon> I remember having a discussion with michelle, certainly
[12:38:47 EST(-0500)] <anastasiac> hm - she's off today
[12:39:43 EST(-0500)] <anastasiac> might it have been on IM? does your IM client keep logs?
[12:40:14 EST(-0500)] <Bosmon> No, and unfortunately it crashes a lot
[12:43:11 EST(-0500)] <anastasiac> well, she might come online later, or join stand-up. I'll check in with her before committing anything
[12:44:19 EST(-0500)] <anastasiac> Bosmon, while I have your attention:
[12:44:35 EST(-0500)] <anastasiac> Was any progress made on the task of separating out the data binding from the renderer
[12:44:36 EST(-0500)] <anastasiac> ?
[12:44:42 EST(-0500)] <Bosmon> No, none
[12:44:58 EST(-0500)] <anastasiac> is there an ETA on when that might be done?
[12:45:08 EST(-0500)] <Bosmon> Well, not really
[12:45:12 EST(-0500)] <anastasiac>
[12:46:12 EST(-0500)] <anastasiac> ok - I'm refreshing my understanding of the renderer in prep for another push at documentation, and I wanted to know if that change was relatively imminent
[12:46:33 EST(-0500)] <Bosmon> Well, when it happens, I don't think it will cause all that much upheaval
[12:46:42 EST(-0500)] <Bosmon> There will be a new file, and a couple of new APIs
[12:46:47 EST(-0500)] <anastasiac> k
[13:21:13 EST(-0500)] <colinclark> Regarding the question of using the shorthand type specification in defaults.
[13:21:18 EST(-0500)] <Bosmon> Yes
[13:21:21 EST(-0500)] <colinclark> I think it's an idiom to avoid...
[13:21:28 EST(-0500)] <colinclark> It's the kind of thing that doesn't scale well.
[13:21:36 EST(-0500)] <colinclark> Perhaps at some point your subcomponent has no options...
[13:21:46 EST(-0500)] <Bosmon> Well, the situation of an "unconfigurable subcomponent" seemed quite stable to me
[13:22:01 EST(-0500)] <colinclark> but if someday it acquires some, it's easy to forget to change the format of your default options
[13:22:22 EST(-0500)] <colinclark> Things will appear to work from the component developer's end, but will break for the user when they actually try to override some options.
[13:22:39 EST(-0500)] <Bosmon> Oh well
[13:22:44 EST(-0500)] <Bosmon> This appears to be the Will of the Community
[13:22:46 EST(-0500)] <colinclark> It's one of those little things. It's not a big deal, but why use something that we can clearly identify as having potential for error?
[13:23:01 EST(-0500)] <Bosmon> I worry about the sprawling verbosity of all our JSON
[13:23:21 EST(-0500)] <Bosmon> Certainly so far, many of our attempts to shorten it could be said to have represented more trouble than they are worth
[13:23:27 EST(-0500)] <Bosmon> viz for example "dehydrated component trees"
[13:26:21 EST(-0500)] <colinclark> Bosmon: Yeah, I worry about that, too.
[13:27:19 EST(-0500)] <Bosmon> I think a lot of our component configuration "looks overcomplicated" now
[13:27:27 EST(-0500)] <Bosmon> I think it might well put people off
[13:35:54 EST(-0500)] <colinclark> Yep, that's a good point.
[13:36:04 EST(-0500)] <colinclark> I think it's something we should try to address.
[13:36:37 EST(-0500)] <colinclark> Though I think it's a separate problem to this short hand in the defaults issue.
[13:42:50 EST(-0500)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[14:30:48 EST(-0500)] * colinclark_ (n=colin@142.150.154.154) has joined #fluid-work
[15:42:55 EST(-0500)] * colinclark (n=colin@142.150.154.154) has joined #fluid-work
[15:45:12 EST(-0500)] * colinclark_ (n=colin@142.150.154.101) has joined #fluid-work
[16:59:30 EST(-0500)] * jayshao (n=jayshao@ool-44c4edd3.dyn.optonline.net) has joined #fluid-work
[17:30:29 EST(-0500)] * anastasiac (n=team@142.150.154.235) has left #fluid-work
[17:55:42 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has left #fluid-work
[18:07:16 EST(-0500)] * apetro (n=apetro@ip68-3-207-51.ph.ph.cox.net) has joined #fluid-work
[21:14:39 EST(-0500)] * laurelw (n=laurel@dsl-207-112-65-164.tor.primus.ca) has left #fluid-work