Re: Request for Feedback: Lokalize Glossary Tab

So hopefully this wall of text is helpful...

The tab is a great improvement over the previous state (where Ctrl+S didn't seem to work) and I'd still be reasonably happy if it stayed the way it is now. (I think its bugginess is mostly fixed?)

I'll note that Lokalize is more like an IDE or Blender: as a professional tool it needs to work first and be intuitive second (ideally both but this is how it should be prioritized if one needs to). Compare this to, say, a "consumer" application like Dolphin where if a feature is too unintuitive it might as well not exist.

Here's some of its issues I've encountered (all of which has been the case long before the change that put the glossary UI into a tab, that change was strictly an improvement):

- The source language term list and target language term list are implemented with a kind of bespoke widget where empty list entries are created beforehand and you double click on those entries to edit them. I don't think any other editable list works like this.

These should distinguish between having empty entries and not having entries.

It should also be possible to navigate with a keyboard.

- (Do not make n-to-n mappings harder to define! It'll definitely be tempting to do what Weblate does and "simplify" to 1-to-n ("just" define multiple entries) but that falls flat when you have real source text synonyms.)

- The manual "load from disk" button should just, not be a thing. I expect the glossary file to be autosaved, basically. The glossary feels like a (Lokalize-)project-wide database, so I shouldn't have to know to press Ctrl+S to save it.

- Ctrl+S to save the glossary is far better than the previous state though, which was that there's no save button and yet it's not saved automatically, so you had to save by closing the window and relying on the "are you sure?" popup. This is why I say the change that made the glossary UI a tab is strictly an improvement.

- There should be a way to define notes for either the whole entry or for individual target text terms to specify *how to* disambiguate them. Right now I have to put that into the main text, which works but means that the notes also gets inserted when I insert an entry.