-Eric
Tim Carroll wrote:
well, you would request the portlet to render itself as an icon, such as you would ask it to render itself minimized or maximized. maybe it would help to put together a couple quick use cases for this... like rendering a list of subscribable portlets in a windows explorer like interface that would allow the user to select the way they would like to view the available portlets: 1. each portlet to render itself simply as the "icon" that is associated with it 2. similarly, you could have a "listitem" state that might render a small version of the icon with the title next to it, or 3. a "properties" state that is the icon - title, date created, portlet description, etc.... i'm thinking this functionality would make the icon state more multifunctional... it could be used to display a portlet as a stand-alone icon or something more complex like the windows explorer metaphor described above. ---- Original message ----Date: Mon, 21 Jan 2008 20:36:26 -0600From: Eric Dalquist <[EMAIL PROTECTED]> Subject: Re: [uportal-dev] Portlet type identifier To: [email protected]Not sure I follow how 'icon' is a PortletState (or for channels PortalEvent). Those are the state the channel/portlet is rendered in. I believe this is more a description of the published channel, like a title or category. -Eric Tim Carroll wrote: i brought this up in one of the sessions at the unconference. in my opinion, this is not unlike "minimize", so i believe that "icon" should be created as one of the custom portlet states. paul identified many other ideas for custom portlet states at that same meeting... ---- Original message ----Date: Mon, 21 Jan 2008 17:10:47 -0700From: Gary Thompson <[EMAIL PROTECTED]> Subject: [uportal-dev] Portlet type identifier To: [email protected]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________________smime.p7s (5k bytes)
smime.p7s
Description: S/MIME Cryptographic Signature
