Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

[09:06:25 EST(-0500)] * jayshao (n=jayshao@jayshao.oirt.rutgers.edu) has joined #fluid-work
[09:35:22 EST(-0500)] * esm (n=esm@asdf.dkc.jhu.edu) has joined #fluid-work
[09:38:44 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has joined #fluid-work
[09:44:19 EST(-0500)] * michelled (n=team@142.150.154.199) has joined #fluid-work
[10:01:24 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[10:19:33 EST(-0500)] <clown> michelled: good morning.
[10:19:49 EST(-0500)] <michelled> good morning clown
[10:22:16 EST(-0500)] <clown> While going through the changes to the wiki, I noticed at least one page is getting a lot of spam attached to it. See the comments section on "http://wiki.fluidproject.org/display/~gthompson/Home?focusedCommentId=1710276&#034; Warning: the page will take a long time to load because there is a lot of spam there.
[10:22:34 EST(-0500)] <clown> I'm going to check a few other pages
[10:25:21 EST(-0500)] <michelled> I thought we'd turned off anonymous comments.
[10:26:27 EST(-0500)] <michelled> Are you looking into it?
[10:27:25 EST(-0500)] <clown> i was thinking about it. but there would be a learning curve. if you know how to fix it quickly, great.
[10:28:14 EST(-0500)] <clown> btw, i haven't found any other page so affected so far.
[10:30:21 EST(-0500)] <michelled> I'm guessing it's just a permission somewhere in confluence. I don't know off hand.
[10:35:14 EST(-0500)] <clown> i've looked in the security section, and I don't see that one. i'll look some more.
[10:35:31 EST(-0500)] <clown> "that one" = "turn off anonymous comments."
[10:46:19 EST(-0500)] <michelled> It's likely to be in the section that controls what users can do. There is likely an 'anyone' user group that has to be configured.
[10:47:47 EST(-0500)] <EricDalquist> hey
[10:47:57 EST(-0500)] <EricDalquist> so the link (replace the bit at the start for the fluid wiki) is: http://www.ja-sig.org/wiki/admin/permissions/globalpermissions.action
[10:48:26 EST(-0500)] <EricDalquist> on that page at the bottom there is a "Anonymous Access" section
[10:48:33 EST(-0500)] <EricDalquist> select edit permissions
[10:49:01 EST(-0500)] <EricDalquist> oh ... actually that may be the wrong link ... (smile)
[10:49:11 EST(-0500)] <EricDalquist> just a sec ... I know we turned this off for the jasig wiki
[10:50:30 EST(-0500)] <EricDalquist> ah right
[10:50:33 EST(-0500)] <EricDalquist> it is a per-space setting
[10:50:34 EST(-0500)] <EricDalquist> http://www.ja-sig.org/wiki/spaces/spacepermissions.action?key=JSG
[10:50:44 EST(-0500)] <EricDalquist> tweak that URL as appropriate for fluid
[10:50:55 EST(-0500)] <EricDalquist> there in an "Anonymous Access" section at the bottom
[10:51:06 EST(-0500)] <EricDalquist> on the ja-sig wiki anonymous users are only allowed to view
[10:52:21 EST(-0500)] <clown> hey thanks Eric (i just got back to my computer). I'll look into that.
[10:52:24 EST(-0500)] * jayshao (n=jayshao@wg-198-hill012.rutgers.edu) has joined #fluid-work
[10:52:37 EST(-0500)] <EricDalquist> np
[10:54:20 EST(-0500)] <clown> oh my. i got a "System Error" and a large stack trace using your first url.
[10:54:46 EST(-0500)] <EricDalquist> interesting
[10:54:47 EST(-0500)] <EricDalquist> well
[10:55:01 EST(-0500)] <EricDalquist> you get to that page by going to the home page of a space
[10:55:06 EST(-0500)] <EricDalquist> clicking the browse space link
[10:55:12 EST(-0500)] <EricDalquist> then the space admin tab
[10:56:29 EST(-0500)] <clown> ok, i'll try that
[11:02:08 EST(-0500)] <clown> that worked. well, for the Fluid space, anonymous commenting is off, as you suspected michelle. Only confluence-users are allowed to create comments. i'll check the other spaces to see if that reveals anything.
[11:18:11 EST(-0500)] <clown> aha - the "Open collection" space was allowing anonymous users to add comments. I've turned that ability off. But...is it a possilbe that it should be on?
[11:26:29 EST(-0500)] <michelled> No, it's just asking for trouble.
[11:26:45 EST(-0500)] <clown> indeed.
[11:27:22 EST(-0500)] <clown> is there a way to configure such permission for "people" pages. they appear to be in their own "people" space.
[11:27:26 EST(-0500)] <clown> ?
[11:47:12 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[12:05:24 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[13:20:52 EST(-0500)] * jhung (n=Fluid@142.150.154.178) has joined #fluid-work
[13:52:01 EST(-0500)] * jayshao (n=jayshao@jayshao.oirt.rutgers.edu) has joined #fluid-work
[13:52:58 EST(-0500)] * esm (n=esm@asdf.dkc.jhu.edu) has joined #fluid-work
[14:01:09 EST(-0500)] <clown> jQuery("some_selector")[0] is equivalent to jQuery("some_selector").get(0). We use both in our code. Is one preferable to the other? Anyone know?
[14:11:43 EST(-0500)] * clown_ (n=chatzill@user383.megabit.utoronto.ca) has joined #fluid-work
[14:12:16 EST(-0500)] * clown_ (n=chatzill@user383.megabit.utoronto.ca) has left #fluid-work
[14:13:23 EST(-0500)] <colinclark> clown: Sorry, I missed your message. One sec...
[14:16:04 EST(-0500)] * ecochran (n=ecochran@dhcp-169-229-212-31.LIPS.Berkeley.EDU) has joined #fluid-work
[14:16:53 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has left #fluid-work
[14:17:02 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has joined #fluid-work
[14:17:06 EST(-0500)] <colinclark> Eli: what's your preference...
[14:17:15 EST(-0500)] <ecochran> here
[14:17:27 EST(-0500)] <ecochran> but I don't know why
[14:17:33 EST(-0500)] * simonjb (n=Simon@142.150.154.170) has joined #fluid-work
[14:17:52 EST(-0500)] <colinclark> eocochran: jQuery ().get (0) or jQuery()[0]
[14:17:57 EST(-0500)] <colinclark> Sorry. I'm typing slow.
[14:18:07 EST(-0500)] <colinclark> Do you have a preference for the former or the latter?
[14:18:12 EST(-0500)] <colinclark> They're identifcal. Clown was asking.
[14:18:22 EST(-0500)] <colinclark> simonjb: Hi again!
[14:18:30 EST(-0500)] <ecochran> they are supposed to be equivalent but I had some trouble with ()[0]
[14:18:31 EST(-0500)] * colinclark is typing badly.
[14:18:35 EST(-0500)] <colinclark> Really?
[14:18:42 EST(-0500)] <ecochran> I may have mistyped
[14:19:20 EST(-0500)] <colinclark> clown: My preference has always been get(0), but I really can't justify why. [0] is more succinct, which is preferable.
[14:19:32 EST(-0500)] <colinclark> michelled: You were on the [0] side of the fence, right?
[14:19:39 EST(-0500)] <ecochran> Stop... .eq(0) and ()[0]
[14:19:43 EST(-0500)] <ecochran> not get(0)
[14:19:49 EST(-0500)] <ecochran> get(0) is different
[14:19:58 EST(-0500)] <colinclark> ?
[14:20:15 EST(-0500)] <clown> colinclark: yes, [0] is more succinct, and probably a nonasecond faster.
[14:20:23 EST(-0500)] <colinclark> "his function called as $(this).get(0) is the equivalent of using square bracket notation on the jQuery object itself like $(this)[0]."
[14:20:32 EST(-0500)] <colinclark> That should have been "this."
[14:20:45 EST(-0500)] <colinclark> Functions are gender neutral, I think. (smile)
[14:20:59 EST(-0500)] <ecochran> my code used .eq(0)
[14:21:03 EST(-0500)] <colinclark> Ah, I see.
[14:21:21 EST(-0500)] <ecochran> but I like [0]
[14:21:27 EST(-0500)] <colinclark> So shall we standardize on [0] because it's succinct?
[14:21:30 EST(-0500)] <ecochran> yes
[14:21:33 EST(-0500)] <clown> yes
[14:21:43 EST(-0500)] <michelled> yes
[14:21:49 EST(-0500)] <jhung> yes
[14:21:50 EST(-0500)] <colinclark> Michelle just said she doesn't care either way, but then said "certainly I like more succinct."
[14:22:00 EST(-0500)] <colinclark> She is ignoring us in favour of actually coding!!
[14:22:08 EST(-0500)] <ecochran> there is also the ever delightful :first
[14:22:12 EST(-0500)] <clown> good for her...
[14:22:16 EST(-0500)] <ecochran> which is english
[14:22:28 EST(-0500)] <colinclark> But then you have to use a selector.
[14:22:32 EST(-0500)] <colinclark> Which I can only assume is slower.
[14:22:32 EST(-0500)] <ecochran> yep
[14:22:36 EST(-0500)] <colinclark> So you'd do this? ...
[14:22:46 EST(-0500)] <clown> jQuery(...)[:first]?
[14:22:52 EST(-0500)] <colinclark> jQuery ("listOfBunchOfStuff").find(":first")
[14:23:05 EST(-0500)] <colinclark> clown: :first is a selector, so that wouldn't work.
[14:23:13 EST(-0500)] <ecochran> I'm usually addressing something by selector anyway
[14:23:32 EST(-0500)] <ecochran> Haven't tried find for that
[14:23:37 EST(-0500)] <ecochran> Find scares me
[14:23:45 EST(-0500)] <colinclark> (smile)
[14:23:58 EST(-0500)] <clown> colinclark: yeah, that's why I was "asking", by giving an example that couldn't possibly be correct.
[14:24:51 EST(-0500)] <ecochran> [0] is probably best when you want to cast a jQuery object or collection to a single DOM element
[14:25:06 EST(-0500)] <clown> btw, since jQuery() itself takes selectors as args, what's the difference between jQuery(":first") and find(":first")?
[14:25:26 EST(-0500)] <colinclark> clown: Good question.
[14:25:32 EST(-0500)] <colinclark> One sec... it's distracting in here today. (smile)
[14:25:43 EST(-0500)] <ecochran> you're not specifying first what
[14:25:58 EST(-0500)] <clown> eli, that's exaclty how it's being used. but so is get(0) being used that way (to get the first DOM element).
[14:26:19 EST(-0500)] <colinclark> find () lets you search in an existing jQuery.
[14:26:30 EST(-0500)] <colinclark> Make sense?
[14:26:33 EST(-0500)] <ecochran> :first would return a jQuery object
[14:26:38 EST(-0500)] <ecochran> I think
[14:26:54 EST(-0500)] * simonjb (n=Simon@142.150.154.170) has left #fluid-work
[14:26:56 EST(-0500)] <colinclark> eocochran: I think we're going to move our conversation with Resig to a channel on mozilla.org.
[14:26:59 EST(-0500)] <clown> whaddya mean "I think". We want definitive! (smile)
[14:27:02 EST(-0500)] <colinclark> Confusing.
[14:27:09 EST(-0500)] <colinclark> :first is a selector.
[14:27:28 EST(-0500)] <ecochran> to tell the truth, I don't usually worry about the object unless it doesn't work or I have to get a DOM object... most of the time it just works
[14:27:31 EST(-0500)] <colinclark> You would have to use a jQuery object to call any selector!
[14:27:39 EST(-0500)] * simonjb (n=Simon@142.150.154.170) has joined #fluid-work
[14:27:50 EST(-0500)] <colinclark> Like this jQuery (":first a") would get you the first <a> tag on the page.
[14:28:06 EST(-0500)] <colinclark> .find() lets you use a selector to search through an existing jQuery instance.
[14:28:11 EST(-0500)] <ecochran> no, jQuery('a:first')
[14:28:14 EST(-0500)] <clown> i see.
[14:28:29 EST(-0500)] <clown> makes sense
[14:28:30 EST(-0500)] <colinclark> Sorry, yes, you're right. (smile)
[14:28:43 EST(-0500)] <colinclark> jQuery ("a:first");
[14:28:57 EST(-0500)] <ecochran> technically :first refers the first child of that type
[14:29:07 EST(-0500)] <colinclark> Right.
[14:29:19 EST(-0500)] <clown> and jQuery ("a:first") returns? a jQuery object? or the first anchor dom element?
[14:29:22 EST(-0500)] <colinclark> http://docs.jquery.com/Selectors/first
[14:29:48 EST(-0500)] <ecochran> might not even work on a collection
[14:29:55 EST(-0500)] <ecochran> havn't tried
[14:30:04 EST(-0500)] <ecochran> back to [0]{color}
[14:30:11 EST(-0500)] <colinclark> clown: If you use the jQuery () function, the result will always be a jQuery instance.
[14:30:53 EST(-0500)] <clown> in that we are back to jQuery ("a:first")[0] vs. jQuery ("a:first").get(0). Or ":first" is a red herring in this context.
[14:31:04 EST(-0500)] <colinclark> Yes, exactly!
[14:31:14 EST(-0500)] <ecochran> sorry I even brought it up
[14:31:27 EST(-0500)] <ecochran> :first is not equivalent
[14:31:28 EST(-0500)] <colinclark> ecochran: No, it was a fun digression.
[14:31:35 EST(-0500)] <clown> no, not at all. how else will I learn these details?
[14:31:53 EST(-0500)] <colinclark> jQuery's documentation is very helpful, too. (smile)
[14:32:03 EST(-0500)] <clown> indeed
[14:32:05 EST(-0500)] <colinclark> So we'll stick to using the jQuery("foo")[0] instead of .get(0).
[14:32:08 EST(-0500)] <ecochran> so what's the diff between get() and eq()?
[14:32:21 EST(-0500)] <clown> colinclark: right
[14:32:52 EST(-0500)] <colinclark> ecochran: eq() actually modifies the jQuery set in-place.
[14:33:05 EST(-0500)] <colinclark> http://docs.jquery.com/Core/eq#position
[14:33:38 EST(-0500)] <colinclark> So if you have this: jQuery("selectorThatWillFindTonsOfStuff") and then for some reason you want to cut that set down to just one element, but have it continue to be a jQuery object, you'd use .eq(0).
[14:33:57 EST(-0500)] <clown> looks like eq(0) returns a jQuery object, but get(0) returns an element (when the array contains elements)
[14:34:20 EST(-0500)] <ecochran> ah, very nice. I've never used get() but now I will
[14:34:21 EST(-0500)] <colinclark> Yes, exactly.
[14:35:46 EST(-0500)] <colinclark> This is the longest fluid-work conversation on record, I think. (tongue)
[14:35:47 EST(-0500)] <clown> okay, i'm off to replace get(0) with [0] whenever the code is looking for the first dom element in the jQuery array.
[14:36:14 EST(-0500)] <clown> hey, when did antranig enter the room? and why is he disguised as colin?
[14:36:28 EST(-0500)] <colinclark> Glarg.
[14:36:33 EST(-0500)] <colinclark> CAT!
[14:36:34 EST(-0500)] <colinclark> (tongue)
[14:36:48 EST(-0500)] <clown> just remember, this is being recorded for eternity.
[14:37:06 EST(-0500)] <clown> and...it's public...
[14:37:09 EST(-0500)] <ecochran> the jQuery IRC is debating Ron Paul, this is why I'm never on IRC
[14:37:19 EST(-0500)] <clown> is he still in the race?
[14:37:28 EST(-0500)] <ecochran> as far as I know
[14:37:57 EST(-0500)] <clown> actually, ignore my last question; it means that fluid-work has begun to discuss Ron Paul. Let's nip that in the bud.
[14:38:05 EST(-0500)] <ecochran> thanks
[14:38:31 EST(-0500)] <EricDalquist> lol
[14:39:32 EST(-0500)] <ecochran> oh, I did use get() in the code that I sent Jonathan... damn, I knew what I was doing even when I didn't
[15:00:24 EST(-0500)] <colinclark> John Resig was happy with our proposal to Mozilla. So we'll keep our fingers crossed.
[15:00:37 EST(-0500)] <colinclark> It will be nice to have Fluid more involved in the jQuery community from an accessibility perspective.
[15:01:18 EST(-0500)] <clown> yes, we can make jAria rock, possibly.
[15:02:34 EST(-0500)] <colinclark> We should do that regardless.
[15:02:56 EST(-0500)] <colinclark> In our copious spare time.
[15:03:16 EST(-0500)] <colinclark> But in the meantime, we've got portlets to reorder. (smile)
[15:04:02 EST(-0500)] <clown> indeed.
[15:59:21 EST(-0500)] * esm (n=esm@asdf.dkc.jhu.edu) has joined #fluid-work
[16:44:00 EST(-0500)] * jhung (n=Fluid@142.150.154.178) has left #fluid-work
[17:01:19 EST(-0500)] * michelled (n=team@142.150.154.199) has left #fluid-work
[17:26:28 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has left #fluid-work

  • No labels