Hi, I was trying to use WebClientInfo to get browser information on the server, and also extend the implementation in Wicket 6.x, reasons for me to extend Wicket's implementation are 1. Current implementation does not allow me to detect browser's touch api support 2. Wanted to use client side implementation library to detect browser features - like Modernizr.
On a brief look at the implementation I thought it is possible, but I ended up copy/pasting lot of code to workaround the problems I faced. Changing the implementation a bit might allow extension to Wicket's implementation. As changes are more, I created a quick start to show the changes required in Wicket's implementation. Please find the attached quick start. 1. I've copied and changed Wicket's implementation and they can be found in package "in.rakesh.example.wicket.page.browserinfo" 2. Extension to this implementation can be found under package "in.rakesh.example.wicket.page" Another problem I'd while doing these changes is regarding 'WebClientInfo' object creation. Current implementation creates instances in multiple places, making it difficult to have a subclass/extension to it. Adding a method to WebSession (WebSession#createClientInfo()), and using it to create instance gives lot of flexibility to extend it. In the attached quick start, I've added TODOs which need to be updated/corrected, if we've a method in WebSession. Can you please provide your views on this change. browserinfo.7z <http://apache-wicket.1842946.n4.nabble.com/file/n4673024/browserinfo.7z> Regards, Rakesh.A -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Regarding-Browser-Client-info-implementation-tp4673024.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
