This is a slippery slope and can easily become an excuse to do whatever it is that one wants an excuse to do. It's impossible to argue against supposed silent, anonymous individuals. They may think anything or have any problem whatsoever... whatever suits the argument at hand.
I think we're all listening if there are identifiable, real-world problems that need solving here. I just don't want more complexity (particularly a new concept) unless it's solving an actual identified problem or set of problems arising from reasonable coding practices. Chris Colman wrote: > > I think Eelco is right. It may be inaccurate to make assumptions about > how rare a use case might be based on what feedback you get on the > mailing list. Some people may find work arounds for a framework > problem/issue or they might just give up trying to do something that is > causes problems - possibly because they believe that they are doing > something wrong or are missing some essential points about how to use > the framework. This is exactly what I did at first with > page.getVariation() - I ended up overriding getVariation in the panels > instead of the pages as this seemed to work without getting errors. This > got me by for a while. > -- View this message in context: http://www.nabble.com/Lifecycle-issue-with-getVariation-tf3476789.html#a9783309 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
