> one of the nice things of wicket is that java-code (programmer) and
> html-code (designer) are quite independent. only watching a wicket-java-file
> does a programmer deduce the structure and behaviour of the corresponding
> view, both things, without fully depending on inspecting html for
> understanding it all, in most cases.
>
> so, would your proposal tie programmers to requiring to watch the html-code
> to understand structure instead of a self-contained java-code. that's what
> old-fashioned frameworks do...

Quite the opposite in the general case. I cannot come up with an
example case that would require to watch the html code, more than we
must do already now.

**
Martin

>
> On Tue, Nov 9, 2010 at 5:08 PM, Martin Makundi <
> martin.maku...@koodaripalvelut.com> wrote:
>
>> >> @Carl-Erik
>> >> Reason why I haven't commented your "enabledInHierarchy" comment is
>> >> because it would not afect it in any way.
>> >>
>> >> I hope the proposition will be clear when we have it ready. We are
>> >> working on Igor's proposal.
>> >
>> > It will be interesting to see how you propose not affecting something
>> > that depends on the hierarchy when you remove the hierarchy.
>>
>> Sorry for miscommunicating.. we are not removing hierarcy. We are
>> trying to automatically nest the components according to the hierarchy
>> defined in markup.
>>
>> **
>> Martin
>>
>> >
>> > Carl-Eric
>> > www.wicketbuch.de
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>

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

Reply via email to