Page Comparison

[08:03:37 EST(-0500)] * jayshao (n=jayshao@jayshao.oirt.rutgers.edu) has joined ##uportal
[08:10:59 EST(-0500)] * jayshao (n=jayshao@jayshao.oirt.rutgers.edu) has joined ##uportal
[08:44:51 EST(-0500)] * awills (n=awills@tp-wireless.its.yale.edu) has joined ##uportal
[09:07:39 EST(-0500)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined ##uportal
[09:47:58 EST(-0500)] * colinclark (n=atrcwrk2@142.150.154.101) has joined ##uportal
[10:16:41 EST(-0500)] * michelled (n=team@142.150.154.114) has joined ##uportal
[12:07:05 EST(-0500)] <EricDalquist> morning all
[12:07:43 EST(-0500)] <EricDalquist> anyone here want to talk uportal structure/theme parameters with me?
[12:21:34 EST(-0500)] <awills> I'm game what's up?
[12:22:26 EST(-0500)] <EricDalquist> just working on the pluto integration (taking a lot longer than I hoped it would, but I'm making good changes to the pipeline) and want to see if an idea for syncing portlet states/modes with the layout sounds sane
[12:22:46 EST(-0500)] <awills> ok
[12:23:18 EST(-0500)] <EricDalquist> so right now UserInstace.renderState() is pretty much the pipeline
[12:23:28 EST(-0500)] <awills> you mean WindowStates and PortletModes specifically? or other stateful data as well?
[12:23:59 EST(-0500)] <awills> um yes... there's a lot of code in there
[12:24:00 EST(-0500)] <EricDalquist> in it UserPreferencesManagers.processUserPreferencesParameters(request) is called to update the layout prefs that control min/max and such for channels in the layout
[12:24:17 EST(-0500)] <EricDalquist> in this case just PortletModes & WindowStates
[12:24:30 EST(-0500)] <awills> alright, i follow
[12:24:40 EST(-0500)] <EricDalquist> so this parsing method works for channels because channels don't have a stateful idea of min/max/etc
[12:24:47 EST(-0500)] <EricDalquist> those are just channel events they are notified of
[12:25:18 EST(-0500)] <awills> gotcha... i think
[12:25:22 EST(-0500)] <EricDalquist> with portlets it is a pain, since they are stateful (ie once a portlet switches to minimized we have to keep telling it that it is minimized until that changes)
[12:25:31 EST(-0500)] <awills> yeppers
[12:26:20 EST(-0500)] <EricDalquist> so I'm thinking this ... we add a portlet state data -> layout state data syncing step in the rendering pipeline
[12:26:45 EST(-0500)] <EricDalquist> so when a portlet is clicked on and requests MAXIMIZED in the URL, that gets parsed by the URL processing code I'm just finishing up
[12:26:55 EST(-0500)] <EricDalquist> when we get to rendering we do the following logic:
[12:27:16 EST(-0500)] <EricDalquist> if the request targets a portlet and is maximized we update the layout prefs correctly to maximize that channel element
[12:27:20 EST(-0500)] <EricDalquist> else
[12:27:39 EST(-0500)] <awills> so essentially those parameters get re-added before UserPreferencesManagers.processUserPreferencesParameters(request) for portlet modes & window states?