On Tue, 9 Nov 2010 10:05:39 -0500
James Carman <ja...@carmanconsulting.com> wrote:

> I think we need to try to put our heads together on this one.  I don't
> necessarily think this approach is the best, but I haven't really had
> a chance to wrap my head around it yet, frankly.  Do we really think
> this is that big of a problem that we need to change the whole
> paradigm of the framework to address it?  Perhaps you can create a new
> "container" component that does all of this stuff with some pre-render
> magic or something?  If you want to use it, you can.  If not, you
> don't have to.  So, if you're the type that likes this loosey goosey
> stuff, you basically "wrap" your pages with one of these things to
> enable this type of behavior.  I don't know.  This is just off the top
> of my head.  Still not done with my morning coffee.


If this can be done with a special-case container
(HighlyDangerousLiquidHierarchyMarkupContainer ;-) ), I wouldn't really
mind, as long as the impact on the rest of the framework is small.

I do not think it's worth it to change the whole framework around this
special case. Especially since things like enabling/disabling of
components based on their parents in the hierarchy don't seem to have
been addressed yet.


To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to