Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 69439 invoked from network); 30 Nov 2004 16:54:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Nov 2004 16:54:59 -0000 Received: (qmail 45928 invoked by uid 500); 30 Nov 2004 16:54:59 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 45798 invoked by uid 500); 30 Nov 2004 16:54:58 -0000 Mailing-List: contact user-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: user@forrest.apache.org Delivered-To: mailing list user@forrest.apache.org Received: (qmail 45785 invoked by uid 99); 30 Nov 2004 16:54:58 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from natsmtp00.rzone.de (HELO natsmtp00.rzone.de) (81.169.145.165) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 30 Nov 2004 08:54:57 -0800 Received: from [192.168.0.107] (58.red-213-227-48.user.auna.net [213.227.48.58]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id iAUGsnPf027142 for ; Tue, 30 Nov 2004 17:54:50 +0100 (MET) Subject: Re: commercial Forrest skins? From: Thorsten Scherler To: forrest user In-Reply-To: References: Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1101833704.3835.63.camel@gci> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 30 Nov 2004 17:55:04 +0100 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N El mar, 30-11-2004 a las 15:16, peter.dykstra@donovandata.com escribi�: > > Thortsten Scherler wrote > > > > > Yeah, we will drop the concept of skins in 0.7 and introduce > > forrest:templates (a new templating language). > > > > While I love templates and so would applaud the introduction of any > new templating language, I am curious why this would replace skins. > Normally I would have thought these are different and complementary > concepts -- templates having more to do with the content and structure > of information (within pages, say, or of a navigational scheme) and > skins with, well, the skin. > *skin* produces placeholder for nuggets/fbits skelleton. *views* can use certain placeholder and add design information to the skin. *themes* add the final design implementation for the view in form of css-files. The forrest core will produce all existing nuggets/fbits as a contract skelleton without the actual implementation. Saying this means that we will only support *1* skin. The view and theming is then doing the presentation. The view will decide which content and functionality it will use and how it will be placed in graphical container. The view will let you as well implement your own contracts and override the default ones. This will produce an e.g. (because the same is true for fo,...) html-skelleton that is used by the theming. That makes it possible to develope different themes for a view. I do not like the expression "skin" anymore. It mixes to many concerns and if you are developing skins you will find yourself in the position to be designer and functionality provider. SOC!!! ;-) The language is called forrest:templates, because I was in the xsl:template mood and a forrest:view can contain several forrest:template's. ;-) like

> Has any more been written or is there an ongoing discussion about > this? I might like to participate, if there's that opportunity. > http://marc.theaimsgroup.com/?l=forrest-dev&w=2&r=1&s=forrest%3Atemplate&q=b Search as well for: leather, naming convention, fbits, nuggets, ... For more information just start a thread over in dev@f.a.o or answer to the above mentioned one. HTH -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)