I've written a custom ResourceNameIterator (to be used in a custom ResourceStreamLocator), that based on a user agent, can load specific HTMLs.
The concept is pretty simple, and what it does is to try loading a resource based on this names pattern: Page.<mobile>.<extension> Page.m.<extension> // generic mobile version Page.<extension> Where <mobile> can be 'android', 'iphone', 'ipad', 'blackberry' or whatever you want it to be. The only requirement is that the resource must have the same component structure as the Java class (the Wicket way). But of course, one can check few things to not render this or that component. Bruno Borges www.brunoborges.com.br +55 21 76727099 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld On Sun, Apr 3, 2011 at 11:52 AM, Martin Makundi < [email protected]> wrote: > http://www.thebuzzmedia.com/apache-wicket-powers-mobile-walmart-com/ > > 2011/4/3 Ayodeji Aladejebi <[email protected]>: > > Hi, > > I like to find out the compatibility of wicket on mobile phones? > especially > > the wicket javascript > > Have there been any publication or any project discussing wicket > > compatibility on Mobile Devices > > > > Thanks > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
