fluid-work IRC Logs-2009-01-19

[08:10:36 EST(-0500)] * Justin_o (n=Justin@142.150.154.101) has joined #fluid-work
[08:32:32 EST(-0500)] * laurelw (n=Laurel@142.150.154.178) has joined #fluid-work
[08:52:05 EST(-0500)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[09:16:42 EST(-0500)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:24:31 EST(-0500)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:49:13 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has joined #fluid-work
[10:17:30 EST(-0500)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[10:30:29 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176406152.dsl.bell.ca) has joined #fluid-work
[12:12:02 EST(-0500)] * lessthanzero (n=FatalRem@CPE001ff342457c-CM001ac352aefc.cpe.net.cable.rogers.com) has joined #fluid-work
[12:23:59 EST(-0500)] * michelled (n=michelle@142.150.154.197) has joined #fluid-work
[12:24:16 EST(-0500)] <colinclark> Justin_o: I just saw michelled's response about testing Fluid-all.js
[12:24:28 EST(-0500)] <colinclark> What do you think of option #5? Do you think it's sufficient?
[12:26:05 EST(-0500)] <Justin_o> i believe it should be. the minimal set of files would have to make use of all of the js files that go into fluid-all.js
[12:26:32 EST(-0500)] <Justin_o> that should be enough to catch if anything is missing or not working properly as they did in 0.6
[12:26:58 EST(-0500)] <colinclark> So you guys think it's a good approach?
[12:27:03 EST(-0500)] <michelled> I think so
[12:27:24 EST(-0500)] <colinclark> ok
[12:27:29 EST(-0500)] <colinclark> i'm going to +1 the suggestion then
[12:27:32 EST(-0500)] <michelled> I'd want the samples to have different html. for example one of them should not specify the encoding
[12:27:32 EST(-0500)] <colinclark>
[12:27:36 EST(-0500)] <colinclark> right
[12:27:45 EST(-0500)] <colinclark> i guess a comment in the markup will be required for that
[12:27:54 EST(-0500)] <michelled> yes
[12:29:07 EST(-0500)] <colinclark> I guess the only downside is that, when checked out of svn, the shared examples won't work
[12:29:14 EST(-0500)] <colinclark> a build will have to be created?
[12:30:56 EST(-0500)] <Justin_o> yes...that would be a draw back... i suppose if the fluid-all.js is built with the nightly rebuild... then you could like it with the http:// address
[12:31:28 EST(-0500)] <colinclark> Justin_o: Yeah, there's no reason we can't build the distribution on a nightly basis
[12:31:39 EST(-0500)] <colinclark> michelled: Do you think this is a reasonable tradeoff?
[12:31:58 EST(-0500)] <colinclark> My only concern, I guess, is that we sometimes like showing off these shared examples.
[12:32:09 EST(-0500)] <colinclark> But I guess, as Justin_o says, we generally would do so on the build site.
[12:33:26 EST(-0500)] <Justin_o> colinclark: I'm not necessarily sold on any one solution at the moment... they all have pros and cons that i like and dislike... i'm probably easily swayed at the moment... but leaning towards option 5
[12:33:54 EST(-0500)] <colinclark>
[12:34:09 EST(-0500)] <colinclark> ok, well, perhaps i'll leave it for another day or two and see if any other feedback comes in
[12:34:28 EST(-0500)] <colinclark> it seems we have several of these "no clear best way" issues that we're debating at the moment.
[12:34:32 EST(-0500)] <colinclark> this and the documentation
[12:35:19 EST(-0500)] <Justin_o> that's true... maybe it needs some more time
[12:35:26 EST(-0500)] <michelled> sorry - was afk
[12:35:36 EST(-0500)] <michelled> yes, I think the tradeoff is reasonable
[12:35:46 EST(-0500)] <michelled> and we already build Fluid-all nightly
[12:35:57 EST(-0500)] <michelled> I believe the demos on the wiki link to it
[12:35:58 EST(-0500)] <colinclark> michelled: Oh, good.
[12:36:21 EST(-0500)] <colinclark> and i guess the wiki demos aren't sufficient for this kind of testing?
[12:36:29 EST(-0500)] <colinclark> I suppose we don't have enough control over the markup.
[12:37:07 EST(-0500)] <michelled> one of the problems with the wiki demos is that we don't have a full set of them
[12:37:27 EST(-0500)] <michelled> if we could put cycles into the wiki demos then that would probably be ok
[12:37:47 EST(-0500)] <michelled> if anyone had looked at the wiki demos for the 0.6 release then we would have found the bug
[12:37:57 EST(-0500)] <michelled> that's how I found it when doing the 0.7 release
[12:38:29 EST(-0500)] <colinclark> michelled: Interesting.
[12:38:36 EST(-0500)] <Justin_o> the only problem i see, is that we wouldn't be able to test the fluid-all.js file that is included in the build package...
[12:39:11 EST(-0500)] <colinclark> There's a real advantage the wiki demos, in that they're useful as part of our larger documentation effort.
[12:42:59 EST(-0500)] <michelled> I'd love to get anastasiac's opinion. She was the one who created the wiki demos. I've been feeling that fj4000's springboard, I mean functional demos, have taken their place.
[12:44:31 EST(-0500)] <michelled> and we'd still need to test the Fluid-all file in the release bundle as Justin_o mentioned
[12:46:48 EST(-0500)] <Justin_o> testing aside, i think it would be a good idea to have a live version embedded within the documentation (so you could see a working version as you learn how to make it). I'm not sure it will be enough for testing the release though
[12:47:45 EST(-0500)] <colinclark> Yeah, I agree with Justin_o about how it's useful to see a working version while you're learning what a component is or how to use it.
[12:48:06 EST(-0500)] <colinclark> And that's the main distinction between the wiki demos and the springboards.
[12:48:12 EST(-0500)] <colinclark> It's interesting, because several issues are converging here.
[12:48:52 EST(-0500)] <colinclark> 1. How we handle our documentation; 2. Our project directory structure and how we describe our various samples; 3. QA testing for Fluid-all.js
[12:51:30 EST(-0500)] <michelled> There's a related question I'm about to send to the list about what should be in Fluid-all.
[12:52:38 EST(-0500)] <colinclark>
[12:52:58 EST(-0500)] <colinclark> Antranig and I have it on our framework plan to build at least a Fluid-core.js as well.
[12:54:07 EST(-0500)] <colinclark> I'd like to see a version also that includes just enough framework support for the Uploader.
[12:54:22 EST(-0500)] <colinclark> I think it's going to be a hot component that people may want to try out without the rest of Fluid.
[12:55:38 EST(-0500)] <michelled> sounds like we need to get Simon's build scripts into trunk
[12:55:39 EST(-0500)] <Justin_o> maybe we should look at being able to build distributions on a component by component basis.. i think simon wanted to do something like that
[12:57:39 EST(-0500)] <colinclark> michelled: We definitely have to get on Simon's scripts by 0.9 at the latest, yep
[12:57:59 EST(-0500)] <colinclark> Justin_o: You're right. When it comes to the framework, it gets a bit more complicated.
[12:58:24 EST(-0500)] <colinclark> Since, at the moment, it's essentially treated as monolithic. Everything in Fluid.js is the framework.
[12:58:55 EST(-0500)] <colinclark> But we're probably going to have to take a look at how components use the framework, and see if we can break it up into modules. I had started that process of 0.5, but it was late in the game, and I only did a bit.
[13:18:45 EST(-0500)] * michelled (n=michelle@142.150.154.197) has left #fluid-work
[13:19:20 EST(-0500)] * michelled (n=team@142.150.154.197) has joined #fluid-work
[13:23:21 EST(-0500)] <lessthanzero> colin!
[13:23:21 EST(-0500)] <lessthanzero> clark!
[13:23:27 EST(-0500)] <lessthanzero> jess!
[13:23:35 EST(-0500)] <lessthanzero> great conversation going down in #codeigniter right now.
[13:25:50 EST(-0500)] * Topic is '0.8 here we go! http://issues.fluidproject.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10001&fixfor=10005' set by michelled on 2009-01-19 13:25:50 EST(-0500)
[14:02:43 EST(-0500)] * Topic is '0.8 Release Status: http://wiki.fluidproject.org/display/fluid/Fluid+0.8+Release+Status' set by michelled on 2009-01-19 14:02:43 EST(-0500)
[14:37:28 EST(-0500)] * phiggins (n=dante@c-68-34-199-67.hsd1.tn.comcast.net) has joined #fluid-work
[15:29:44 EST(-0500)] * mtheoryx83 (n=mtheoryx@c-68-58-86-205.hsd1.in.comcast.net) has joined #fluid-work
[15:30:05 EST(-0500)] <mtheoryx83> afternoon all!
[15:32:14 EST(-0500)] * laurelw (n=Laurel@142.150.154.178) has left #fluid-work
[15:49:05 EST(-0500)] <lessthanzero> hey mtheoryx83
[15:49:09 EST(-0500)] <lessthanzero> welcome welcome.
[15:49:19 EST(-0500)] <lessthanzero> I'm here on and off.
[15:49:29 EST(-0500)] <lessthanzero> when I remmeber to have colloquy open.
[15:52:06 EST(-0500)] <mtheoryx83> understood
[16:59:41 EST(-0500)] * michelled (n=team@142.150.154.197) has left #fluid-work
[17:26:10 EST(-0500)] * clown (n=clown@guiseppi.atrc.utoronto.ca) has left #fluid-work
[17:41:46 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176406152.dsl.bell.ca) has joined #fluid-work
[18:56:52 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176406152.dsl.bell.ca) has joined #fluid-work