> because the designer delivers only part of the solution - the markup. I meant software designer.
> <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? I did not propose that. If hierarchy is parsed from markup the visibility rules will remain same at runtime. >> I believe most are just acustomed to using it as it is. Even more people are >> accustomed using JSF. >> That feels more like an excuse to refrain from making Wicket even better. > > 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? I'm not standing in the way of this improvement ;) > anywho, i think the fact that no one has really jumped in and sided > with you is a good indication where this is going. Not so good indication ;) But pretty predictable ;) I think it's just fear of change. ** Martin >> 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
