+1024 on all of this. Let me release 1.2b1 tonight and then commit
right after that... cool?
Rapha�l Luta wrote:
<snip>
> 4- Portlet state support
> ------------------------
>
> I wanted to implement portlet state support but came to the conclusion that
> it's not currently possible until we hav an ID available for referencing portlets.
>
> The issue is:
> If I put a minimize/maximize button in the portlet controlbar, I need to create
> an URL that will change the state of *this* portlet so I must pass on the URL
> an action parameter (Minimize, Maximize, etc...) and a portlet reference.
> Currently the portlet reference passed is the protlet name but this not good
> since the portlet name doesn't give enough information to retrieve the portlet
> with its associated context (skin, etc...) as it's readily apparent from
> the current maximize screen.
I know. I have been thinking about this too. The problem is that each
user can have different Portlet settings and be logged in at the same
time. Therefore we need to keep its state separate from the Portlet and
specific to the user. We really want the PortletControl/Skin/State info
stored in the User object with a reference to the Portlet.
That should work.
> 5 - Currently working on
> ------------------------
>
> Adding basic multi-access capability, see my response to kevin WAP proposal.
Cool.
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
