Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 70939 invoked from network); 2 Aug 2005 02:41:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Aug 2005 02:41:44 -0000 Received: (qmail 94839 invoked by uid 500); 2 Aug 2005 02:41:44 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 94656 invoked by uid 500); 2 Aug 2005 02:41:43 -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 List-Id: Delivered-To: mailing list user@forrest.apache.org Received: (qmail 94642 invoked by uid 99); 2 Aug 2005 02:41:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2005 19:41:43 -0700 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (asf.osuosl.org: transitioning domain of webmaster@cfas.org does not designate 65.32.5.134 as permitted sender) Received: from [65.32.5.134] (HELO ms-smtp-04.tampabay.rr.com) (65.32.5.134) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2005 19:41:34 -0700 Received: from [192.168.0.203] (179.197.202.68.cfl.res.rr.com [68.202.197.179]) by ms-smtp-04.tampabay.rr.com (8.12.10/8.12.7) with ESMTP id j722fdah025190 for ; Mon, 1 Aug 2005 22:41:40 -0400 (EDT) Message-ID: <42EEDD5A.8030907@cfas.org> Date: Mon, 01 Aug 2005 22:41:30 -0400 From: CFAS Webmaster User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: user@forrest.apache.org Subject: Re: Help with new templates References: <42ED7699.1060200@cfas.org> <200507312317.20420.diwaker@apache.org> <42EEC320.6010507@cfas.org> <42EED497.8090401@cfas.org> In-Reply-To: <42EED497.8090401@cfas.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Diwaker, Got it... I needed to add this to CSS: #skinconf-toc-page { float: left; } Now on to why forrest never stops when generating a static site and why the logs get so darn big :> Thanks! -Paul CFAS Webmaster wrote: > Diwaker, > > In responding to my own post, I've made some progress. I've found > the correct xsl syntax to import a file and used that in the contract, > adjusting for the location of where forrest thinks it wants the file > vs. where it actually lives: > > > select="document('../../../cfas-new/src/documentation/content/xdocs/extra.xml')"> > > > + > |start extra-info > + > > + > |end extra-info > + > > > > > Firefox is telling me that
is still within
id='content'> but the HTML says otherwise. Unfortunately I'm still > having a problem with the CSS, or at least I think it's the CSS. I > have #rightbar declared as this: > > #rightbar { > float: right; > width: 100px; > background: #eae8e3; > border: thin dashed #565248; > margin-bottom: 10px; > } > > And I see the decorations correctly, as is the width and the float, > but Firefox is refusing to place it up by the header, instead stuffing > it below almost everything else. > > Any thoughts? > -Paul > > CFAS Webmaster wrote: > >> Diwaker, >> >> It does to some degree. I had found the foo.xml/foo.fv, default.fv >> mapping and that helps immensely. I think the part that I'm not >> understanding is the other bit. >> >> Should that content be in another file and included somehow? I see, >> but do not understand, how the leftbar is pieced together because >> forrest generates it, specifically with the nav-section contract. I >> just tried hacking the sitemap-contact.ft contract, calling it >> extra-info.ft and placing this into index.fv: >> >> >> >> >> >> >> >> >> >> >> >> The content bit comes from your default.fv and I've added the >> extra-info piece. The extra-info contract is a bit large and I don't >> know how much stuff is normally posted to the list as far as code >> goes. The core part of the template goes like this: >> >> > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> >> >> >> >> + >> |start extra-info >> + >> > select="div[@id='content']/div[@id='content-main']/*"/> >> + >> |end content-main >> + >> >> >> >> >> >> >> Where extra.xml is where I've stuffed the information for the third >> column. Does this look like a valid approach where I just have some >> syntax wrong, or have I completely missed what's supposed to be going >> on here? >> >> Thanks! >> -Paul >> >> Diwaker Gupta wrote: >> >>> On Sunday 31 July 2005 6:10 pm, CFAS Webmaster wrote: >>> >>> >>>> Is anyone would be willing to help me through the process of making >>>> this work properly? The original site that I'm trying to emulate is: >>>> http://www.cfas.org/, the new site is >>>> http://cfas-new.kronenpj.dyndns.org/. >>>> >>> >>> >>> >>> glad to help where I can :) >>> >>> >>> >>>> Essentially, I'd like the third column flush against the header. I >>>> think it'll work if I can convince Forrest to place that column in its >>>> own
. Unfortunately since it's part of the source >>>> file, it's part of
. I looked briefly at writing a >>>> new contract but I don't know enough about them to know if that's >>>> even a >>>> valid approach. >>>> >>> >>> >>> >>> Have you read the documentation on views? >>> http://forrest.apache.org/docs_0_80/howto/howto-view-dsl.html >>> >>> IIUC, all you need to do is put some of the content (like your >>> quicklinks and news items on the old site) within another >>> in the view file for the front page (most likely it >>> should be named index.fv) and thats it! >>> >>> Just in case you didn't know, you can specify per file as well as >>> per directory view configs. So, each page can have a different >>> layout, all pages in the same directory can have a different layout >>> and so on! >>> >>> The naming convention is that for a file named foo.xml, Forrest will >>> look for foo.fv, and then default.fv in the directory containing >>> foo.xml, and then the project wide default.fv and then finally the >>> default.fv that ships with views. >>> >>> HTH, >>> Diwaker >>> >>>