fluid-work IRC Logs-2009-07-21

Owned by Fluid IRC Log Bot
Last updated: Jul 21, 2009Version comment
4 min read

[07:04:32 EDT(-0400)] * heidi (n=thesumme@bas5-oshawa95-1176478111.dsl.bell.ca) has joined #fluid-work
[08:15:23 EDT(-0400)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[08:32:59 EDT(-0400)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[08:44:33 EDT(-0400)] * michelled (n=team@142.150.154.193) has joined #fluid-work
[09:06:19 EDT(-0400)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[09:21:41 EDT(-0400)] * yura (n=yura@142.150.154.168) has joined #fluid-work
[10:31:34 EDT(-0400)] * athena (n=athena@75.58.122.144) has joined #fluid-work
[10:59:37 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[11:46:26 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[11:49:56 EDT(-0400)] <laurel> jamon: do we still have a plan to meet today?
[11:54:27 EDT(-0400)] <jamon> laurel: how does 1-2pm work?
[11:55:17 EDT(-0400)] <jamon> laurel: also if you can show me the specific problem now i can look into it at lunch
[11:55:34 EDT(-0400)] <laurel> jamon: works for me.
[11:56:44 EDT(-0400)] * yura (n=yura@142.150.154.168) has joined #fluid-work
[12:11:36 EDT(-0400)] * jsilvaa (n=jsilva@142.150.82.73) has joined #fluid-work
[12:18:19 EDT(-0400)] * jessm (n=Jess@129.10.178.249) has joined #fluid-work
[13:30:52 EDT(-0400)] * mackrauss (n=mackraus@142.150.154.128) has joined #fluid-work
[13:38:04 EDT(-0400)] * mackrauss (n=mackraus@142.150.154.128) has joined #fluid-work
[13:38:04 EDT(-0400)] * athena (n=athena@75.58.122.144) has joined #fluid-work
[13:38:04 EDT(-0400)] * michelled (n=team@142.150.154.193) has joined #fluid-work
[13:38:04 EDT(-0400)] * heidi (n=thesumme@bas5-oshawa95-1176478111.dsl.bell.ca) has joined #fluid-work
[13:49:23 EDT(-0400)] * fj4000 (n=Jacob@142.150.154.106) has joined #fluid-work
[14:06:55 EDT(-0400)] <colinclark> but michelled had a good point yesterday about the lack of API changes
[14:07:23 EDT(-0400)] <colinclark> you bind to a particular version of fluid because you want to know that your code won't break if you update
[14:07:30 EDT(-0400)] <colinclark> which tends to happen because of api changes
[14:07:43 EDT(-0400)] <colinclark> here, we can guarantee the api is unchanged
[14:08:00 EDT(-0400)] <colinclark> changing an api in a minor release is unkind (wink)
[14:08:13 EDT(-0400)] <colinclark> on the other hand, if people were using the version number for something other than this, we'd be doing them a disservice by not changing it
[14:08:24 EDT(-0400)] <colinclark> but, if they are using the version number and want this fix for free, they'll be happier if they don't have change their own code
[14:08:45 EDT(-0400)] <colinclark> which makes me think that namespace version number changes should be restricted to API changes... in other words, to major releases.
[14:08:51 EDT(-0400)] <Justin_o> so the only real risk is that a user would run into is if 0.8 and 0.8.1 are both included, they may or may not get the version with the bug fix
[14:09:04 EDT(-0400)] <colinclark> there is a human-readble string in Fluid.js; that should change to 0.8.1 for sure
[14:09:08 EDT(-0400)] <colinclark> Justin_o: That's a really good point
[14:09:40 EDT(-0400)] * jessm (n=Jess@129.10.178.249) has joined #fluid-work
[14:09:56 EDT(-0400)] <jessm> jamon: ping
[14:10:22 EDT(-0400)] <colinclark> Justin_o: I guess our argument is that 0.8 should be removed from production and replaced with 0.8.1
[14:10:33 EDT(-0400)] <colinclark> or patched with the results of the 0.8.x branch
[14:10:53 EDT(-0400)] <colinclark> in other words, this is an "upstream" change
[14:11:24 EDT(-0400)] <colinclark> wiki's back
[14:11:56 EDT(-0400)] <Justin_o> colinclark: so we are saying that they should not be used together? meaning that anyone using 0.8 should update
[14:12:05 EDT(-0400)] <colinclark> Justin_o: I think that's the idea, yes.
[14:12:29 EDT(-0400)] <colinclark> athena: Hey, are you busy at the moment?
[14:12:32 EDT(-0400)] <jamon> jessm: pong
[14:13:24 EDT(-0400)] <colinclark> Justin_o: curious if jen has any advice on this one, since she's our Favourite User (smile)
[14:13:24 EDT(-0400)] <athena> hey colinclark: i'm helping with a demo at the moment
[14:13:26 EDT(-0400)] <athena> can i get back to you in 45min or so?
[14:13:30 EDT(-0400)] <jessm> jamon: can you jump on skype text?
[14:13:43 EDT(-0400)] <colinclark> athena: of course, no rush
[14:13:43 EDT(-0400)] <athena> lol
[14:13:44 EDT(-0400)] * athena is honored
[14:13:58 EDT(-0400)] <athena> be back in a bit
[14:14:00 EDT(-0400)] <colinclark> So Justin_o, in terms of moving forward:
[14:14:10 EDT(-0400)] <colinclark> I say no change to the namespace version number.
[14:14:31 EDT(-0400)] <jamon> jessm: ah i see your emails, one sec
[14:15:00 EDT(-0400)] <colinclark> Perhaps others will be able to share their opinion about it, and if consensus builds in the other direction, it'll be easy to change the version.
[14:15:08 EDT(-0400)] <colinclark> Justin_o: seem reasonable?
[14:18:53 EDT(-0400)] <yura> hey colinclark, Justin and I looked into tiny_mce editor user problem and it seems that it fails on loading the advance theme for the editor
[14:18:54 EDT(-0400)] <Justin_o> colinclark: yes i think so
[14:19:21 EDT(-0400)] <colinclark> yura: In any context, you mean? Not just when instantiating the component upon click?
[14:19:44 EDT(-0400)] <colinclark> Justin_o: cool. I'm gonna disappear in a sec. If you see jen return, can you walk her through the issue and see if she has an expert opinion?
[14:19:56 EDT(-0400)] <colinclark> I'm making some progress on my writing and want to try to wrap it up by the end of day.
[14:20:36 EDT(-0400)] <fj4000> michelled: you see this?
[14:20:44 EDT(-0400)] <yura> default inline edit instantiates with no errors, however if I enable advance theme it fails (I only tested that in the context of that user's example)
[14:20:53 EDT(-0400)] <Justin_o> colinclark: sure will do
[14:21:23 EDT(-0400)] <colinclark> yura: interesting
[14:24:04 EDT(-0400)] * michelled (n=team@142.150.154.193) has joined #fluid-work
[14:24:28 EDT(-0400)] <yura> colinclark: yes, i just tested it with one of the demo examples and it fails as well
[14:26:09 EDT(-0400)] * athena (n=athena@adsl-75-58-122-144.dsl.wlfrct.sbcglobal.net) has joined #fluid-work
[14:27:28 EDT(-0400)] * mackrauss (n=mackraus@142.150.154.128) has joined #fluid-work
[14:28:10 EDT(-0400)] * heidi (n=thesumme@bas5-oshawa95-1176478111.dsl.bell.ca) has joined #fluid-work
[15:14:11 EDT(-0400)] <athena> Justin_o: i don't think from a uportal standpoint it will affect us much if the version is renamed
[16:28:33 EDT(-0400)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[16:29:08 EDT(-0400)] <Justin_o> athena: sorry... i was away from my desk for a bit.
[16:29:57 EDT(-0400)] <athena> hey, no problem (smile)
[16:30:00 EDT(-0400)] * athena plays irc tag
[16:30:21 EDT(-0400)] <Justin_o> I think from yesterday you mentioned that uPortal currently doesn't use our versioning strategy, so either way it shouldn't affect uportal?
[16:30:26 EDT(-0400)] <athena> right
[16:30:32 EDT(-0400)] <athena> we really should start using it (smile)
[16:30:40 EDT(-0400)] <Justin_o> ah okay... thank you very much
[16:30:53 EDT(-0400)] <Justin_o> (smile)
[16:30:57 EDT(-0400)] <athena> though we're currently blowing away most of the javascript globals because of jquery's lack of versioning
[16:31:10 EDT(-0400)] <athena> so i think there are good arguments for doing either, and we'll be fine either way (smile)
[16:52:16 EDT(-0400)] <Justin_o> athena: thank you very much... i think we are going to go with the suggestion that was made earlier then and not change the version number unless there are api changes, which there won't be for this one
[16:53:32 EDT(-0400)] <athena> sounds reasonable
[16:53:42 EDT(-0400)] <Justin_o> thanks
[16:53:45 EDT(-0400)] <athena> (smile)
[16:54:20 EDT(-0400)] * Justin_o (n=Justin@142.150.154.171) has left #fluid-work