Hallo,
I understand that potentially things could be overridden at a lower child. Although, you can have the same in the opposite direction. Same counts for bugs, but the beauty would be the flexibility I would say. On top of that, I am wondering how others use it than in combination with jQuery. Typically, jQuery has some element specific javascript and css, but rely on the common jQuery (file jqeury-min.js). If now all is driven from the lower childs you cannot place the common jQuery in the toplevel page from which all pages inherit and if a lower child adds the common jQuery you may end up with multiple (potentailly even different versions as well). Therefore, I am curious how most people use it with jQuery as I would say adding a single line in the html from which pages inherit from is way easier then putting a this in Java code. I understand the point of view that you may try to avoid a ParentFHRS, but disagree that core-developers make such a choice for others. So deprecating it sounds not the way to go for me, it reduces maybe the burden of maintaining it by core developers, but for sure also reduces the flexibility of using Wicket. Harrie [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
