Looks great to me this way.
Maybe checking as well if value.respond_to(is_a?) can be a plus, needs to check the ruby doc to make sure of the real need of it.

Hi Hukl,

Thanks a lot for your feedback.

I do agree it needs polishing, that's why kept the pending in the lighthouse ticket. Indeed it need to be merged with the actual master branch. I'll check your branch when I get a bit time, thanks a lot for it.

Great point with the value.is_a? I'll check what nicer check I can find to keep things robust.

Regarding the usage, I've already got successful cases where it add been proven to be extremely easy / comfortable to use. At least to me and an other Globalize2 user.

The whole process still require extra work, specially regarding the validation side. As explained in the lighthouse ticket. I've started work on this way as well and hope to get time to finish this as this could make translation more flexible and much easier to use when dealing with multiple locales. eg. an admin in X locales updating content in Y languages.

Still on the "when I get time" I'll pull a demo using my 2 other plugins that makes multiple translation really easy to handle, from view side as well as controller side.

I keep feeling like having an extra method to set multiple translations is making things more complicate when we can keep them simple. Anyway, I'll illustrate my point of view with the demo, that will speak much more.

Why to use an extra function like set_translations for setting multiple translations at once ? We could do this seamlessly when creating / updating the object.

eg: Post.create( { :title => { :en => "title", :fr => "titre" } } )

I've proposed such patch few month back http://globalize2.lighthouseapp.com/projects/15085/tickets/6-add-locale-parameter-to-setters#ticket-6-6

Looking for feedback,