"Kevin A. Burton" wrote:
>
> oops... I meant <portal-structure> instead of <portlet-structure>
>
> :(
>
<portal-structure> is fine (don't know how cator handles hyphen though...).
We could also simply use <screen> since we're describing the content of a Turbine
screen.
In fact, it's feature I plan to implement (but not for 1.2): support in PSML for
multiple screen definition.
> "Kevin A. Burton" wrote:
> >
> > So any thoughts on this? It isn't "Portlets" anymore. It marks up the
> > controller, skins, entryRefs, panes, etc.
> >
Well, let's see:
entryRef = portlet
pane = portletSet = portlet
controller, control, skin, layout: elements inside the sets or entries...
All in all, we're still mainly describing Portlet(s)... :)
> > I am also working on a better user customization system and a
> > getPortletStructure API which returns the Castor PortletStructure object
> > would be cool.
> >
> > Thoughts?
Not so sure about that, at least not with the current version of Castor. The
Castor generated APIs are certainly very functional but not very OO since AFAIK
Castor doesn't support yet type inheritance. This makes using these APIs somewhat
painful as we can't use the features of the language. So I think we should avoid
exposing castor generated elements in the main Jetspeed APIs and keep those as
peers of the real Jetspeed elements. When Castor will be more mature maybe we will
be able to use Castor-generated API without losing to much in functionality.
--
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]
