Glenn R. Golden wrote: > Still More... > > I think that the idea of checking for the presence of the "template" > in the request might work to be the criteria of when NOT to > maximize... but I don't like it. I might work, but it's not based on > any solid *reasons*! > > So, here's another approach. Lets "fix" maximize. > > Right now, maximize is handled in the session validator. Maximize is > really a property of the portal page, for the user (session) viewing > it. For this user, now it's maximized, now we show the entire page, > etc. The page session state is modified by the Maxmize and Restore > actions. > > The display of the portal page is handled by our "home" screen > template. I propose that we modify home.vm so that it detects the > presence of maximized in the page's session state. If not there, it > does the entire page, or pane. If there, it does just that portlet. > This merges the maximize template with the home template. > > This is a better solution, because when we send in a request and that > request ends up using the "home" (default) screen, then maximize comes > into play. If we send in a request that ends up using a different > screen / layout (such as will be for the panel's iframes using > "content"), then the maximize naturally doesn't come into play, since > that's a feature of the "home" screen. > > Both maximize and home are very simple vm files, and the combined > version should be very clean. > > What say you all? > +1 to merge Home and Maximize.
-- Rapha�l Luta - [EMAIL PROTECTED] Professional Services Manager Vivendi Universal Networks - Paris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
