Comments on: I’ve released another Grails plugin

By: sudhir

sudhir — Mon, 28 Mar 2011 07:37:00 +0000

Great plugin, discovered just recently, However the issue is, it doesn’t seem to support global custom field templates. Is there any way that would let me define custom templates for just once and then use it for all requests. I wouldn’t want to customize my template for each request.

Instead of customizing it in GSP, there could be a way to customize them in configuration, or just have partials(_textField.gsp) for each tag.

Answer my question of global templates

But, really helpful plugin.
Thanks

By: Marc Palmer

Marc Palmer — Tue, 24 Aug 2010 11:23:34 +0000

Shaun – did you follow the link to the plugin docs? they should answer most of your questions.

By: Shaun

Shaun — Sun, 22 Aug 2010 14:50:48 +0000

Marc – do you have any how-to docs? I just landed on this planet and am not sure how to use/implement your plugin. I think it will do what I need it to (manage default label property values?), but don’t know where to start.

Appreciate any help,
Shaun

By: Denis

Denis — Mon, 05 Oct 2009 21:25:02 +0000

Mark, thanks for response. I think the stack limit of 10 will be more than most needed. That’ll be a great feature.

Continuing working with bean-field I noticed that nested withBean are not supported. Is there any way I can display validation errors of domains that are in relationship (one-to-one, one-to-many) with modified bean? For example:

class DomainA {
static hasOne = [ b:DomainB ]
}

class DomainB {
String data
static constraints {
data(blank:false, inList:['first','second'])
}
}

And the form is here http://www.everfall.com/paste/id.php?u3po01mh5mby
I have no idea how to force error displaying in this case.

Thanks for the great plugin.

By: Marc Palmer

Marc Palmer — Tue, 29 Sep 2009 20:56:19 +0000

Sven you can easily do that with custom field templates that use with a code using a convention-based name using the bean + field name

By: Sven

Sven — Tue, 29 Sep 2009 13:58:26 +0000

Awesome, Marc, thanks for developing this – it’s amazingly useful and speeds my Grails development even further. One extra feature that I’m always adding manually and that would clearly be the icing on the cake: kind of a descriptive line. Cool Web startups usually place those directly below the input in small print, i.e. “We need this for whatever reason”. Optionally the template could even hide it below some mouseover-help-icon.

Thanks again for a great plugin!

By: Marc Palmer

Marc Palmer — Tue, 29 Sep 2009 09:33:40 +0000

Denis – that could be a godd idea. I will jira it but it needs some more thought, eg it could be very confusing as to what it will revert to, and do we maintain an unlimited stack?

I normally render GSP templates using g:render to set common field setups.

By: Denis

Denis — Mon, 28 Sep 2009 23:51:07 +0000

Hi Marc.
I wonder if you would add the ability to reset any field template to default ones or last used. It’ll need often when developer need to change field template only in the middle of the page or in GSP template which could appear in any part of GSP. I would suggest this:

Thanks for great plugin.

By: Marc Palmer

Marc Palmer — Sun, 20 Sep 2009 20:24:06 +0000

Hi Ted – yes this is already planned!

I just had to publish the code I had as a) otherwise it would never happened and b) other projects I have depend on it!

By: Ted Naleid

Ted Naleid — Sat, 19 Sep 2009 18:01:49 +0000

Looks cool Marc, thanks for putting this together.

A fellow coworker and I put something similar together at a previous workplace. The code was a little to specific to that company to release publicly unfortunately and I don’t have access to the source anymore.

One enhancement that we had that might be nice for your plugin is an iterator that iterates through all of the fields on the bean, with an order that can be either passed in, by default it could respect the “constraints” order.

Then you could pretty much replace the statically generated grails templates with a simple dynamic template that is customizable, but that automatically adjusts based on changes to the domain class.