Now that we have PortletSet(s) and panes, I think the current content generation
model is not really well-suited handling complex portlet layouts:
basically, the controller has to calculate the complete layout from the
individual portlets info, which can get quite hairy if we enable of lot of
skin and layout customizations in the portlet markup.
My proposal is to change the way the classes work together to better
mirror standard java.awt layout machanism.
Basically, I propose to base the layout process on the PortletSet which would
be modified to implement the Portlet interface.
The Controller would be associated to a PortletSet just like a LayoutManager
is associated to a Container in awt.
The PortletCntrol would be used for all Portlet (including PortletSet)
except that the default control for a PortletSet is transparent (but may be
caching...)
Advantages:
- more intuitive mechanism since it's closer to the well-known AWT layout
system
- more regular because if PortletSer are portlets, they can have their
PortletConfig too
- allows for simpler controller implementation, with XMLController,
PaneController, RowController and ColumnController, we can do nearly anything.
Comments ? Objections ?
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
