QUOTE(koan @ Aug 22 2007, 11:36 PM)
I must admit the filter buttons at the top confused me; I didn't realise that I had imported my file so I imported a few times before I realised that I had to add the language and then set the filter to show it.
You're right, it can be confusing (especially the first time). I plan to improve that but I wanted to make an early release. In the future, when importing a glossary, I will probably warn the user that the imported glossary contains words in more than 2 languages and/or when the languages are not among the selected Languages of Interest (in the Language Preferences).
This way, the user will be able to select the languages of the data he wants. And the Languages of Interest should be set automatically. About the Language Selectors (comboboxes at the top) I could set them automatically when the imported glossary is in 2 languages only but if it contains more than 2 languages, it's ambiguous and I better not touch it. I could set the Filter off though to make sure that we see the imported glossary in the TreeView.
Imagine for example that a medical glossary file has been translated in English, French, Spanish, and Italian and German, the user should be able to import only English, French and Spanish and omit Italian and German. Doing so should automatically select English, French and Spanish in the Languages of Interest Preferences if they were not already selected and the Filter should be turned Off.
Turning the Filter Off can have a confusing/surprising effect some times as you may not see the words in the right pane if the Language Selector is not properly set. This is a "feature" though as it allows a user to translate a glossary in a third or fourth language as described in the Online Help of the Glossary Manager.
So I went to edit my tree.xml but as the imported file is number.xml it was difficult to know which files to remove.
I understand, especially now that the glossary files are encoded in binary. Of course, this file should not normally be edited :-) You could have removed all the imported glossaries using red cross button in toMOTko's GUI and import it again.
When I switch the filter from English to Thai to Thai to English the Alt/Phon field is empty. I think this must be a bug ? It's the same for other languages.
I'm aware of this. Actually, it's not a bug but rather a choice I made. As you know, the screen's real estate of the Zaurus is quite limited so I chose to display only an Alt field for the Target Language. If I had more space, I would have an Alt field for both Source and Target Language. Practically, we don't need so much an Alt field for the Source Language as this language is usually your mother tongue or a language you're very proficient with. I preferred to spend the space on the Comments field. So the language of study should always be set in the right Language Selector in order to see the Alt field.
I think the filter buttons should not be required: if you tap a English to Japanese glossary the right listview should update to English to Japanese. It might be good if there is a button to switch direction though.
Your idea is good but doesn't work for a Glossary containing translations in more than 2 languages like the previous use case I mentioned before.
The Language Selectors (as I call them) and Filter are very convenient when you're learning more than one language. If you're just learning Japanese, for example, you should leave the Language Selectors to English, Japanese and Filter On, and never touch them again.
If you're learning more than one language, the Filter is very convenient as the TreeView can become quite loaded. If you take a look at my screenshots, you will see.
The Language Selectors are not intended to be used as directional selector but they can be used as such if you don't care about the Alt field. I admit it can be confusing to get used to it. The proper way to set the direction of study is by checking Revealing Orders options in the Quiz Preferences.
A glossary folder can have a description but a glossary file doesn't. Can I suggest adding a description field to each glossary ?
I will think about it. Once again, it's a trade-off I made. The space is limited and I thought it was not essential to have a description for a glossary. Maybe I should add a button besides the title which would invoke a dialog containing Description, Author, Date and other metadata. There is enough room to fit a TextField just over the list of words but I'm not sure if it will be pretty, especially in Portrait mode.
Also, when I export a glossary, it retains the id. If I redistribute the glossary, as for example my Thai glossary, what id should I set ?
It doesn't matter, the number will be ignored when importing the glossary. Instead, a new number will be generated in function of the state of the destination Glossary Manager. You can set it to "1".
Thanks a lot for your feedback. I will think about ways to improve the usability of the application.