portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From raphael.l...@networks.groupvu.com
Subject Re: [PATCH] org.apache.jetspeed.portal.BasePortletSet.sortPortlet Set()
Date Thu, 04 Apr 2002 09:15:16 GMT
Glenn Golden wrote:
> The sorting must be done for customization, which the customizer *could*
> (and does) do.
> The sorting ALSO must be done just to display the tabs or menus!  So each
> request must have a properly layout sorted set of portlets (panes).

If I remember correctly these 2 codes, they don't sort the same objects:
- PortletSet sorts (or should sort) the Portlet children so that they follow
   either the explicit layout positioning or the implicit element ordering
- RowColumnControllerAction sorts Entry elements to make sure the customization
   actions (which are coded as "move up" or "move down" in the ordered list)
   are handled properly.

> Now, storing them sorted, or sorting them when read and saving them when
> sorted might help..

For PortletSet, it's kind of hopeless as the Portlet objects are dynmic and
constantly regenerated or cached.
For the PSML Entry, we can optimize somewhat by sorting Entries when loading
a page into memory but there's still an issue on customization because there's
no way a Portlets container object will be notified that the position attribute
of one of its child has been modified... thus a "defensive" approach during
customization is probably the best way to implement it, unless somebody
wants to add a callback or observer mechanism.
Raphael Luta - raphael.luta@networks.groupvu.com
Professional Services Manager
Vivendi Universal Networks - Paris

To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

View raw message