Can you clarify what you mean by "Administrator"? In our world we have (at
least) three levels:
a) Administrator
b) Page/Portal Designer
c) End User
Your use of Administrator seems to map closest to our (a) Administrator. [see
definitions below]. When others have talked about it I have mapped to (b)
Page/Portal Designer. I can see how (a) might be done out of the "usage
interface". Its less obvious to me the value to do (b) outside the "usage
interface".
Definitions:
The Administrator is responsible for registering/adding portlets to the portal.
The administrator can configure portlets (change those configuration settings
that are modifiable). Changes made here effect all portlet instances created
here after.
The Page/Portal Designer is responsible for developing the initial structure of
the portal for a collection of end users. In doing so the Page/Portal Designer
is capable of modifying portlet settings. Portlet settings may effect either
portlet state or behaviors of a specific portlet instance (though its just as
easy to imagine that this instance is a template for future instances).
Commonly, these settings include the End user customization attributes allowing
the Page/Portal Designer to preset defaults for the End-Users.
End User is responsible for personalizing the Portal. In doing so they are
capable of personalizing portlets.
-Mike-
Alejandro Abdelnur wrote:
