2 - here I have an simple consideration: framework should respect my
component design.
My view is different: we should respect the framework design. Don't fight
your tools, learn how to use them properly.
I agree. Let me say it in a different way:
framework should allow an simple component design like the one described
That said, I think that the model is the place where lazy instantiations
should occur. I mean, create your components with models that create their
'backend' on demand, like LoadableDetachableModel (without the 'detach'
stuff, maybe). Such model object should be pretty small in byte size, so it
shouldn't be a problem for memory consumption.
I agree too. But is up to me decide how and when my components will have
they models. I see it just as an fair wish.
Well, I'm not an expert in Wicket's internals, so it's just a guess. :)
I'm not too :) It was just a wish.Tank you for the opinion.
On Sun, Nov 1, 2009 at 12:25 PM, tetsuo ronald.tet...@gmail.com wrote:
2 - here I have an simple consideration: framework should respect my
component design.
My view is different: we should respect the framework design. Don't fight
your tools, learn how to use them properly.
That said, I think that the model is the place where lazy instantiations
should occur. I mean, create your components with models that create their
'backend' on demand, like LoadableDetachableModel (without the 'detach'
stuff, maybe). Such model object should be pretty small in byte size, so it
shouldn't be a problem for memory consumption.
Well, I'm not an expert in Wicket's internals, so it's just a guess. :)
--
Pedro Henrique Oliveira dos Santos
