The only dependant spring class is org.springframework.web.filter.OncePerRequestFilter on the DeviceResolverRequestFilter which can be dropped, but does reduce the overhead of the filter.
Tablet defaults currently to mobile. Roller could be enhanced to use more rendering views (standard, mobile, tablet, etc) which does make managing the design easier (less csmess) but a whole lot more work/duplication. I guess why frameworks are switching to mobile first (Foundation, Bootstrap) which makes supporting multiple devices easier (based on viewport size rather than the actual device. Cheers Greg On 4 September 2014 18:43, Dave <snoopd...@gmail.com> wrote: > On Wed, Sep 3, 2014 at 3:14 AM, Greg Huber <gregh3...@gmail.com> wrote: > > > Checking the spring-mobile license it uses > > http://www.apache.org/licenses/LICENSE-2.0. > > > > So it looks ok to use, I will add a version which uses > > DeviceResolverRequestFilter and LiteDeviceResolver to determine the > browser > > type (also its easily maintained by spring! ;) ) and which we can easily > > switch to. > > > > I have added the code Committed revision 1622172. If it is OK I will > > update roller accordingly. > > > Hi Greg, > > Seems like a good idea, despite the fact that it means more Spring ;-) > > Does this solution or your design for using it require a theme author to > create a mobile, table-size and desktop version of every template or can an > author just choose to provide mobile and desktop? > > - Dave >
