Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

[03:54:30 EST(-0500)] * phiggins ( has joined #fluid-work
[04:19:07 EST(-0500)] * fj4000 (n=Jacob@ has joined #fluid-work
[08:18:39 EST(-0500)] * Justin_o (n=Justin@ has joined #fluid-work
[08:28:43 EST(-0500)] * fj40001 ( has joined #fluid-work
[08:35:45 EST(-0500)] * colinclark ( has joined #fluid-work
[08:36:25 EST(-0500)] <colinclark> wow, we have two models of fj400x here.
[08:36:38 EST(-0500)] <colinclark> fj40001 has been upgraded!
[08:36:56 EST(-0500)] <fj40001> arugh?
[08:37:05 EST(-0500)] <fj40001> I hate it when I do that.
[09:08:00 EST(-0500)] * michelled (n=team@ has joined #fluid-work
[09:27:02 EST(-0500)] * anastasiac (n=team@ has joined #fluid-work
[09:28:10 EST(-0500)] * EricDalquist ( has joined #fluid-work
[09:30:25 EST(-0500)] <Justin_o> fj4000: do you use some sort of debugger for IE on your machine at work
[09:35:03 EST(-0500)] * Topic is 'RELEASE DAY! Documentation:; ' set by anastasiac on 2008-12-18 09:35:03 EST(-0500)
[09:35:21 EST(-0500)] <anastasiac> Justin_o, I could use your help today with some of the release prep
[09:35:31 EST(-0500)] <Justin_o> sure ... what can i do for you
[09:35:38 EST(-0500)] <anastasiac> you have your finger on the pulse of the currently known issues
[09:35:48 EST(-0500)] <anastasiac> our release documentation should highlight those
[09:36:09 EST(-0500)] <anastasiac> do you think you could review JIRA and produce a list of the known issues you think people should really know about?
[09:36:37 EST(-0500)] <Justin_o> hmm... interesting... you want one for each component individually or as a whole
[09:37:43 EST(-0500)] <anastasiac> probably breaking it down by component would be helpful for readers
[09:37:53 EST(-0500)] <Justin_o> okay...
[09:38:31 EST(-0500)] <anastasiac> it doesn't have to be everything, of course, just the things that they probably should be warned about before they get started (smile)
[09:39:09 EST(-0500)] <Justin_o> I have already created the known issues and resolved issue jira filters for this release... and I'm going through all of them now to update the affects versions and getting rid of duplicates that may have been filed yesterday... i'll go through and look for these types of issues as i go along
[09:51:01 EST(-0500)] * EricDalquist ( has joined #fluid-work
[09:52:42 EST(-0500)] * clown ( has joined #fluid-work
[10:23:54 EST(-0500)] * phiggins ( has joined #fluid-work
[10:31:10 EST(-0500)] <Justin_o> michelled: did you review Fluid-2009
[10:31:28 EST(-0500)] <michelled> yes, I did
[10:31:35 EST(-0500)] <michelled> I'll comment on the JIRA
[10:31:38 EST(-0500)] <Justin_o> thanks
[10:33:35 EST(-0500)] * colinclark ( has joined #fluid-work
[10:51:50 EST(-0500)] <Justin_o> colinclark: I'm looking at
[10:52:09 EST(-0500)] <Justin_o> i'm wondering if i should close it or move it to a new version
[10:52:18 EST(-0500)] <colinclark> Justin_o: That one was resolved at the tail end of the bug parade
[10:52:20 EST(-0500)] <Justin_o> will the cancel button be coming back
[10:52:26 EST(-0500)] <colinclark> Justin_o: It will eventually
[10:53:04 EST(-0500)] <Justin_o> okay... i'll just close it for now and we can re-open it if need be in the future
[10:53:16 EST(-0500)] <colinclark> y
[11:08:08 EST(-0500)] * phiggins ( has joined #fluid-work
[11:09:34 EST(-0500)] * phiggins ( has left #fluid-work
[11:34:36 EST(-0500)] <Justin_o> anastasiac: just to let you know there is still a jira open for release commits FLUID-1962
[11:39:21 EST(-0500)] * ecochran ( has joined #fluid-work
[11:45:48 EST(-0500)] <michelled> fj40001, you there?
[11:49:03 EST(-0500)] <fj40001> yup
[11:49:41 EST(-0500)] <michelled> I'm working on the API docs for UI Options and I realized that there is some missing here
[11:49:57 EST(-0500)] <fj40001> whats missing?
[11:50:28 EST(-0500)] <michelled> programmatically applying skins docs
[11:50:38 EST(-0500)] <michelled> essentially Skin.js is part of FSS
[11:50:45 EST(-0500)] <michelled> but I'm not sure where the docs belong
[11:50:46 EST(-0500)] <fj40001> hmmm
[11:50:58 EST(-0500)] <fj40001> since the two are tied so close together?
[11:51:37 EST(-0500)] <michelled> well FSS is more then CSS - if you know what I mean
[11:51:48 EST(-0500)] <fj40001> yes
[11:51:53 EST(-0500)] <michelled> and the js that goes along with it is currently in Skin.js
[11:52:01 EST(-0500)] <michelled> the top level fluid.applySkin
[11:52:40 EST(-0500)] <michelled> and the functions inside - removeStyling and style
[11:52:44 EST(-0500)] <fj40001> well...since it really only does anything in the context of UI Options
[11:52:51 EST(-0500)] <fj40001> I guess it belongs there too, right?
[11:53:12 EST(-0500)] <fj40001> and from there, it could point to all the FSS docs im writing
[11:53:16 EST(-0500)] <michelled> well, it's not true that only does something in the context of UI Options
[11:53:36 EST(-0500)] <fj40001> brb
[11:54:27 EST(-0500)] <michelled> meaning - you don't need UI Options to apply a skin programmatically - what you need is a javascript objects with the selected settings
[11:55:31 EST(-0500)] <michelled> for example if you look at the uPortal example right now, it does not include UIOptions.js - only Skin.js and it uses the those functions I mentioned to apply the appropriate settings
[12:01:27 EST(-0500)] <michelled> I think I'll create a new page and we can both link to it
[12:03:43 EST(-0500)] * jrnorman ( has joined #fluid-work
[12:08:12 EST(-0500)] <fj40001> michelled: can you elaborate how you could use skin.js without the UI Options interface?
[12:09:18 EST(-0500)] <michelled> for example once the UI Options is integrated into an actual app, all pages that the application creates needs to be styled appropriately but they may not all contain a UI Options component
[12:09:20 EST(-0500)] * apetro_ ( has joined #fluid-work
[12:09:22 EST(-0500)] <michelled> does that make sense?
[12:10:29 EST(-0500)] <fj40001> ohh
[12:10:30 EST(-0500)] <fj40001> I see
[12:10:46 EST(-0500)] <fj40001> so they would need to call skin.js on their own to apply it?
[12:11:00 EST(-0500)] <michelled> ya - just like the uportal example does
[12:11:08 EST(-0500)] <fj40001> thats very cool
[12:11:36 EST(-0500)] <fj40001> then is it fair to say its the bridge or link between the css and the js?
[12:12:03 EST(-0500)] <fj40001> sorry
[12:12:12 EST(-0500)] <michelled> it's the bridge between the CSS portion of FSS and the javascript component UI Options
[12:12:14 EST(-0500)] <fj40001> the js = UI Options
[12:12:19 EST(-0500)] <fj40001> yes
[12:12:22 EST(-0500)] <fj40001> my mistake
[12:12:44 EST(-0500)] <michelled> so it's really the javascript portion of FSS - don't you think?
[12:13:11 EST(-0500)] <fj40001> you know, I never really imagined FSS being more than the CSS part, but now I think your right
[12:13:26 EST(-0500)] <fj40001> it is the js face of the FSS
[12:13:31 EST(-0500)] <michelled> yes
[12:14:02 EST(-0500)] <fj40001> so then I would like to answer your question with a question
[12:14:23 EST(-0500)] <michelled> actually, that's what the namespace for those functions should be. I had so much trouble figuring it out. so we should have a 'fluid.fss' namespace
[12:15:04 EST(-0500)] <michelled> ask away
[12:15:05 EST(-0500)] <fj40001> as opposed to just the fluid namespace?
[12:15:07 EST(-0500)] <fj40001> ok
[12:15:29 EST(-0500)] <fj40001> so you were asking where to put the api docs, right?
[12:15:58 EST(-0500)] <michelled> ya, because I felt they should be part of the FSS API docs
[12:16:16 EST(-0500)] <fj40001> as far as I understand, FSS API would only cover Skin.js
[12:16:23 EST(-0500)] <fj40001> since the CSS is being documented elesewhere
[12:16:31 EST(-0500)] <fj40001> in the tutorials
[12:16:47 EST(-0500)] * colinclark (n=colin@ has joined #fluid-work
[12:16:51 EST(-0500)] <fj40001> since there really isnt a clear way to put CSS into a nice API article
[12:18:10 EST(-0500)] <fj40001> unless you might say the UI Options component, Skin.js, and the CSS are all under the FSS umbrella
[12:19:34 EST(-0500)] * michelled afk
[12:38:49 EST(-0500)] * phiggins ( has joined #fluid-work
[12:41:03 EST(-0500)] * michelled is back
[12:42:30 EST(-0500)] <michelled> ya, they are all closely related
[13:02:39 EST(-0500)] * dlester_ (n=dlester@ has joined #fluid-work
[13:28:34 EST(-0500)] <Justin_o> anastasiac: do you know if this one was fixed, if not maybe it is something we could do as part of this release
[13:31:29 EST(-0500)] <anastasiac> Justin_o, good catch
[13:31:45 EST(-0500)] <anastasiac> we added license info, but not version info
[13:32:33 EST(-0500)] <Bosmon> I am sort of here now
[13:32:36 EST(-0500)] <Justin_o> okay... i'm going through jira so i'm seeing all of these issues... i'll let you know if anything else comes up
[13:32:39 EST(-0500)] <Bosmon> But a bit confused after Christmas Lunch
[13:32:49 EST(-0500)] <anastasiac> "confused" ?
[13:32:53 EST(-0500)] <Justin_o> Bosmon: what did you eat?
[13:32:56 EST(-0500)] <anastasiac> nice euphamism
[13:33:44 EST(-0500)] <Bosmon> It was Christmas Lunch (tongue)
[13:33:49 EST(-0500)] <Bosmon> It can only consisted of one thing
[13:34:46 EST(-0500)] <Justin_o> Bosmon: so i was going to ask you how you wanted to handled bugs filed in jira which should be fixed by someone else... i.e. jQuery
[13:35:29 EST(-0500)] <Bosmon> Yes
[13:35:35 EST(-0500)] <Bosmon> I suppose we should have a new category
[13:35:39 EST(-0500)] <Bosmon> Something like "Escalated"
[13:35:44 EST(-0500)] <Bosmon> Or rather, a new "disposition"
[13:35:49 EST(-0500)] <Bosmon> For "what has been done with the bugs"
[13:36:09 EST(-0500)] <Bosmon> After we raise them in the relevant place, we can mark them "Closed as Escalated" with a reference to the external JIRA or whatever crappy thing they run
[13:37:45 EST(-0500)] <Justin_o> so there are two areas that I could add a new type to, 1) is the status 2) is the Resolution... so we could keep closed as the status and create a new resolution of type "Escalated"
[13:38:06 EST(-0500)] <Bosmon> ok
[13:38:12 EST(-0500)] <Bosmon> 2 sounds reasonable to me
[13:38:44 EST(-0500)] <Justin_o> okay... i'll create a new resolution type of Escalated...
[13:39:36 EST(-0500)] <Justin_o> here is a quick question... do you think they should be closed if the problem still exists... or should they be open with resolution escalated until the 3rd party fixes it
[13:40:21 EST(-0500)] <Justin_o> oh well... i don't think you can assign a resolution without it being closed... so never mind
[13:40:22 EST(-0500)] <Bosmon> That's an interesting question
[13:40:35 EST(-0500)] <Bosmon> Yes
[13:40:42 EST(-0500)] <Justin_o> if that is the case, then maybe my resolution idea isn't correct
[13:40:54 EST(-0500)] <Justin_o> maybe the status should be escalated...
[13:41:23 EST(-0500)] <Bosmon> I guess the question is just what would be most interesting/unsurprising to people browsing the JIRA
[13:41:36 EST(-0500)] <Bosmon> Typically you will browse for "Open" issues, perhaps looking for work to do
[13:41:49 EST(-0500)] <Bosmon> These Escalated issues would be a rather grey area
[13:42:07 EST(-0500)] <Bosmon> Since there does remain work to do, that of chivvying the upstream geezer, or trying to determine if he has done anything relevant
[13:42:16 EST(-0500)] <Bosmon> But it is not in the same sense, your work....
[13:42:18 EST(-0500)] <Justin_o> yes... that is true... i'm also thinking about people who may be looking through our jira if they are trying to find out why something isn't working
[13:42:44 EST(-0500)] <Justin_o> like an implementor
[13:42:51 EST(-0500)] <Bosmon> But for those communities we don't really have relationships with, there might not really be anything "to be done"
[13:43:01 EST(-0500)] <Bosmon> Appearing on forums and griping, perhaps
[13:43:04 EST(-0500)] * dlester (n=dlester@ has joined #fluid-work
[13:43:23 EST(-0500)] <Justin_o> that's always an option... may not work though
[13:43:26 EST(-0500)] <Bosmon> (smile)
[13:43:37 EST(-0500)] <Bosmon> Being a pessimist, I find it hard to imagine any of these issues will ever be resolved
[13:43:44 EST(-0500)] <Bosmon> Especially the "tab focus black hole" one
[13:43:49 EST(-0500)] <Bosmon> But we can only do our best
[13:44:06 EST(-0500)] <Justin_o> yes... i do agree...
[13:45:07 EST(-0500)] <Justin_o> in the end, i'm only afraid of marking it closed as it may imply that we are no longer tracking the issue
[13:51:16 EST(-0500)] <Bosmon> OK
[13:51:31 EST(-0500)] <Bosmon> So, "Escalated" is at the least, going to be a form of being "Unresolved"
[13:51:42 EST(-0500)] <Justin_o> yes
[13:52:13 EST(-0500)] <Justin_o> so if it were a status then instead of being open.. it would be escalated
[13:54:04 EST(-0500)] <Justin_o> would that seem to make sense for you...
[13:54:45 EST(-0500)] <Justin_o> or would you find it confusing as you were traversing through jira
[14:02:40 EST(-0500)] <anastasiac> Bosmon, what is the status of the Pager API page - is there still work to do on it?
[14:09:58 EST(-0500)] <colinclark> I prefer 1
[14:10:44 EST(-0500)] <Bosmon> Yes, there is, sorry
[14:10:49 EST(-0500)] <Bosmon> I have it open in an edit buffer here
[14:11:00 EST(-0500)] <Bosmon> But a rather distracting conversation has blown up down here
[14:11:03 EST(-0500)] <anastasiac> ok - are you updating it to reflect what's in trunk?
[14:11:16 EST(-0500)] * michelled (n=team@ has left #fluid-work
[14:11:16 EST(-0500)] <Bosmon> yes
[14:11:31 EST(-0500)] <anastasiac> ok, cool - Justin_o wasn't sure if you'd been working in a branch or not
[14:11:40 EST(-0500)] <Bosmon> No, everything is in trunk
[14:11:45 EST(-0500)] <anastasiac> excellent
[14:11:51 EST(-0500)] <Bosmon> The only thing that might have gone in a branch is my sakai-site-setting demo
[14:11:59 EST(-0500)] <Bosmon> But FEES convinced me it was too late to disturb trunk now
[14:12:19 EST(-0500)] * dlester (n=dlester@ has joined #fluid-work
[14:14:55 EST(-0500)] <colinclark> dlester: Hey! An Omeka-ite!
[14:15:00 EST(-0500)] <colinclark> Welcome
[14:15:05 EST(-0500)] <anastasiac> welcome, dlestser!
[14:15:43 EST(-0500)] <dlester> howdy colinclark and anastasiac
[14:16:48 EST(-0500)] <Bosmon> OMEKA
[14:20:52 EST(-0500)] <anastasiac> Justin_o, any progress on the short-list of known issues for the Readme?
[14:22:03 EST(-0500)] <Justin_o> i have lists for Uploader and UI Options
[14:22:09 EST(-0500)] <Justin_o> what is your definition of short though
[14:24:42 EST(-0500)] * michelled (n=michelle@ has joined #fluid-work
[14:25:07 EST(-0500)] <anastasiac> Justin_o: top one or two issues per component (three, if necessary)
[14:27:05 EST(-0500)] <Justin_o> oh okay... sure
[14:27:08 EST(-0500)] <ecochran> anastasiac, colinclark, and anyone else who's interested : I've just checked in the new ReadMe for the Uploader [/js/fluid/uploader/ReadMe.txt]. Please take a look at it
[14:27:19 EST(-0500)] <anastasiac> ecochran, thanks!
[14:27:23 EST(-0500)] <Justin_o> anastasiac: i suppose you are just going to list them then and don't need a jira filter
[14:27:46 EST(-0500)] <anastasiac> right - just a bullet-point kind of thing
[14:28:16 EST(-0500)] <ecochran> I'm running up to campus soon, so if I'm offline, I'll be back after my 12 noon team meeting
[14:28:54 EST(-0500)] <colinclark> ecochran: "In Firefox and IE, the Flash-based Browse button does not size correctly..."
[14:29:04 EST(-0500)] <colinclark> I think I'd go ahead and put specific version numbers here
[14:29:26 EST(-0500)] <colinclark> FF3 and IE7 seem to be susceptible to the worst resizing issues with the Flash movie.
[14:29:50 EST(-0500)] <ecochran> Well, I checked in FF3 and 2 and found that even though it sizes better in FF2, I still wouldn't call it "correct"
[14:30:07 EST(-0500)] <ecochran> since in FF2 it doesn't resize
[14:30:20 EST(-0500)] <ecochran> I didn't check IE6
[14:30:20 EST(-0500)] <colinclark> yes, true
[14:30:24 EST(-0500)] <colinclark> it's like FF2
[14:30:28 EST(-0500)] <ecochran> ah
[14:30:33 EST(-0500)] <colinclark> " The flashUrl option is probably wrong. Check that first. "
[14:30:54 EST(-0500)] <colinclark> I guess, to be accurate it would be the flash9URL and flash10URL options are probably wrong.
[14:31:09 EST(-0500)] <ecochran> good catch
[14:31:26 EST(-0500)] <Bosmon> OK, I have to go on to dinner now
[14:31:34 EST(-0500)] <Bosmon> I have left Pager API page in a sort of 70% done condition (sad)
[14:31:47 EST(-0500)] <Bosmon> Hopefully I can finish it off in the evening, but I have some structural problems
[14:32:47 EST(-0500)] <colinclark> Bosmon: Enjoy dinner
[14:34:11 EST(-0500)] <ecochran> colinclark: anything else?
[14:34:11 EST(-0500)] <ecochran> I struggled to not use "harsh language" :-p
[14:34:28 EST(-0500)] <colinclark> ecochran: (wink)
[14:35:22 EST(-0500)] <colinclark> ecochran: I think it's charmingly written.
[14:35:37 EST(-0500)] <colinclark> Even Gyphie himself wouldn't be offended.
[14:35:39 EST(-0500)] <ecochran> colinclark: lol
[14:36:07 EST(-0500)] <ecochran> colinclark: as long as it is also "truthful"
[14:36:16 EST(-0500)] <colinclark> yep, it's uniquely correct
[14:37:47 EST(-0500)] <ecochran> colinclark: how much of this should go into the general Infusion ReadMe. Can we get away with "Read the Uploader ReadMe at <path>" or should I detail all the failings there as well?
[14:38:18 EST(-0500)] <colinclark> I think a fair bit of it should go into the general readme
[14:38:27 EST(-0500)] <colinclark> anastasiac can cherry pick from the uploader readme file
[14:39:30 EST(-0500)] <ecochran> colinclark : OK, I'll leave it to anastasiac for now
[14:39:44 EST(-0500)] <ecochran> gotta run... be back online at 1pm
[14:45:10 EST(-0500)] * jessm ( has joined #fluid-work
[14:46:28 EST(-0500)] <jessm> where's the release party?
[15:01:35 EST(-0500)] * jessm ( has joined #fluid-work
[15:21:50 EST(-0500)] * jessm wants cake and party
[15:30:41 EST(-0500)] <anastasiac> jessm is missing cake, crumble, cookies, crackers and dip, chocolates and wine
[15:30:59 EST(-0500)] <jessm> oh well!
[15:31:04 EST(-0500)] <jessm> Happy Release y'all
[15:31:06 EST(-0500)] <jessm> way to go!!
[15:31:08 EST(-0500)] <jessm> woot woot
[15:36:06 EST(-0500)] * colinclark (n=colin@ has joined #fluid-work
[15:38:26 EST(-0500)] <colinclark> jessm: If only we could courier you some cake
[15:38:31 EST(-0500)] <colinclark> (sad)
[15:38:34 EST(-0500)] <colinclark> It was a nice party
[15:38:42 EST(-0500)] <jessm> i'm glad! (smile)
[15:38:50 EST(-0500)] <jessm> i celebrated here with some fig newtons
[15:38:57 EST(-0500)] <colinclark> ha!
[15:42:32 EST(-0500)] * phiggins ( has joined #fluid-work
[16:26:47 EST(-0500)] * ecochran (n=ecochran@dhcp-169-229-212-48.LIPS.Berkeley.EDU) has joined #fluid-work
[16:28:50 EST(-0500)] * apetro- (n=apetro@ has joined #fluid-work
[17:02:00 EST(-0500)] * michelled (n=michelle@ has left #fluid-work
[17:09:02 EST(-0500)] * apetro_ ( has joined #fluid-work
[17:23:53 EST(-0500)] * apetro-_ (n=apetro@ has joined #fluid-work
[17:27:38 EST(-0500)] * clown ( has left #fluid-work
[17:48:56 EST(-0500)] * anastasiac (n=team@ has left #fluid-work
[17:58:02 EST(-0500)] * phiggins ( has joined #fluid-work
[18:14:01 EST(-0500)] * colinclark ( has joined #fluid-work
[18:18:41 EST(-0500)] * apetro_ ( has joined #fluid-work
[18:21:21 EST(-0500)] * apetro- ( has joined #fluid-work
[19:24:24 EST(-0500)] * jessm ( has joined #fluid-work
[21:21:32 EST(-0500)] * apetro_ ( has joined #fluid-work