Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 86998 invoked from network); 12 Jun 2005 22:11:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jun 2005 22:11:45 -0000 Received: (qmail 32483 invoked by uid 500); 12 Jun 2005 22:11:44 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 32427 invoked by uid 500); 12 Jun 2005 22:11:43 -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 32410 invoked by uid 99); 12 Jun 2005 22:11:43 -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 natsmtp00.rzone.de (HELO natsmtp00.rzone.de) (81.169.145.165) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 12 Jun 2005 15:11:42 -0700 Received: from 192.168.2.2 (181.Red-81-44-7.pooles.rima-tde.net [81.44.7.181]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j5CMBbER009630 for ; Mon, 13 Jun 2005 00:11:38 +0200 (MEST) Subject: Re: packaging views - how's it work? From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <42ACA7BB.30500@apache.org> References: <499888440506110809503eb0c1@mail.gmail.com> <42ACA7BB.30500@apache.org> Content-Type: text/plain Date: Mon, 13 Jun 2005 00:11:35 +0200 Message-Id: <1118614296.8055.41.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-12 at 22:23 +0100, Ross Gardler wrote: > Tim Williams wrote: > > I've taken my first look at views and this is great stuff. One thing > > I don't grasp is how they're "packaged" in the same way that skins > > are. It seems that if I create customizations in > > {project-dir}\src\documentation\resources\templates\*.fv or even > > FORREST_HOME\build\plugins\org.apache.forrest.plugin.output.viewHelper.xhtml\resources > > then I'd want to be able to offer those up to someone else in the same > > way that skins can be. Without a subdirectory for a each named view, > > I dont' understand how that happens? Would one just implement another > > viewXYZ / viewHelperXYZ plugin combo? > > From what I can see there is currently no packaging system for views. It is only a matter to implement it. ;-) Actually it will be quit simple as soon as I will experiment in the locationmap branch with the project.view.skin property in forrest.properties that we talk about the other day. > This is one of my must-haves. But I've not brought it up yet, because > I'm still only just starting to explore. > Just speak up. ;-) Like I said I will implement that in the loctionmap branch soon. > Remember, views are still in the whiteboard. They are quite incomplete > still (excellent, but incomplete). In terms of what they can do, totally agree. It is a prototype implementation till the day we make some major design refactoring decision of the "under the hood". It is *only* implemented in html. I would like a view package. ...I can go on and on. Bottom line IMO views will only leave the whiteboard till it do not depend on leather anymore, supports skin packages and I like to see another format as well supporting views. > After 0.7 is out, I would like to see > views and the locationmap stuff come into trunk almost immediately. I see this branch as well as integrating branch where locationmap and views will grow together and up. > Then > we can really get to grips with this brand new feature views) and old, > but unused feature (locationmap). > I had a quick look into it and I am working on the edit link example for lenya. Thanks for the awesome setup. :) > Ross -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)