Grails Platform UI – A Universal UI and Theming API to move Grails plugins forward

Grails Platform UI – A Universal UI and Theming API to move Grails plugins forward

Posted by: on Nov 27, 2012 | No Comments

I am very pleased, in fact relieved to have finally released a public 1.0 RC1 of the Platform UI plugin for Grails.

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.

Better i18n using the p:text tag from Grails Platform-Core

Posted by: on Aug 17, 2012 | No Comments

The Grails Platform Core plugin release 1.0.M3 added a new mechanism for rendering UI strings that is especially useful for plugins.

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.

Announcing commercial support and a new Grails plugin

Posted by: on Feb 28, 2012 | 2 Comments

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.

Anyone I eventually managed to launch Grailsrocks. Please take a look. Some great value commercial support plans for my Grails plugins.

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.


Resources 1.1(.1) plugin released

Posted by: on Oct 21, 2011 | 5 Comments

After a frantic 12 hours or so of coding and debugging, I managed to release version 1.1.1 of the Resources plugin for Grails today.

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:

  1. 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.
  2. There is now support for laying out arbitrary dispositions by passing a “disposition” to the r:layoutResources tag. This means you can position sets of resources wherever you like in the output, using multiple dispositions. Currently this is only relevant for JavaScript but in future we should be able to support images so that you can e.g. have a bunch of “preloaded” images that are hidden in the page somewhere.
  3. The integration with Grails 2.0 has been “finalized” now. The ResourceService has changed to a “grailsResourceProcessor” bean, and all g:javascript invocations result in called to r:require or r:script as necessary. The default layouts in 2.0 now use layoutResources and a default “application” module exists in new projects.

There are still some outstanding important bugs that I will endeavour to fix soon, as well as improving the error reporting on all fronts.