This sounds like a good starting approach - not that I can really weigh
in on the framework implementation - but the end result of having
attributes on the <channel> elements should do the job. That then also
opens up a means for specifying channels to render "borderless",
"highlighted", "alternate", or other possibilities.
It would be good to have the Set Channel Attributes page be a default
part of the publishing process for all channel/portlet types.
Gary
Eric Dalquist wrote:
I believe we're specifically targeting uPortal 3.0 with this feature
though as with anything if it works in 2.X no reason not to.
In the sandbox code I believe there was a planned concept of
portlet/channel attribute sources. These would be additional places
that fed attributes on to the <channel> elements in the layout. I
would think in uPortal 2 and 3 this would be fairly reasonable to
achieve by adding an additional SAX filter in the rendering chain or
in the layout loading code to add these attributes to each channel
from some backing store. As long as there isn't a requirement for
these to be dynamic I don't think it would have to involve having the
caching framework be aware these attributes were being added in.
Channel Manager then seems like the appropriate place to configure
these, say adding a 'Channel Attributes' page which would allow the
portal administrator to set name/value pairs to be set as attributes.
Deciding on some well known attribute names could be quite handy for
this purpose (channel type) but could also be extended to other things
such as css and javascript. The theme transform could be aware of the
cssLink attribute: <channel cssLink="/uPortal/channel/style.css"/> and
add all of the CSS links to the <head> of the rendered content.
That should solve your problem Gary, I'd like to hear what other devs
think of the idea. If it sounds good I can add it to the list for 3.0 RC2
-Eric
Gary Thompson wrote:
I am desiring to have icons associated with portlets, at least the
main ones (email, calendar, news, announcements, rss, etc.). Do you
know of any way to identify the portlet as one of these other than
the fname or title? The fname/title will be tricky without some ugly
parsing or standardization of naming.
It would be nice to have something like a "type" attribute on the
<channel> node for this, where an email portlet would register itself
as type=email, a calender portlet as type=calendar, etc. It could
also be done as a custom parameter in the portlet manager, but it
would obviously be preferable for the system to do it automatically.
Any thoughts?
Gary
--
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
