| Weichun Qian 2005-02-25, 8:01 am |
| Hi Maik!
Thanks for your reply!
But how could I define unique names for controls and what apis could
I use to get them?
2005-2-25 16:07:19
Maik Weber <maikweber@de.ibm.com> wrote in message
<cvmmbp$4k9g$1@news.boulder.ibm.com>
> Hello Weichun,
>
> a page consists of rows and column containers. But there is also a
> container which is holding the portlet instance. This container is
> called control. The control is necessary because you can define a
skin
> for each portlet on a page. So, the skin information is combined
with
> the control which is holding the portlet. In a tree view it would
be
> like this:
>
> row
> |
> +-----+-------+
> | |
> colum column
> | |
> +---+---+ +--+---+
> | | | |
> control control control control
> | | | |
> portlet portlet portlet portlet
>
> This is a page containing two column and in each of the column are
two
> portlets.
>
> Each control like every object in Portal gets a unique id. However,
to
> be able to transfer configuration between several portal
installation
> and also in reason of human readability you can assign a unique
name to
> each object. That means you can also define a unique name for a
control.[vbcol=seagreen]
>
> Hope that helps.
>
> Maik
>
>
> Weichun Qian wrote:
portlet.[vbcol=seagreen]
page[vbcol=seagreen]
|