fields do
group :contact_info do
email_address :email_address, :login => true
first_name :string
middle_name :string
last_name :string
suffix :string
nickname :string
organization :string
address_line_1 :string
address_line_2 :string
city :string
state :state_abbr
zipcode :us_zip_code
country :string
end
group :some_fields_the_user_shouldnt_change do
magic_field :string
end
end
Then one could reference those group names somehow in, for instance,
only_changed? or none_changed? to simplify permissions checking. Rapid
might want to wrap a group in a named fieldset tag, to make a long
form look nicer, and so on.
Does this make sense to anybody else?
--Matt Jones
I like this too - I've definitely found that fields fall naturally
into groups in my apps
Tom