Re: Leave out a HeaderItem?

2013-01-31 Thread Martin Grigorov
Hi, You stated that you want to avoid global/application scoped solutions. That's why I didn't mention resource filtering. Now I see that you don't want replacements .. Use custom IHeaderResponseDecorator that has public IHeaderResponse decorate(final IHeaderResponse response) { return ne

Re: Leave out a HeaderItem?

2013-01-31 Thread Stefan Renz
Hi Martin, thanks for the suggestion, but I was wondering if there was anything more "global" than that. The story is not quite as simple as I suggested, but basically it's not the ChildPage that decides to exclude the stylesheet, but rather a Border that may be present on the ChildPage, or not.

Re: Leave out a HeaderItem?

2013-01-31 Thread Martin Grigorov
Hi, class BasePage { void renderHead(IHeaderResponse ihr) { String externalUrl = getExternalResourceUrl(); if (Strings.isEmpty() == false) { ihr.render(CssHaderItem.forUrl(externalUrl)); } } protected String getExternalResourceUrl() { ... } } class ChildPage extends Base

Leave out a HeaderItem?

2013-01-31 Thread Stefan Renz
Hi, I'm wondering how I could conditionally leave out or replace a CSSHeaderItem that is usually included. Application-wide resource replacement is not an option. Here's the scenario: BasePage adds a Stylesheet by rendering a URL (it's external to the Wicket application). A component in Concrete