On Sat, Nov 19, 2011 at 4:52 PM, jlazeraski <supreme_java_gur...@yahoo.com> wrote: > Another area I am not keen with at all with wicket which is mentioned is > having to build the object tree code the same way the html page is. With > element Ids, I am a little confused as to why we cant simply insert the > component using the element id and let wicket figure out where to stick it > on the page. To me, as it scans the html page for wicket ids, it should be > able to pluck wicket component/objects from a Map using the same ID and put > it where it needs to be.
ironically, i already posted a link to the discussion thread on how this will be fixed in this thread :) here it is: http://markmail.org/message/imgf6a2heszaptbp that thread is a good read that explains why a simple map of id->component wont do. > This is one of the areas I have had some trouble > getting right. this is a growing pain, after using Wicket for two weeks it will become second nature... > Otherwise, I love the idea of Wicket. I've often thought of making my own > template framework like how I describe above.. stateless on the server side > (no object model in memory), modular components that can be reused on any > page, without all the JSP scriplet nightmares. if you try to build it, eventually you will end up with Wicket :) -igor > > Look forward to any replies. Thanks all. > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4087666.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...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
