On Oct 7, 2011, at 2:00 PM, Drew Wills wrote: > On 10/7/2011 1:48 PM, Eric Dalquist wrote: >> How about we do something like: <xsl:copy-of >> select"//channel[parameter[@name = 'notificationPortlet' and >> @value='true']]"/> (note that XPath is off the top of my head and may >> not be 100% syntactically correct but thats the idea) >> > > Sounds good. We could even do just... > > <xsl:copy-of select"//channel[parameter[@role = 'notifications']"/> > > And use (only) an arbitrary publishing parameter.
This seems like it would work well. Just as a sanity check though, I don't think there's a technical requirement that a portlet linked from the theme be a framework portlet. We'd certainly include such a cool, useful portlet in the default overlays and create a default portlet registration for it. This suggestion does seem to add some nice flexibility though! > What about Jasig Widget Portlets for a home? To me, these portlets seem like > tiny things that are best included within some broader collection or platform > -- not the sort of thing you'd spin up an entire project for. Sounds great to me. At some point it's nice to group portlets together just to save on startup time and perigean space, and this sounds like a simple portlet that'd be a great match for that portlet set. - Jen -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
