The problem with that is in the current code-base I'm not sure there is a way to get at the portlet state early on enough.

-Eric

Jason Shao wrote:
On Nov 1, 2007, at 3:42 PM, Eric Dalquist wrote:

You would have to expose the layout parameters to CPortletAdapter in setRuntimeData *I think*. And then update the state handling code in setRuntimeData to look at the current layout parameters for the channel and figure out the correct state for the portlet then. Remember that this also has to work during action requests, when there is no layout state modification done even though the URL may have requested it since layout processing never occurs during an action request.

-Eric

I was actually thinking more along the lines of theme xform trickery where the controls in the portal chrome always reflect the portlet state as reported by the portlet, and we change the URLs in the XSL to actually send a windowstate change event to the portlet -- e.g. slam in a portletUrl construct.

Jason

--

Jason Shao
Application Developer
Rutgers University, Office of Instructional & Research Technology
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http://jay.shao.org



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to