fluid-work IRC Logs-2009-11-23

[06:24:04 EST(-0500)] * sveto (n=sveto@62.44.101.70) has joined #fluid-work
[06:50:54 EST(-0500)] * boyan1 (n=boyan@62.44.101.70) has joined #fluid-work
[08:20:52 EST(-0500)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[08:38:44 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[08:43:44 EST(-0500)] * sveto_ (n=sveto@62.44.101.70) has joined #fluid-work
[08:53:20 EST(-0500)] * anastasiac (n=team@142.150.154.189) has joined #fluid-work
[09:01:47 EST(-0500)] * EricDalquist (n=dalquist@128.104.17.46) has joined #fluid-work
[09:09:03 EST(-0500)] * yura (n=yura@142.150.154.163) has joined #fluid-work
[09:10:08 EST(-0500)] * jameswy (n=jameswy@142.150.154.196) has joined #fluid-work
[09:33:33 EST(-0500)] <Justin_o> sveto_: Just wanted to say hi and see how everthing is going.. also, if you hadn't noticed, there was a recent conversation on the infusion users list about posting the data from a reorder operation back to the server. There may information in there that might be useful to you.
[09:34:05 EST(-0500)] * athena (n=athena@75.58.127.15) has joined #fluid-work
[09:35:42 EST(-0500)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[09:37:34 EST(-0500)] <sveto_> Justin_o: hi, I'll have a look, I've found a short example from a link in the reorderer API page that I intended to use. right now I'm waiting for McCord database to replicate locally as I want to see how users are organized there - I saw something is done in that direction for MMI and wanted to compare. Just to clarify this - we should have one central database for Engage that will contain user comments, collections and s.o., right?
[09:41:14 EST(-0500)] <Justin_o> I'm not entirely sure it may be that the user specific info is held in a user database and somehow related to the museums specific one... (although these would likely be databases within the same instance of couchdb). We'll probably need to check in with colinclark though. He may have an approach in mind already.
[09:50:12 EST(-0500)] <sveto_> Justin_o: should I then create a simple mapping between user ids and artifact names so I can develop further my collections and elaborate on it when we clarify the issue?
[09:52:04 EST(-0500)] <jameswy> sveto_: Give me a few minutes to mull that one over,
[09:57:04 EST(-0500)] <sveto_> sorry, I meant should I talk with colinclark before doing this?
[10:14:04 EST(-0500)] * michelled (n=michelle@142.150.154.193) has joined #fluid-work
[10:27:23 EST(-0500)] * jessm (n=Jess@c-71-232-1-65.hsd1.ma.comcast.net) has joined #fluid-work
[10:29:38 EST(-0500)] * sveto_ (n=sveto@62.44.101.70) has left #fluid-work
[10:33:10 EST(-0500)] <boyan1> michelled: I found that clicking on an image in ImageReorderer fires the onSelect event multiple times (= the number of images in the grid)
[10:33:15 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[10:33:40 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[10:33:43 EST(-0500)] <boyan1> michelled: unsure what to do I tried to create and fire my own event
[10:33:58 EST(-0500)] <boyan1> and got to the following question
[10:35:03 EST(-0500)]

[10:35:15 EST(-0500)] <boyan1> a remember reading somewhere the latter should not be used
[10:35:20 EST(-0500)] <boyan1> but cannot remember why
[10:37:09 EST(-0500)] <colinclark> boyan1: I'm coming in midway through your question, but I think I can answer.
[10:37:19 EST(-0500)] <colinclark> The former is based on the jQuery API, and is preferred.
[10:39:10 EST(-0500)] <boyan1> colinclark: thanks, I will use the former then
[10:39:35 EST(-0500)] <colinclark> Whereas, the latter form is the old Netscape style of registering event listeners
[10:39:58 EST(-0500)] <boyan1> colinclark, other than that, I found the following issue: clicking on an image in ImageReorderer fires the onSelect event multiple times (= the number of images in the grid)
[10:40:03 EST(-0500)] <colinclark> So, ensure cross-browser support, you'll want to bind all your events with jQuery to ensure that everything is normalized.
[10:40:17 EST(-0500)] <colinclark> boyan1: That seems pretty odd
[10:40:32 EST(-0500)] <colinclark> boyan1: How are you registering your click event?
[10:41:25 EST(-0500)] <boyan1> colinclark: yes, it does, and I managed to reproduce it in the imageReorderer demo that is in the infusion repository
[10:41:48 EST(-0500)] <colinclark> Really? Can you explain how to reproduce? Is there a JIRA ticket for this issue?
[10:42:08 EST(-0500)] <boyan1> colinclark: I have not written a JIRA issue and couldn't find one
[10:42:33 EST(-0500)] <boyan1> I'll give you the steps to reproduce in a minute
[10:42:45 EST(-0500)] * michelled (n=michelle@142.150.154.193) has joined #fluid-work
[10:48:35 EST(-0500)] <boyan1> colinclark: steps to reproduce:
[10:48:35 EST(-0500)] <boyan1> I added the following lines to imageThumbnail.js in infusion/src/webapp/demos/reorderer/imageReorderer/js folder
[10:48:35 EST(-0500)] <boyan1> var i = 0 as a first line of the formBasedImageReorderer function and
[10:48:35 EST(-0500)] <boyan1> listeners: {
[10:48:35 EST(-0500)] <boyan1> onSelect: function(item) {
[10:48:37 EST(-0500)] <boyan1> document.title = i++;
[10:48:39 EST(-0500)] <boyan1> }
[10:48:41 EST(-0500)] <boyan1> }
[10:48:43 EST(-0500)] <boyan1> in the list of options
[10:48:45 EST(-0500)] <boyan1> It is not a good testing scenario but was the first thing that came through my mind
[10:48:47 EST(-0500)] <boyan1> I would expect that on each click the title should increment with 1.
[10:48:49 EST(-0500)] <boyan1> Instead it increments with the number of images in the reorderer
[10:48:51 EST(-0500)] <boyan1> (tried the html in infusion/src/webapp/demos/reorderer/imageReorderer/html)
[11:10:30 EST(-0500)] <colinclark> boyan1: Interesting. Can you file a JIRA for this and we'll take a look?
[11:11:00 EST(-0500)] <boyan1> ok, I will file a JIRA and send out an email
[11:12:00 EST(-0500)] <colinclark> Thanks so much. I really appreciate it.
[11:27:59 EST(-0500)] * elicochran (n=elicochr@dhcp-169-229-212-80.LIPS.Berkeley.EDU) has joined #fluid-work
[11:38:46 EST(-0500)] * hydee (n=hydee@bas5-oshawa95-1176457924.dsl.bell.ca) has joined #fluid-work
[11:39:34 EST(-0500)] * heidi_ (n=hydee@bas5-oshawa95-1176457924.dsl.bell.ca) has left #fluid-work
[11:42:33 EST(-0500)] * hydee (n=hydee@bas5-oshawa95-1176457924.dsl.bell.ca) has joined #fluid-work
[11:43:15 EST(-0500)] * boyan1 (n=boyan@62.44.101.70) has left #fluid-work
[11:43:18 EST(-0500)] * hydee (n=hydee@bas5-oshawa95-1176457924.dsl.bell.ca) has left #fluid-work
[13:18:45 EST(-0500)] <elicochran> colinclark: is the list of "Production Ready" components still correct? http://wiki.fluidproject.org/display/fluid/Components
[13:19:20 EST(-0500)] <jessm> elicochran: see the demo portal: http://fluidproject.org/releases/1.1.2/demos/
[13:19:30 EST(-0500)] <jessm> it also gives "readiness" mention
[13:20:06 EST(-0500)] <elicochran> ah, that pretty much sync's up, but is much prettier!
[14:18:46 EST(-0500)] <athena> by the way, i think i probably know why the fluid uportal build is down at the moment
[14:19:07 EST(-0500)] <athena> we've discovered some incompatibilities between fluid's ant built recommendations and uportal's current build
[14:19:21 EST(-0500)] <athena> so if you use the same ant install to build both projects, that's likely the issue
[14:19:37 EST(-0500)] <colinclark> athena: eek
[14:19:39 EST(-0500)] <colinclark> right
[14:19:41 EST(-0500)] <athena> yeah
[14:19:48 EST(-0500)] <colinclark> We use the latest Ant, and uP uses 1.6.2, right?
[14:19:54 EST(-0500)] <athena> we spent a little while friday night sorting that out
[14:19:58 EST(-0500)] <athena> no, uportal can use 1.7.1
[14:20:01 EST(-0500)] <colinclark> ah
[14:20:15 EST(-0500)] <athena> but you guys have recommended installing extra jars in ant, i believe?
[14:20:32 EST(-0500)] <colinclark> yes, that's right
[14:20:36 EST(-0500)] <athena> yeah
[14:20:42 EST(-0500)] <athena> one of those is that's causing the problem
[14:21:10 EST(-0500)] <athena> uportal's now using a newer version of the maven ant tasks that isnt' compatible with the version fluid has
[14:21:35 EST(-0500)] <athena> if you look at uportal's build, they use extra ant jars, but have things set up such that you don't need to modify the ant installation
[14:21:39 EST(-0500)] <colinclark> athena: I wonder if we'll have any trouble upgrading ourselves to the newest version?
[14:21:51 EST(-0500)] <colinclark> smart
[14:22:16 EST(-0500)] <athena> probably not - our problem is that one of the new properties we're using in our build isn't available in the old ant task jar - i think it's backwards compatible
[14:22:30 EST(-0500)] <athena> yeah, eric set up the uportal build with what essentially is like an additional ant classpath
[14:23:18 EST(-0500)] <athena> he'd really be the one to speak to it, but if you wanted to take a look, most of the relevant stuff is in the bootstrap directory in uportal
[14:23:24 EST(-0500)] <colinclark> ok
[14:23:41 EST(-0500)] <colinclark> I'll see if one of us can find some time to take a look at it soon
[14:23:43 EST(-0500)] <colinclark> I miss our uPortal build already
[14:24:41 EST(-0500)] <athena> me too, it's a useful debugging tool sometimes
[14:25:33 EST(-0500)] <athena> wonder if it's possible to just update a jar or two in the meantime
[14:25:36 EST(-0500)] <athena> i don't really know
[14:46:26 EST(-0500)] <jamon> athena: i'm looking at the build server right now, is it just a matter of some extra ant tasks jar files? i can see about collecting them and trying the build that way
[14:47:20 EST(-0500)] <athena> i think you need to set up a bootstrap as well to pull them into the classpath
[14:47:23 EST(-0500)] <athena> EricDalquist would know more
[14:47:40 EST(-0500)] <jamon> ok, thanks athena
[14:47:52 EST(-0500)] <EricDalquist> I heard my name ...
[14:47:53 EST(-0500)] <athena>
[14:48:03 EST(-0500)] <athena> was talking about the ant bootstrap stuff
[14:48:21 EST(-0500)] <EricDalquist> ah yeah
[14:48:26 EST(-0500)] <EricDalquist> saw that
[14:49:18 EST(-0500)] <EricDalquist> here is an example of how we use maven-ant-tasks ant-contrib without modifying the ant install at all:
[14:49:19 EST(-0500)] <EricDalquist> https://www.ja-sig.org/svn/uPortal/trunk/bootstrap/build_includes.xml
[14:49:38 EST(-0500)] <EricDalquist> that file gets included by our main build.xml file
[15:16:45 EST(-0500)] <athena> by the way, another option just to get the nightly build back up and running would be to add an additional clean install of ant and just run uportal against that for the time being
[15:19:12 EST(-0500)] <jamon> athena: yeah i've tried that with various ant versions, there's some funky environment variables that keeps forcing ant 1.6.5 despite having 1.7.1
[15:19:54 EST(-0500)] <athena> you might be able to just set the nightly job to use the full path to the ant executable
[15:20:33 EST(-0500)] <jamon> yeah that's the thing, "ant" itself is a bash script that looks at environment variables for ant.jar
[15:20:45 EST(-0500)] <jamon> at this point i'm thinking about just upgrading the whole server
[15:20:51 EST(-0500)] <athena>
[15:21:13 EST(-0500)] <athena> i guess i just never bothered to set the ant environment variables on my laptop
[15:21:21 EST(-0500)] <athena> so it has nothing to look at ;P
[15:22:03 EST(-0500)] <jamon> heh, there are 4 different versions here, and they all end up running a fifth 1.6.5 that is somewhere else
[15:22:29 EST(-0500)] <EricDalquist> is this some version of linux?
[15:23:06 EST(-0500)] <jamon> EricDalquist: you could say that, gentoo 2007, with a million scripts and such in each user's $HOME
[15:23:20 EST(-0500)] <jamon> but that's why we're cleaning it up
[15:23:32 EST(-0500)] <EricDalquist> from my experience any 'ant' script included with a linux distribution is evil
[15:23:43 EST(-0500)] <EricDalquist> they do all sorts of non-standard ant finding tricks
[15:23:52 EST(-0500)] <EricDalquist> which make multiple ants very difficult
[15:24:04 EST(-0500)] <jamon> so i've discovered
[15:24:22 EST(-0500)] <EricDalquist> I usually delete the included ant script and just make sure the one I want used is first in the path
[15:24:29 EST(-0500)] <jamon> running an up to date distribution would make that slightly less painful
[15:27:06 EST(-0500)] <EricDalquist> yeah
[15:36:20 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[15:44:44 EST(-0500)] <athena> yeah, that's a pain
[15:44:48 EST(-0500)] <athena> gentoo is also a pain
[15:45:14 EST(-0500)] <athena> i've always thought of that distro more as an ongoing hobby than a working server option
[15:59:33 EST(-0500)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[16:29:02 EST(-0500)] <jamon> athena: i've learned it through nakul, and it has it's advantages for sure
[16:29:23 EST(-0500)] <athena> yeah, there are nice things about it
[16:29:24 EST(-0500)] <jamon> but i <3 debian
[16:29:26 EST(-0500)] <athena>
[16:29:45 EST(-0500)] <jessm> +1
[16:31:02 EST(-0500)] <jamon> athena, colinclark, jessm, uPortal demo is working again thanks to michelled
[16:31:14 EST(-0500)] <colinclark> jamon: You rule
[16:31:19 EST(-0500)] <colinclark> as does michelled
[16:31:22 EST(-0500)] <athena> woo! thanks
[16:31:32 EST(-0500)] <colinclark> jamon: What'd you end up doing?
[16:32:03 EST(-0500)] <jamon> was a matter of ~/.bashrc having a MAVEN2_HOME variable set, where the build.xml was reading maven.home from the M2_HOME environment variable
[16:32:15 EST(-0500)] <jamon> make sense?
[16:32:42 EST(-0500)] <jessm> that damned bashrc!
[16:33:21 EST(-0500)] <jamon> chsh -s /bin/zsh flexibus
[16:33:47 EST(-0500)] <jamon> i'm lazy, love zsh
[16:37:09 EST(-0500)] <athena> think i took an intro class from the guy it was named after
[16:37:42 EST(-0500)] <jamon> sweet
[16:39:41 EST(-0500)] * athena may not have spent a whole lot of time attending her intro classes
[16:40:39 EST(-0500)] <jessm> athena: shame! skipping class
[16:41:34 EST(-0500)] <athena>
[16:42:06 EST(-0500)] <athena> i showed up when they finally got challenging
[16:42:16 EST(-0500)] <athena> and for the non-science ones
[17:05:02 EST(-0500)] * anastasiac (n=team@142.150.154.189) has left #fluid-work
[17:49:09 EST(-0500)] * clown (n=clown@142.150.154.101) has left #fluid-work