I’ve also launched a Theme competition with real prizes – please do enter a theme, closing date December 10th 2012!
This project is the culmination of many years of usage of Grails and thinking about the problems web developers face.
I need your help.
Note that there is a 1.0.M6 release now which is the recommended version.
The new p:text tag behaves very much like the Grails g:message tag.
The key difference is that the tag supports prefixing the message keys, and automatically applies a prefix based on the name of the plugin that supplied the GSP.
It’s been an odd day. It started with me starving because I had to fast all night for a blood test. Then I had to fix some horrible Java date calculation bugs in some client code. Next up (its not 9am yet) I had to go and catch a very feisty rabbit that was running across the A419 outside our house.
I also released a new plugin to accompany this, but not just for customers, called Rocks. Its pretty cool, and hints at some of the future ideas I have for the Grails development.
It was meant to be 1.1 but there was a bug that needed fixing immediately after releasing so 1.1.1 is where we’re at. This version is tested with Grails 1.3.7 and Grails 2.0 RC1 which is set to drop this weekend.
What’s new in this release of Resources?
Well aside from some useful bug fixes there’s a few interesting changes:
- If you forget to include r:layoutResources tags, you will get an error in the console. The error may or may not display in the browser currently depending on whether you used site mesh layouts or not. We may be able to improve this in future. This means that people who wondered where their JS code was disappearing to after installing Resources into a 2.0 app will now get an error telling them that they need to add r:layoutResources.
There are still some outstanding important bugs that I will endeavour to fix soon, as well as improving the error reporting on all fronts.