Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 25888 invoked from network); 5 Jun 2005 15:53:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Jun 2005 15:53:15 -0000 Received: (qmail 24117 invoked by uid 500); 5 Jun 2005 15:53:14 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 24067 invoked by uid 500); 5 Jun 2005 15:53:14 -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 List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 24047 invoked by uid 99); 5 Jun 2005 15:53:14 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from natnoddy.rzone.de (HELO natnoddy.rzone.de) (81.169.145.166) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 05 Jun 2005 08:53:13 -0700 Received: from 192.168.2.2 (145.Red-83-39-17.pooles.rima-tde.net [83.39.17.145]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j55FqwEB014810 for ; Sun, 5 Jun 2005 17:53:05 +0200 (MEST) Subject: Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n. From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <42A30018.3090609@apache.org> References: <1117896991.5068.91.camel@localhost.localdomain> <42A30018.3090609@apache.org> Content-Type: text/plain Date: Sun, 05 Jun 2005 17:52:38 +0200 Message-Id: <1117986758.5069.13.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sun, 2005-06-05 at 14:37 +0100, Ross Gardler wrote: > Thorsten Scherler wrote: > > hello devs, > > > > I just work on the i18n integration for pelt and crossed again the whys > > for using views. ;-) > > This mail makes for a pretty good piece of documentation. > :) It explains a wee bit better what I am doing to create the contracts. ;-) > A number of times over the last couple of weeks I have wanted to write a > mail asking you to write some user level documentation for views. You > see, I keep finding a few minutes to play with new stuff and Views is > one of the things I keep starting up and looking at. However, I never > get past looking at it. > > The reason is that I am thoroughly confused by the huge amount of RT's > that have been posted on this subject. It currently seems to me that > views are the solution to eveything. This makes it really difficult for > me to get started. So I was going to ask you to write a simple How-To on > creating a new contract, and then embedding it in my own site. > Yeah I can understand that. Did you see whiteboard/plugins/org.apache.forrest.plugin.output.viewHelper.xhtml/src/documentation/content/xdocs/index.xml I will extend that with this RT and write a howto. > As I say, I have resisted asking you to do this because I know I have > very little time for views until 0.7 is released, all my none payed for > time is currently spent on the 0.7 release. However, this RT is *almost* > the how to I want to see so perhaps I should be brave enough to ask. > :) > Is there any chance you can move the *user* relevant parts into a How-To > for views? It doesn't matter if it is not complete, just something that > will enable poor old me to get past the confusion of "views does > everything" to views does "this nice simple task like this". > Yeah I will extend as well the part of using basic forrest:views for writing view configs. > Maybe my poor little brain can catch up with you then :-) > I need as well to write some slides for the upcoming workshop about views. How did you do it again within forrest. ;-) > Thanks, > Ross salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)