[Koha-bugs] [Bug 15308] New: Suggested new interface for item type translation process

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15308

            Bug ID: 15308
           Summary: Suggested new interface for item type translation
                    process
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: I18N/L10N
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: oleonard at myacpl.org
        QA Contact: testopia at bugs.koha-community.org
                CC: frederic at tamil.fr

Created attachment 45418
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=45418&action=edit
Mockup of suggested changes

I find the new item type translation interface confusing, so I have attached a
screenshot showing an idea for how to change it.

We've got two competing modes in the current interface: A typical form for
adding new translations and a hidden inline editing system for existing
translations. I think we can combine the two:

- List all installed languages.
- Put an "Add" in rows for languages which lack a translation.
- Put an "Edit" link in rows for languages which have a translation.
- Use "Delete" text of the delete link for clarity and consistency.

The way I picture it, clicking the "Edit" link would move the focus to and
highlight the existing text in such a way to suggest that it is editable
(perhaps by imitating the style of a text input).

Clicking the "Add" link would move the focus to the "Empty" cell and set the
style of the cell in a way to suggest that it is editable.

I would further suggest that while an add or edit is being performed, the
corresponding add/edit link be replaced with a save button. Right now the user
has to both guess that the text is editable and guess that the changes will be
saved.

This is a good opportunity to establish a good usable pattern for using
contenteditable interactions so that they can be extended to more places in
Koha.

I would love to hear comments.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.