Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 70820 invoked from network); 30 Jun 2004 18:24:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Jun 2004 18:24:49 -0000 Received: (qmail 6280 invoked by uid 500); 30 Jun 2004 18:25:01 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 6009 invoked by uid 500); 30 Jun 2004 18:24:58 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 5946 invoked by uid 99); 30 Jun 2004 18:24:57 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [80.91.224.249] (HELO main.gmane.org) (80.91.224.249) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 30 Jun 2004 11:24:55 -0700 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Bfjl4-0003Vz-00 for ; Wed, 30 Jun 2004 20:24:35 +0200 Received: from 80.28.148.244 ([80.28.148.244]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jun 2004 20:24:34 +0200 Received: from thorsten by 80.28.148.244 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jun 2004 20:24:34 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@forrest.apache.org From: "Scherler, Thorsten" Subject: [RT] Skin-engine and new css-style skin Date: Wed, 30 Jun 2004 20:27:01 +0200 Lines: 69 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 80.28.148.244 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en Sender: news X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello devs, > The http://www.csszengarden.com/ would be an awesome template to use as start! I mean the plan can be to grep the html code and write the pipelines around that. In the end we would have the "original" cssgarden html with the project content and "whatever" css. > If we would let the user choose different standard html-output template like zengarden et al. and their css provider would make it easy to build a skin engine around that. Basicly what the user has to define is the css he wants to use for the output. That he can choose from over a hundert or thousand free designs out in the web. Afterwards we can make this css editable so the user can further customize the design. All information the skin engine would need are providers. * The skin-html-provider, that provides the base html output structure with css-tags * The skin-css-provider, that provides the base css-files At best that information is provided by hrefs that containing the dowload location. With that information the user can have a great design out of the box in defining in skinconf.xml:

To start with that we could acomplish the css-style skin http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-182 with the zengarden html reference site. That would be a good combination for the project.skin and its forrest.skins.descriptors. The project skin packages could be seen as skin distribution. Skin distribution can be seen as *.deb or *.rpm packages containing all needed files to install a skin. Like the skins we have now. The css-style skin should in the end become a zengardes-transformer that is able to read out difference files from different provider and apply that on the forrest documentation. WDYT? king regards thorsten -- Thorsten Scherler Spain <@mail>thorsten.at.apache.org <@cocoon-WIKI>http://wiki.cocoondev.org/Wiki.jsp?page=Scherler http://www.target-x.de http://www.acronymfinder.com "My task which I am trying to achieve is, by the power of the written word, [...] to make you see." *Joseph Conrad (1857-1924)*