Re: Free wicket from component hierarchy hell

2010-11-05 Thread Igor Vaynberg
On Fri, Nov 5, 2010 at 11:39 AM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: Hi! its not about the list *items* its about the components you add to them onpopuateitem(item item) {  add(new label(name));  add(new label(email)); } wont work Why should it? Won't make it any

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Brian Topping
On Nov 5, 2010, at 3:01 PM, Martin Makundi wrote: Duh.. I think there can be _no_ excuse to not reduce manual work where it is really not needed. It's not like we are talking about airline autopilots here. So we don't need Wicket to work predictably and reliably all the time? MTBF is a

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Martin Makundi
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

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Martin Makundi
Duh.. I think there can be _no_ excuse to not reduce manual work where it is really not needed. It's not like we are talking about airline autopilots here. So we don't need Wicket to work predictably and reliably all the time? We are only proposing a new way of doing things faster with equal

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Igor Vaynberg
On Fri, Nov 5, 2010 at 1:07 PM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: 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

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Brian Topping
On Nov 5, 2010, at 4:15 PM, Martin Makundi wrote: We will provide a patch if possible. However, we might need some help onto our endevor. If it's not possible, why would you expect someone else to do it? Step up and make it happen! Avoid the misunderstandings, show what it should do! If

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Martin Makundi
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

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Martin Makundi
We will provide a patch if possible. However, we might need some help onto our endevor. If it's not possible, why would you expect someone else to do it? Step up and make it happen!  Avoid the misunderstandings, show what it should do! If you are demonstrating progress on something that

Re: Free wicket from component hierarchy hell

2010-11-05 Thread Jeremy Thomerson
On Sat, Nov 6, 2010 at 12:08 AM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: We will provide a patch if possible. However, we might need some help onto our endevor. If it's not possible, why would you expect someone else to do it? Step up and make it happen! Avoid the

Free wicket from component hierarchy hell

2010-11-04 Thread Martin Makundi
I propose Free Wicket from component-hierarchy hell We have discussd before that Wicket has unnecessary binding to wicket:id and component hierarchy [http://www.mail-archive.com/users@wicket.apache.org/msg53941.html]. I think I found a simple solution: wicket:id should be allowed to be on any

Re: Free wicket from component hierarchy hell

2010-11-04 Thread 7zark7
nice. On 11/4/10 1:13 PM, Martin Makundi wrote: I propose Free Wicket from component-hierarchy hell We have discussd before that Wicket has unnecessary binding to wicket:id and component hierarchy [http://www.mail-archive.com/users@wicket.apache.org/msg53941.html]. I think I found a simple

Re: Free wicket from component hierarchy hell

2010-11-04 Thread Jonathan Locke
-from-component-hierarchy-hell-tp3027705p3027881.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h

Re: Free wicket from component hierarchy hell

2010-11-04 Thread Martin Makundi
hierarchies to be hell, you probably aren't using Wicket right. Break things down into small reusable chunks using Panels and you will find everything gets much, much easier. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Free-wicket-from-component-hierarchy-hell

Re: Free wicket from component hierarchy hell

2010-11-04 Thread Martin Makundi
in context: http://apache-wicket.1842946.n4.nabble.com/Free-wicket-from-component-hierarchy-hell-tp3027705p3027881.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr

Re: Free wicket from component hierarchy hell

2010-11-04 Thread Jeremy Thomerson
On Thu, Nov 4, 2010 at 5:13 PM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: Can you see the matrix? ;) If you have: html form wicket:id=form input wicket:id=input .../ /form /html public class MyPage extends WebPage { public MyPage () { add(new

<    1   2   3