cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From leo leonid <>
Subject Re: [RT] Improving Views
Date Wed, 20 Aug 2003 09:07:57 GMT

On Mittwoch, August 20, 2003, at 09:07  Uhr, Carsten Ziegeler wrote:

> It's seems we have RT Time :)
> With views we have a nice sitemap feature that imho can be improved
> as well:
> One major disadvantage currently is that views are not inherited to
> subsitemaps, so I:
> ****
> Views should be inherited and can be extended/overwritten in 
> subsitemaps
> like any other component.
> ****
> Views are used for different scenarios; they provide a different ending
> of your pipeline. This is e.g. useful for debugging. Now by default
> the content view is enabled (for the main sitemap), and most times
> this view is not disabled when the application goes in production,
> so a user can invoke this view on deployed applications and see the
> output of the generator. But, this might contain sensitive data which 
> is
> not intended to be seen by the average user. So it makes sense to
> have a way to turn off views. But at the same time you might need
> views in different areas of your application, so:
> ****
> Views can have a default state: enabled or disabled that can be
> set in the sitemap:
> <map:views default="enabled"> (or disabled)
> This default can be overwritten on a map:pipeline base:
> <map:pipeline views="disabled"> (or enabled)
> In addition, you can allow only some views, like:
> <map:pipeline allow-views="x,z">
> ****
> And now you :)

I think it is not sufficient to have views that can be 
enabled/disabled. Sometimes other components depend on certain views 
(like the Lucene indexer) and so you can't disable. Maybe we need a 
sort of access restriction mechanism.


> Carsten
> Carsten Ziegeler
> Open Source Group, S&N AG

View raw message