Yep, that change is worth it. Thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Devutils-sizeOf-tp4653827p4658055.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
t
> >> because of the DebugPanel. Is there an easy way to avoit that?
> >>
> >>
> >Can't you make this field 'transient' ?
> >This way it will be excluded in serialization process.
> >
> >
>
>
>
> --
> View this message
to avoit that?
>>
>>
>Can't you make this field 'transient' ?
>This way it will be excluded in serialization process.
>
>
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Devutils-sizeOf-tp4653827p4658051.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
;
> >> >It wouldn't be a problem if debug bar was the "last" component to be
> >> >rendered... I do agree information is misleading without detaching.
> >> >
> >> >On Tue, Nov 13, 2012 at 4:06 PM, Martin Grigorov
> >> <mgri
>It wouldn't be a problem if debug bar was the "last" component to be
>> >rendered... I do agree information is misleading without detaching.
>> >
>> >On Tue, Nov 13, 2012 at 4:06 PM, Martin Grigorov
>> <mgrigorov@>wrote:
>> >
>> >
> >> Only if you use the debug bar.
> >> Currently the showed size is misleading IMO.
>
>
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Devutils-sizeOf-tp4653827p4657764.html
> Sent from the Forum for Wicket Core develo
> Only if you use the debug bar.
>> Currently the showed size is misleading IMO.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Devutils-sizeOf-tp4653827p4657764.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
+1 Makes sense to me.
(If anyone else is wondering too: Component doesn't implement
IDetachable because if it did, we'd run in an infinite loop when models
reference components.)
Sven
On 11/13/2012 03:58 PM, Martin Grigorov wrote:
Hi,
The debug panel in wicket-devutils uses WicketObjects#s
Not sure whether this is explicitly documented but this is how this panel
should be used anyway.
On Tue, Nov 13, 2012 at 5:21 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> It wouldn't be a problem if debug bar was the "last" component to be
> rendered... I do agree information is
It wouldn't be a problem if debug bar was the "last" component to be
rendered... I do agree information is misleading without detaching.
On Tue, Nov 13, 2012 at 4:06 PM, Martin Grigorov wrote:
> Only if you use the debug bar.
> Currently the showed size is misleading IMO.
>
>
> On Tue, Nov 13, 2
Only if you use the debug bar.
Currently the showed size is misleading IMO.
On Tue, Nov 13, 2012 at 5:04 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> Wouldn't this make complex pages (e.g. with lots of LDMs) much more slow?
>
> On Tue, Nov 13, 2012 at 3:58 PM, Martin Grigorov >w
Wouldn't this make complex pages (e.g. with lots of LDMs) much more slow?
On Tue, Nov 13, 2012 at 3:58 PM, Martin Grigorov wrote:
> Hi,
>
> The debug panel in wicket-devutils uses WicketObjects#sizeOf() to calculate
> the size of the page and the session.
>
> The "problem" that I see is that it c
Hi,
The debug panel in wicket-devutils uses WicketObjects#sizeOf() to calculate
the size of the page and the session.
The "problem" that I see is that it calculates the size of the non-detached
object. I think what really matters is the size after detaching it, because
this is what is being saved
13 matches
Mail list logo
