Ah, sweet. Thanks for digging that up Jeremy.
Alec, since we were pressed for time, I piggybacked off your code to get
something working
@Override
protected void init() {
super.init();
/*
* Adds custom skin at the end of the header
*/
Hey guys, thanks for your responses. We're still using 1.4, it looks like it
will be a few months till we get to upgrade and use all the improvements
that have been made to resource handling in 1.5. In 1.4 it appears that you
cannot put a bucket in the header without things getting confused and
Hi Loren,
See whether you can find the mail mentioned in
https://cwiki.apache.org/confluence/display/WICKET/Resource+decoration
in the mail archives.
Jeremy attached the raw application in this mail thread and I
transformed it to proper wicket-example for 1.5
On Wed, Aug 3, 2011 at 6:36 PM,
Hi,
It is not documented by wicket:head contributes before
#renderHead(). This may change in the future so don't rely on it.
Better take a look at
http://wicketstuff.org/wicket/resourceaggregation application. There
you can see how resources are scored. This way you can setup
I had a similar case where I wanted to contribute header sections that
are written with renderString() last. I was not able to figure out all
that resource aggregation and bucketing stuff, so I wrote something
simpler. I would appreciate if somebody could review and comment on
this:
Under normal circumstances I would, but I don't have my css in a file. It
gets pulled from a database and stashed in the session. All the header
contributer classes and resource references assume there's a file somewhere
with this info. But in my case there is not.
And, even id I did stuff
put your css string from db in:
new StringBufferResourceStream().add(yourCssFromDB)
and then you can contribute to the header properly
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Issues-with-HeaderResponseContainerFilteringHeaderResponse-tp3678890p3685782
We're making our application skinable, but I'm having some trouble getting
user specified css into the right place in the header. We're working in a
distributed environment, so instead of saving their css in the file system
we're putting it in our database, and in order to get the cascade to work
To start, don't use a Label to contribute css. Use a header contributor.
That's what they're made for.
On 2011 7 19 13:22, Loren Cole loren.c...@gmail.com wrote:
We're making our application skinable, but I'm having some trouble getting
user specified css into the right place in the header.
