Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 18063 invoked by uid 500); 2 Jul 2002 11:47:41 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 18052 invoked from network); 2 Jul 2002 11:47:40 -0000 Message-ID: <3D2192FB.4090400@anyware-tech.com> Date: Tue, 02 Jul 2002 13:48:11 +0200 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510 X-Accept-Language: fr, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] Cocoon Blocks References: <3D1C9727.909EC507@apache.org> <3D1E2A97.5090608@anyware-tech.com> <3D1F3039.9421E716@apache.org> <3D20CBE9.4040900@anyware-tech.com> <3D218307.2AA07C08@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stefano Mazzocchi wrote: >Sylvain Wallez wrote: > > >>Ok. I understand your concerns. So what about, for this particular case, >>having 3 skins : a "super-skin" that's the one used by other blocks, >>that dispatches to concrete skins depending on the environment ? >> >> > >Hmmm, define "dispatches" before I can answer. > > Sorry, "delegates" should sound better. The idea is that the "super-skin" chooses the actual skin depending on the environment and delegates the actual work to that skin. Sylvain -- Sylvain Wallez Anyware Technologies Apache Cocoon http://www.anyware-tech.com mailto:sylvain@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org