[09:02:26 CDT(-0500)] * JASIGLogBot (n=PircBot@mammoth.doit.wisc.edu) has joined ##uportal
[09:02:26 CDT(-0500)] * Topic is 'go uP3 go' set by EricDalquist on 2006-09-19 10:24:54 CDT(-0500)
[09:46:03 CDT(-0500)] * dmccallum (n=dmccallu@uni1.unicon.net) has joined ##uportal
[11:23:58 CDT(-0500)] * deuce_ (n=deuce@uni1.unicon.net) has joined ##uportal
[11:44:13 CDT(-0500)] * peterk_ (i=[U2FsdGV@66.226.77.81) has joined ##uportal
[11:56:43 CDT(-0500)] <EricDalquist> hey peterk_ got your email about the portlet mode/state parameters
[11:56:57 CDT(-0500)] <EricDalquist> the issue is with maximizing a portlet
[11:57:09 CDT(-0500)] <EricDalquist> I believe that is passed in as a XSLT parameter to the transformer
[11:58:00 CDT(-0500)] <EricDalquist> my 'solution' right now is the SaxFilter that looks at all the portlets being rendered has a reference to the TransformationFilter and gets the Transformer from it
[11:58:12 CDT(-0500)] <EricDalquist> I'm not sure this is a very valid solution though
[11:58:34 CDT(-0500)] <EricDalquist> and it definetly relies on the transform not starting until the endDocument event
[11:59:10 CDT(-0500)] <peterk_> right, that's not very good
[11:59:47 CDT(-0500)] <EricDalquist> the minimized and edit/help/view I can do via XML attributes in startElement
[11:59:50 CDT(-0500)] <peterk_> hmm ... so all this is to allow portlet to focus on itself by switching to a maximized state during the action processing?
[11:59:56 CDT(-0500)] <EricDalquist> but maximized is a bit of a problem
[12:00:28 CDT(-0500)] <EricDalquist> well right now the portlet changing it's state in any way doesn't affect the style sheet rendered UI
[12:00:54 CDT(-0500)] <EricDalquist> so the goal is to have a strong connection between the actuall WindowStates of things renderings in a user's layout and what the style sheets are doing
[12:01:06 CDT(-0500)] <peterk_> right, I understand.
[12:01:35 CDT(-0500)] <peterk_> but let's focus on that maximized state. How can it change ? 1. by incoming request param (i.e. user hits chrome button) or 2. by portlet changing its state
[12:01:36 CDT(-0500)] <peterk_> right?
[12:01:43 CDT(-0500)] <EricDalquist> yup
[12:01:44 CDT(-0500)] <peterk_> and 2. can only happen during action processing
[12:02:05 CDT(-0500)] <EricDalquist> and a portlet can change its state via a RenderUrl, ActionUrl or via a direct API call in processAction
[12:02:36 CDT(-0500)] <peterk_> well, url processing is done before rendering starts. so is action
[12:02:47 CDT(-0500)] <EricDalquist> ok
[12:02:48 CDT(-0500)] <peterk_> so we could take care of that state before we even get to the rendering pipeline
[12:03:20 CDT(-0500)] <EricDalquist> so we need to move the processing for maximized up in the chain for the up2 context
[12:03:51 CDT(-0500)] <EricDalquist> something that checks the state of the targeted portlet after all the URL/action processing and sets the appropriate structure parameter?
[12:04:31 CDT(-0500)] <peterk_> well, what you want to do is make sure that xslt param is updated whenever any portlet is switched to maximized mode (which can happen by three different ways we've listed)
Page Comparison
Manage space
Manage content
Integrations