Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@apache.org Received: (qmail 37782 invoked from network); 7 May 2002 06:59:36 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 May 2002 06:59:36 -0000 Received: (qmail 22381 invoked by uid 97); 7 May 2002 06:59:46 -0000 Delivered-To: qmlist-jakarta-archive-jetspeed-dev@jakarta.apache.org Received: (qmail 22323 invoked by uid 97); 7 May 2002 06:59:45 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 22299 invoked by uid 98); 7 May 2002 06:59:44 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3CD779E6.1060105@networks.groupvu.com> Date: Tue, 07 May 2002 08:53:26 +0200 From: raphael.luta@networks.groupvu.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: fr, en MIME-Version: 1.0 To: Jetspeed Developers List Subject: Re: panels in portlets conflict with Maximize References: <6C95A68A-6157-11D6-A0D1-0003937AD88E@umich.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 - raphael.luta@networks.groupvu.com Professional Services Manager Vivendi Universal Networks - Paris -- To unsubscribe, e-mail: For additional commands, e-mail: