Re[2]: Selective PDF

[Ferdinand Soethe <sa...@soethe.net>]

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.


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.

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!).


--
Ferdinand Soethe

Re: Selective PDF

[Sean Wheller <se...@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