One thing I've been thinking about is to have greater control over the "core" stack on a request-by-request basis, so that a single app can skin one way for a desktop browser, and skin another way (with changes to the "core" stack) for a mobile device (i.e., include JS & CSS from jQuery Mobile, for example).
On Mon, Nov 28, 2011 at 11:08 AM, SeleniuM <invest-in...@hotmail.com> wrote: > Also, you can always implement your own Chain of Command builder directly > implemented from Tapestry IOC. > The thing is to make parameteres width and height of your own web > application, and to make a selection when detected what device is > approaching your web applications using just variable HTTP_USER_AGENT. On > the knowledge of what device is detected, it parses values width and height > ( and many others if implemented so) to it. :) If you want, I will make some > code tips here. Cheers. > > P.S. Sorry on my English. > > ~SeleniuM > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-5-and-Mobile-tp5028089p5029782.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
