On Mon, 2005-08-15 at 12:16, Lance Lavandowska wrote: > Make it such that the PageServlet (or whatever it's called now) looks > for the presence of $decorator or the existence of a _decorator Page. > In either case it applies the decorator. If neither of those is true, > then it does not. The new shared templates should *not* have a > _decorator. In the absence of shared templates, for those sites > already created, I think this should address the issue.
this *is* how it works now. the problem is as you said, *if* the "_decorator" template exists then it is *always* used. that means that if i use a decorator and i define a template called local.css and want to use it as a css file i'm screwed because my decorator is applied even when it shouldn't be. > > It also allows for advanced usage; those few brave Roller-hackers out > there can still create decorators and make use of them by declaring > the $decorator value in their pages. i am fine with allowing true power users to manually set the $decorator variable to point to alternate decorators. > > We can make it easier for users by eliminating this option (to all > appearances, but maintaining backward compatibility). i disagree. i don't think we can hide this feature and still make it truly useful. if a decorator is going to be selectively applied to only chosen templates then this must be done via the UI. -- Allen
