[08:32:02 EST(-0500)] * athena (n=athena@adsl-76-250-193-123.dsl.wlfrct.sbcglobal.net) has joined ##uportal
[09:00:33 EST(-0500)] * jessm (n=Jess@c-71-232-3-151.hsd1.ma.comcast.net) has joined ##uportal
[09:05:20 EST(-0500)] * tsnfoo (n=tsnfoo@wso-mbp15-2.test.denison.edu) has joined ##uportal
[09:12:57 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176130598.dsl.bell.ca) has joined ##uportal
[10:33:36 EST(-0500)] * awills (n=awills@wsip-72-215-204-133.ph.ph.cox.net) has joined ##uportal
[10:38:36 EST(-0500)] * tsnfoo_ (n=tsnfoo@cpe-173-88-27-191.columbus.res.rr.com) has joined ##uportal
[10:39:39 EST(-0500)] * holdorph (n=holdorph@wsip-72-215-204-133.ph.ph.cox.net) has joined ##uportal
[11:00:08 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined ##uportal
[11:11:15 EST(-0500)] <EricDalquist> hrm apparently isUserInRole isn't implemented in uportal how I thought it was
[11:11:23 EST(-0500)] <EricDalquist> right now it only works with group keys
[11:11:30 EST(-0500)] * michelled (n=michelle@142.150.154.101) has joined ##uportal
[11:11:40 EST(-0500)] <EricDalquist> would it make sense for it to try group key first and if no group exists for that key try group name?
[11:14:12 EST(-0500)] <athena> yes, that would be fabulous
[11:14:19 EST(-0500)] <EricDalquist> ok
[11:14:24 EST(-0500)] <athena> it's a huge pain that it's key-only right now
[11:14:28 EST(-0500)] <EricDalquist> I could have sworn that's how I originally implemented
[11:14:31 EST(-0500)] <athena> since those keys aren't constant
[11:14:35 EST(-0500)] <EricDalquist> yeah
[11:14:38 EST(-0500)] <athena> dunno, i've never seen it work that way
[11:15:09 EST(-0500)] <EricDalquist> guess I was just imagining it 
[11:16:33 EST(-0500)] * lennard1 (n=sparhk@ip68-98-56-21.ph.ph.cox.net) has left ##uportal
[11:16:50 EST(-0500)] <athena> oh well
[11:16:54 EST(-0500)] <athena> that'll be a nice improvement anyway
[11:17:14 EST(-0500)] <EricDalquist> yeah
[11:17:17 EST(-0500)] <EricDalquist> and easy to add
[11:18:02 EST(-0500)] <awills> that's a great enhancement, tyvm
[11:21:27 EST(-0500)] <EricDalquist> so for multiple hits should I just use the first one?
[11:21:51 EST(-0500)] <awills> sounds good, and maybe log a warning
[11:22:32 EST(-0500)] <EricDalquist> yeah
[11:23:17 EST(-0500)] * lennard1 (n=sparhk@ip68-98-56-21.ph.ph.cox.net) has joined ##uportal
[12:00:56 EST(-0500)] <athena> EricDalquist: i think everything for 3.2 is in the resource server
[12:01:02 EST(-0500)] <EricDalquist> great
[12:01:11 EST(-0500)] <EricDalquist> can you do a mvn release of it?
[12:01:13 EST(-0500)] <athena> yep
[12:01:21 EST(-0500)] <athena> just wanted to make sure there wasn't anything else you'd thought of
[12:01:38 EST(-0500)] <EricDalquist> nope
[12:02:10 EST(-0500)] <athena> sounds good then
[12:06:45 EST(-0500)] <tsnfoo> Is there any particular reason the the Portlet Manager Portlet is named as such?
[12:07:03 EST(-0500)] <tsnfoo> It replaces the chanel manager wholesale, right?
[12:07:19 EST(-0500)] <tsnfoo> Man, I'm spelling like a champ today...
[12:08:44 EST(-0500)] <EricDalquist> right
[12:08:46 EST(-0500)] <EricDalquist> it does
[12:08:49 EST(-0500)] <EricDalquist> and no
[12:08:56 EST(-0500)] <EricDalquist> it could probably just be called Portlet Manager
[12:09:42 EST(-0500)] <tsnfoo> Yeah, or something
[12:09:55 EST(-0500)] <EricDalquist> other ideas?
[12:10:44 EST(-0500)] <tsnfoo> Well, on the first page of results on the quickstart, it shows a bunch of things that aren;t Portlets
[12:10:54 EST(-0500)] <tsnfoo> maybe a more generic term would be better
[12:11:02 EST(-0500)] <tsnfoo> like "Content Manager or something
[12:12:03 EST(-0500)] <tsnfoo> Because adding an RSS feed doesn't appear to use the term "Portlet" anywhere in the process
[12:12:22 EST(-0500)] <tsnfoo> What you're really doing is adding content to the portal
[12:12:28 EST(-0500)] <EricDalquist> good point
[12:12:36 EST(-0500)] <tsnfoo> which can be of several supported (or deorecated) types.
[12:12:51 EST(-0500)] <EricDalquist> naming is always a problem when you have developers doing it (since under the hood they are all portlets)
[12:12:58 EST(-0500)] <tsnfoo> s/deorecated/deprecated/
[12:13:43 EST(-0500)] <tsnfoo> EricDalquist: Right - I was thinking the terminology should move into the user domain. Perception is reality, as it were.
[12:13:44 EST(-0500)] <holdorph> it depends though
[12:13:59 EST(-0500)] <holdorph> it all comes down to what the 'users' of the portal call those little rectangle boxes
[12:14:07 EST(-0500)] <holdorph> if they call them portlets, then it's a portlet manager
[12:14:13 EST(-0500)] <holdorph> if they call them channels it a channel manager
[12:14:23 EST(-0500)] <holdorph> if they call them 'content' then it's a content manager
[12:14:38 EST(-0500)] <tsnfoo> I knew you were going to say that 
[12:14:49 EST(-0500)] <holdorph> in my experience, not saying this represents everyone.... most people call them portlets
[12:14:52 EST(-0500)] <holdorph> even when they aren't
[12:15:04 EST(-0500)] <tsnfoo> Developers for sure
[12:15:10 EST(-0500)] <holdorph> no
[12:15:14 EST(-0500)] <holdorph> not just developers
[12:15:27 EST(-0500)] <tsnfoo> Our users have no idea what a portlet is, but probably think you plug a pen drive into it...
[12:15:28 EST(-0500)] <holdorph> managers, portal administrators, even users
[12:16:17 EST(-0500)] <tsnfoo> Our students tend to think of widgets or apps, in my observation
[12:16:29 EST(-0500)] <holdorph> they name can be changed, but I don't think the existing name is bad or incorrect by any stretch
[12:16:34 EST(-0500)] <tsnfoo> they kinda grok channel, but not really, and the rest is gibberish
[12:16:47 EST(-0500)] <holdorph> and it's not even a thing that end users should be using anyway
[12:17:30 EST(-0500)] <tsnfoo> I'd at least drop the redundant use of "Portlet" - redundant text == interface noise.
[12:17:52 EST(-0500)] <tsnfoo> holdorph: true, I just thought "Portlet Manager Portlet" sounded weird.
[12:18:07 EST(-0500)] <EricDalquist> yeah
[12:18:16 EST(-0500)] <EricDalquist> I'll at a minimum fix the redundant naming
[12:18:20 EST(-0500)] <tsnfoo> sweet
[14:48:20 EST(-0500)] <athena> i've always argued that we should call the boxes something that doesn't indicate the backend technology
[14:48:32 EST(-0500)] <EricDalquist> how about boxes?
[14:48:35 EST(-0500)] <EricDalquist> {color}
[14:48:35 EST(-0500)] <athena> i think it causes a whole lot of confusion
[14:48:40 EST(-0500)] <athena> i really don't care
[14:48:55 EST(-0500)] <athena> widgets, boxes, doodads, whatever.
General
Content
Integrations