Why use <g:textField /> in Grails?

grails gsp taglib
knorv picture knorv · Jun 28, 2009 · Viewed 12.5k times · Source

What is the reason to use g:textField in Grails if you're already familiar with standard HTML form tags?

If I understand correctly the following two markup alternatives are equivalent:

<input type="text" name="name" value="${params.name}" id="name" />
<g:textField name="name" value="${params.name}" />

Are there any circumstances under which using g:textField would add value? Am I missing something?

Answer

John Wagenleitner picture John Wagenleitner · Jun 29, 2009

The textField tag is provided as a convenience (slightly shorter than writing the HTML input) and is there to provide a full set of form tags. Personally I prefer to write as much plain HTML as possible in my Grails views and only tend to use the tags that really offer a benefit such as the form tag. I have not found an instance where using textField would have added any value outside of requiring a few less characters to type.

Related questions

Grails - Set "disabled" attribute name and value in GSP

I´m trying to do this without success: <g:textField title="${title}" ${disabled} /> I want to apply a disabled attribute, ONLY if the ${disabled} variable is TRUE. I don't want to use conditionals, because in other views I …

Read More
How do I call a Grails service from a gsp?

How can I invoke a service directly from a view? I'm trying with ${my.domain.service.method}, but it complains it can't find the property. And no, I don't want to use a controller because the view is a template.

Read More
gsp parameter passing from controller

how can i pass parameters to a groovy server page via a controller that are not an instance of a domain class ?

Read More