cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Freeman \(saurik\)" <>
Subject Re: [RT] Improving Sitemap and Flowscript
Date Sat, 23 Aug 2003 06:45:08 GMT

Could you describe what you mean by "above" and "sideways"? :) I'm not sure
what you are seeing, hehe. To me the "super-sitemap" (which is kind of what
this would be, as the main sitemap would be a subsitemap of it) is "above"
the sitemap, and cocoon.xconf is relatively unrelated and is therefor
"sideways" from the sitemap.

Also, to me at least there seems to be more of a "hackish" feeling in having
to different ways to setup components, one using xconf semantics, and one
using sitemap semantics. I'd rather have the base.xmap one where you can
have an extra file of just component definitions from a sitemap that are
overridden by the sitemap itself rather than putting that same thing in the
xconf... at least the layout of the file would be the same (but that still
seems hackish in the sense that this extra feature was added to support
what's pretty much a limited super-sitemap).

Jay Freeman (saurik)

----- Original Message -----
From: "Stefano Mazzocchi" <>
To: <>
Sent: Friday, August 22, 2003 12:39 PM
Subject: Re: [RT] Improving Sitemap and Flowscript

> > It makes more sense to me to use this already existing feature before
> > tacking on a new one. I've already started using this solution on my
> > websites and it seems to do the trick rather well (and also keep the
> > default
> > error handler in it so I don't need that in my sitemaps either).
> Sorry, but it looks hacky too me. Mostly because the components should
> be defined from "above" and not "sideways" (sorry, but that's how I
> visually perceive the thing).
> In short, I'd rather allow the sitemap to have components definitions
> somewhere else, either in cocoon.xconf or in the proposed
> components.xconf.
> --
> Stefano.

View raw message