Comments on: Grails: alternate views for mobile (iPhone) clients http://adammonsen.com/post/548?utm_source=rss&utm_medium=rss&utm_campaign=grails-alternate-views-for-mobile-iphone-clients Tue, 03 Jan 2012 20:12:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Przemyslawhttp://adammonsen.com/post/548/comment-page-1#comment-12129 Przemyslaw Wed, 14 Jul 2010 19:18:21 +0000 http://adammonsen.com/?p=548#comment-12129 But in the meanwhile I discovered, that this only helps to resolve the layout gsp, not the view mapping convention.Probably you can use normal spring interceptors http://www.vaannila.com/spring/spring-interceptor.html That would be like your approach, but a little bit more DRY ( so without adding afterInterceptor for every controller).But I am still not sure about the best approach for this task. But in the meanwhile I discovered, that this only helps to resolve the layout gsp, not the view mapping convention.

Probably you can use normal spring interceptors http://www.vaannila.com/spring/spring-interceptor.html
That would be like your approach, but a little bit more DRY ( so without adding afterInterceptor for every controller).

But I am still not sure about the best approach for this task.

]]> By: adamhttp://adammonsen.com/post/548/comment-page-1#comment-12127 adam Wed, 14 Jul 2010 19:10:54 +0000 http://adammonsen.com/?p=548#comment-12127 Thanks for your comments, folks!@Przemyslaw - I fixed your HTML sample. I had to wrap it in <pre lang="html"></pre> Thanks for your comments, folks!

@Przemyslaw – I fixed your HTML sample. I had to wrap it in <pre lang=”html”></pre>

]]> By: Przemyslawhttp://adammonsen.com/post/548/comment-page-1#comment-12126 Przemyslaw Wed, 14 Jul 2010 12:37:56 +0000 http://adammonsen.com/?p=548#comment-12126 Thanks for this post and thanks Rich Kroll for the sitemesh decorator mapper hint.I like the sitemesh way, cause there is already a sitemesh AgentDecoratorMapper.So I simply extended the sitemesh.xml with<pre lang="html"> <decorator-mappers> <mapper class="com.opensymphony.module.sitemesh.mapper.AgentDecoratorMapper" > <param name="match.iPhone" value="mobile" /> </mapper> <mapper class="org.codehaus.groovy.grails.web.sitemesh.GrailsLayoutDecoratorMapper" /> </decorator-mappers> </pre>Thats all you have to do. Now sitemesh tries first to resolve your view-mobile.gsp and fallback to view.gsp if it does not find any view-mobile.gsp Thanks for this post and thanks Rich Kroll for the sitemesh decorator mapper hint.

I like the sitemesh way, cause there is already a sitemesh AgentDecoratorMapper.

So I simply extended the sitemesh.xml with

<decorator-mappers>
  <mapper class="com.opensymphony.module.sitemesh.mapper.AgentDecoratorMapper" >
    <param name="match.iPhone" value="mobile" />
  </mapper>
  <mapper class="org.codehaus.groovy.grails.web.sitemesh.GrailsLayoutDecoratorMapper" />
</decorator-mappers>

Thats all you have to do. Now sitemesh tries first to resolve your view-mobile.gsp and fallback to view.gsp if it does not find any view-mobile.gsp

]]> By: Mark Phttp://adammonsen.com/post/548/comment-page-1#comment-12125 Mark P Wed, 14 Jul 2010 02:15:13 +0000 http://adammonsen.com/?p=548#comment-12125 Very useful post! Thanks! I definitely would recommend creating a BaseController class and having your controllers extend that class. If you don't want to do that, and you are using the scaffolded controllers, you should look at the "grails install-templates" command and modify the controller template that is used there. Adding the method to that template will cause all newly generate controllers to have the method. Very useful post! Thanks! I definitely would recommend creating a BaseController class and having your controllers extend that class. If you don’t want to do that, and you are using the scaffolded controllers, you should look at the “grails install-templates” command and modify the controller template that is used there. Adding the method to that template will cause all newly generate controllers to have the method.

]]> By: Rich Krollhttp://adammonsen.com/post/548/comment-page-1#comment-12101 Rich Kroll Wed, 28 Apr 2010 14:22:29 +0000 http://adammonsen.com/?p=548#comment-12101 Nice post! I agree with the previous commenter, IMO sitemesh would be a better approach to this problem. You could add a MobileDecoratorMapper to the sitemesh.xml, and have the mapper inspect the user agent string to select different layouts. If you need different content displayed to mobile users, then your approach would be the preferable way to manage things. Great topic, thanks for sharing! Nice post! I agree with the previous commenter, IMO sitemesh would be a better approach to this problem. You could add a MobileDecoratorMapper to the sitemesh.xml, and have the mapper inspect the user agent string to select different layouts. If you need different content displayed to mobile users, then your approach would be the preferable way to manage things. Great topic, thanks for sharing!

]]> By: JThttp://adammonsen.com/post/548/comment-page-1#comment-12097 JT Sun, 25 Apr 2010 12:55:09 +0000 http://adammonsen.com/?p=548#comment-12097 Nice post. I wonder if you could have your controllers extend a base class with the closure.I've thought about this problem too. I haven't tried it yet - but was planning to use different sitemesh templates for mobile clients. In theory the views would be generic, and via sitemesh templates, different formatting (css includes) could be applied. The goal of my thinking is to apply a little DRY and avoid replication of code by not having diff GSPs for different clients. Nice post. I wonder if you could have your controllers extend a base class with the closure.

I’ve thought about this problem too. I haven’t tried it yet – but was planning to use different sitemesh templates for mobile clients. In theory the views would be generic, and via sitemesh templates, different formatting (css includes) could be applied. The goal of my thinking is to apply a little DRY and avoid replication of code by not having diff GSPs for different clients.

]]>