Open infoitservit opened 7 years ago
Do you mean the language/translate
page? Do you want to extend the source or translation column, or both?
With many active languages I don't see how a tab group will work, because the tabs won't fit in one row. Maybe a select works better.
I am still not sure how useful this could be.
I would like to improve the ux of your module. It would great to open an active record having each translatable attribute within a "tab group". Each tab represent available languages for translation, within fill in the translation for the source message exposed in the first tab.
What kind of strategy do you suppose is it better to use?
1) Load source message within the first tab 1.1) Rapidly scan for that message and if that one doesn't exist within language_source table, insert it. 2) Choose another tab for specific language 3) Use ::t helper method to expose the translated message (if exist). If not exist, show empty field. 4) Save the translation using a button. Should i use a new custom action to save it? Or could i use an existent action within your module?
Thanks