Some time back I created a similar complicated grid structure and also submitted a rather rag-tag JIRA suggestion:
http://apache-wicket.1842946.n4.nabble.com/GridView-for-A-Symmetric-tables-issues-td2953859.html This post explains how I did it conceptually with pseudo code. Now, many months later here is what I feel: IF YOUR JAVASCRIPT SKILLS ARE GOOD :: If you can get away with producing JSON or any form of object notation and deliver that the the page, and have the Page decide via JQuery, Javascript + DHTML or some other pure client based solution then ...Do that! It gives you more maintainable and flexible code* and clear Server/Client abstraction. I've realized Table rendering is one of those things that are best left to client pages (if you are ok with a JavaScript solution). ...if not, you can scrape from my earlier work on that post. Its your choice , your neck! :) * For most reasons, ~~~ Browser specific JavaScript is a Pain and best avoided ~~~, but I've found table handling etc. one can write pretty much standard and consistent JavaScript that beats writing code server side. Again, it about your JavaScript skills Vs Wicket skills perhaps and a personal choice. I know many people will cringe at this comment but being honest about my frustrations and what works for me ;) ----- Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Complex-Grid-with-Wicket-tp3464266p3465107.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
