Bug 354265

Description Beat Schwarzentrub 2011-08-09 11:17:05 EDT

Build Identifier: 3.7.0.2011-Jun 2011

PROBLEM DESCRIPTION:
Here are several minor bugs or improvement propositions for the Scout NLS Editor. They are supposed to make the user's life easier, especially when building a new application from scratch (i.e. adding many new keys).

1. Auto generate key

If you add a new entry and begin typing in a text in a specific language, the key should be generated automatically on-the-fly. The resulting key should always be valid (e.g. remove or replace non-ascii characters, convert words to camel case, add "2", "3" etc. on name conflicts, ...). This should only happen, when at the beginning of editing a text, the key is still empty. Otherwise, the key should be left as it was.
Benefit: Entering new texts is quicker, especially if there are not many languages. Usually, the exact value of the key is not very important.

2. Copy new key to clipboard

Add a checkbox "Copy key to clipboard" to the "New entry" dialog. Unchecked by default.
Benefit: Usually, when entering a new key, it will be used somewhere in the code right after that. The checkbox makes it obsolete to select and copy the key manually to the clipboard.

3. Support for multi-line texts

It should be possible the add and edit multi-line texts. Currently, if you enter "a\nb", the text is saved as "a\\nb", i.e. the backlash is escaped, and not recognized as part of "\n" (newline character). The editor has to edit all Texts*.properties files manually.
Proposed solution: Either do not escape "\n" or use multi-line text fields. (The later may not work when managing a large number of languages.) Whatever the solution is, it must work also in the cell editor in the Scout NSL Editor view.
Benefit: Multi-line texts can be entered and edited using the Scout NLS Editor.

4. First column not editable

The first column in the Scout NLS Editor view (showing a "T" icon and the usage count of the particular key) should not be editable.
Benefit: Consistency.

5. Edit all languages at once (like "New Entry")

Besides the direct editing in the table (cell editor), it should be possible to (re-)view and edit all language texts of a key at once.
Proposed solution: Add a context menu "Edit" that opens and fills the same dialog as "New Entry".
Benefit: Changing a text in all languages at once will be easier, especially for longer texts.

6. Make dialogs behave like other Eclipse dialogs

Dialogs (e.g. "New Entry") should be resizable and they should remember the last size (like JDT's "Open Type" dialog).
Benefit: Users with large screens can make better use of the available space when editing large texts.

EVALUATION:
-

PROPOSED SOLUTION:
-

Reproducible: Always