Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
From: Sean Wheller <sean@inwords.co.za>
Reply-To: sean@inwords.co.za
Organization: In Words
To: dev@forrest.apache.org
Subject: Re: Selective PDF
Date: Mon, 15 Nov 2004 12:33:29 +0200
User-Agent: KMail/1.6.2
References: <200411141149.20071.sean@inwords.co.za>
 <200411142040.45330.sean@inwords.co.za> <115509299.20041115105828@soethe.net>
In-Reply-To: <115509299.20041115105828@soethe.net>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200411151233.29579.sean@inwords.co.za>

On Monday 15 November 2004 11:58, Ferdinand Soethe wrote:
> Backwards compatibility:
>
> I agree that we should not break existing sites without good reason.
>
> Yet improving flexibility, intuitiveness and logical structures should
> be good enough reasons especially while this is still a 0.x-version.
>
> In this case changes to existing sites would be rather small and
> easily be done in the time it takes to download the latest Forrest.

Agreed.

>
>
> Control of formats:
>
> I very much support Seans points on positively expressing goals as
> much as possible ("say what you want"). Also because it ensures, that
> later updates will not automatically add formats that the site-owner
> might not have wanted or expected in her site.
>
> Adding optional and inheritable(? not sure I'm using the correct word
> here) output-attributes to site.xml seems a very elegant and easy to
> understand way of combining flexibility and power with intuitiveness.

Agreed. Logical and understandable to the "average user." Site.xml is 
explained before sitemap and is the place where mots average users will focus 
attention.

>
> If it can coexist with expert tweaks to the sitemap, that would
> make it a perfect solution for me.
>
> It would also make it easy to implement when eventually somebody will go
> about creating a visual tree designer for site and tabs to further
> simplify editing those files.
>
> Btw: I propose making the default setting of the topmost site-element
> html and pdf (for clarity already explicitly set in new sites, but
> also used when attribute is not set!).

Agreed.


-- 
Sean Wheller
Technical Author
sean@inwords.co.za
http://www.inwords.co.za