Santiago Gala wrote:
>
> Raphaël Luta escribió:
> >
> > In case you did not notice it yet, in the new layout proposal we use a pull
> > methodology, which means jetspeed has *no way* to know how many and which
> > panes will be included in a given template. I don't think this presents a
> > major issue but you need to be aware of this...
> >
>
> Can you elaborate a little more?
>
> jetspeed has *no way* ---> a portlet code has *no way* ?
>
> or the layout code?
>
The pane selection process for a page is decided by the template
when it's parsed. You can't get a list of panes used by a page
without parsing the template which is something the Jetspeed engine
should probably never do.
In this model, Jetspeed is restricted to managing fragments of web pages
but can not (and should not) try to deal with the full template content.
So the layout engine won't know how many panes are included in a given
template and an individual portlet entry should probably not have access
to information beyond the scope of its current pane.
Of course, if you use the "degeneate" case of a single pane managing the
full-screen, you're actually in the same situation than today except that
the site administrator decided to use this model rather than a more
complex one with multiple pane mixed with non-jetspeed content in a single
template.
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
