Le 31/07/2012 08:33, Emond Papegaaij a écrit :
But one more question though : why rendering wicket:head (in the markup
file) contributions before renderHead() (in the java file) contributions ?
With these things you just have to make a decision. Both orders are equally
valid. You use wicket:hea
On Monday 30 July 2012 18:18:46 Pierre Goiffon wrote:
> But one more question though : why rendering wicket:head (in the markup
> file) contributions before renderHead() (in the java file) contributions ?
> Seems to me that what you'll put in wicket:head will certainly be some
> king of static code
Hello,
> Wicket 6 final won't take long.
Good to know !
> I'm not sure about the Wicket 1.5 ordering, but in Wicket 6, header items are
> rendered child-first in the component hierarchy. For every component,
> is rendered first, followed by the header contributions in the
> Java code. Within a
Le 26/07/2012 20:54, Martin Grigorov a écrit :
>> Another question : can you confirm me there are no equivalent in Wicket
>> 1.5 for the Wicket 6 CssContentHeaderItem
>
> https://github.com/apache/wicket/blob/wicket-1.5.x/wicket-core/src/main/java/org/apache/wicket/markup/html/internal/HeaderRespon
On Thursday 26 July 2012 19:26:36 Pierre Goiffon wrote:
> Le 26/07/2012 10:29, Emond Papegaaij a écrit :
> > Second, I suggest you use Wicket 6, because consistent resource ordering
> > in
> > Wicket 1.5 is nearly impossible.
>
> Reading this made me smile : we use Wicket for a while now, and
> up
On Thu, Jul 26, 2012 at 8:26 PM, Pierre Goiffon
wrote:
> Le 26/07/2012 10:29, Emond Papegaaij a écrit :
>> Hi Pierre,
>
> Hi Edmond, thanks for your answer !
>
>> First of all, I strongly recommend you do not use a different
>> HeaderRenderStrategy.
>
> Yes, Martin made it very clear that ParentFi
Le 26/07/2012 10:29, Emond Papegaaij a écrit :
> Hi Pierre,
Hi Edmond, thanks for your answer !
> First of all, I strongly recommend you do not use a different
> HeaderRenderStrategy.
Yes, Martin made it very clear that ParentFirstHeaderRenderStrategy is
deprecated.
> Second, I suggest you use
Hi Pierre,
First of all, I strongly recommend you do not use a different
HeaderRenderStrategy. It is likely to get removed in future versions of Wicket
and might break libraries that depend on the normal HeaderRenderStrategy.
Second, I suggest you use Wicket 6, because consistent resource order
Hi Pierre,
First of all, I strongly recommend you do not use a different
HeaderRenderStrategy. It is likely to get removed in future versions of Wicket
and might break libraries that depend on the normal HeaderRenderStrategy.
Second, I suggest you use Wicket 6, because consistent resource order
I'll let Emond to answer you.
On Tue, Jul 24, 2012 at 5:24 PM, Pierre Goiffon
wrote:
> Hello !
>
> Le 22/07/2012 21:39, Martin Grigorov a écrit :
> For exemple I am just dealing with a problem in a page hierarchy like
> the one below :
> pageA : adds mycss.css using renderHead and a R
Hello !
Le 22/07/2012 21:39, Martin Grigorov a écrit :
For exemple I am just dealing with a problem in a page hierarchy like
the one below :
pageA : adds mycss.css using renderHead and a ResourceReference
pageB : adds 6 lines of css to change the behavior in wicket:head
pa
Hi,
On Tue, Jul 10, 2012 at 12:18 PM, Pierre Goiffon
wrote:
> >> We recently upgrade to Wicket 1.5. One of the major concern during that
> >> migration was to deal with the new order of the header render strategy.
> >> I see this is defined in AbstractHeaderRenderStrategy#get()
> (...)
> >> F
>> We recently upgrade to Wicket 1.5. One of the major concern during that
>> migration was to deal with the new order of the header render strategy.
>> I see this is defined in AbstractHeaderRenderStrategy#get()
(...)
>> For exemple I am just dealing with a problem in a page hierarchy like
>>
Hi Pierre,
There are some improvements in this area in Wicket 6.
Please read http://wicketinaction.com/2012/07/wicket-6-resource-management/
for more information. Pay attention to PriorityHeaderItem and setting
custom header item comparator. Header contributions from
are represented with org.apac
Hi,
We recently upgrade to Wicket 1.5. One of the major concern during that
migration was to deal with the new order of the header render strategy.
I see this is defined in AbstractHeaderRenderStrategy#get(), and reading
https://issues.apache.org/jira/browse/WICKET-4000 I understand the
reason
15 matches
Mail list logo
