I'd like to announce a new blog for Grails: A Quick-Start Guide. You can find it at http://gquick.blogspot.com. In this blog, I'll continue to build on the example app in the book, and offer tips and techniques that didn't make it into the book.
The first post covers displaying an image property of a domain class in a GSP. In the GQuick example application, there is a Sponsor class that has a logo property. We never had a chance to show how to properly render that logo image to a page in the book.
If you've read the beta of GQuick and have anything else you would like to see discussed, post a comment here, on gquick.blogspot.com, or at the book forum at pragprog.com.
I'd also like to take this opportunity to thank the beta ebook readers. Your feedback has been a huge help!
Monday, August 17, 2009
Monday, August 3, 2009
In the August issue of GroovyMag, guest plugin-corner columnist Keith Cochran covers the new Clojure plugin by Jeff Brown. This plugin allows you to include Clojure source code in src/clj and then access that code in your Grails application. More details on the Clojure plugin can be found at http://grails.org/plugin/clojure.
A while back Vaclav Pech came out with a similar Grails plugin for Scala. This one hasn't been covered in GroovyMag... yet. Anyhow, you can find out more about this plugin at http://grails.org/plugin/scala.
So now in a Grails application you can have Groovy code (all over the place), Scala code in src/scala, and Clojure code in src/clj. That's pretty impressive! As I was marveling at these recent developments, I realized that Grails now supports 3 out of the four languages covered in Stu Halloway's paradigm-shifting blog series on Java.next (Groovy, Scala and Clojure - no JRuby... yet).
So unless something else comes along that as easily supports all four, I think we can safely call Grails the "Official Web Framework for Java.next".