On Fri, Nov 5, 2010 at 11:39 AM, Martin Makundi <mart...@koodaripalvelut.com> wrote:

right. this is the inconsistency i was talking about. sometimes you use straight add() and everything works, but sometimes you have to add to the proper component. this is going to cause headaches.

thank god no one spent millions of dollars designing IEEE1394 to compete against PCI and USB, otherwise it wouldve been a tremendous waste.

because without it you wouldnt be able to control visibility. your proposal does not add any *new* features.

because the designer delivers only part of the solution - the markup. the missing part is the behavior and to think that the behavior can be added in a completely orthogonal manner is foolish because behavior and markup are tightly coupled on matter whichever way you slice it. the best we can do is to make the coupling as easy and us unobtrusive as possible.

the designers are free to move pieces around as long as they do not cross wicket:id border, after all those borders are there for a reason - to attach some behavior.

a very simple example is that you have a container that should only be visible to admins of the application - this container contains sensitive fields that normal users should not see.

<div wicket:id="for-admins-only"> <div wicket:id="salary"></div> <!-- a bunch of other components --> </div>

now the developer takes the "salary" div and moves it out of the "for-admins-only" div. guess what, your *designer* has just opened a huge security hole in your application. who would use wicket if such things were so easily possible?

that is why we have no improvement and new feature requests in jira? because everyone is ok with the status quo? is it also the reason why we have not added anything new from 1.0 to 1.5, these have all been bug fix releases?

and as with many such things we have to calculate if eliminating redundancy is worth decreasing consistency.

if your web pages are trivial then why do you have hierarchy? you don thave to have hierarchy in java just because it is in markup...you dont have to model every single tag in wicket.

anywho, i think the fact that no one has really jumped in and sided with you is a good indication where this is going.

-igor