quote:
Originally posted by Mnjul
Well, now that the translator is essentially integrated into Messenger / Plus!, does it make sense that it loads the current language file along with the default language file as default when it's called?
Makes sense...
Though, this might better be as an option, so the user doesn't need to specify each time the actual file he wants to edit (in case the language he wants to edit is different than what is used in Plus!, eg: English is used and he is editing/working with the German one).
Maybe this could be integrated like this:
- everytime one of the two file selection change, store them in the registry and the next time the Translator is opened read them again (and thus load them again automatically -if they still exist of course-).
- the default values for these two fields (for the very first time the Translator is called) are the default translation file (English) and the translation used at that time in Plus!.
This makes that Mnjul's suggestion will be permormed, as well as:
remember what files where selected previously.
quote:
Originally posted by Mnjul
At least, the OpenFile dialogbox, shown when "Original file"'s browse button is clicked, should use "Lng_Default.ini" as default filter, instead of the current Lng_*.ini one 
That saves some time.
- Only when no file was previously selected/entered in the file editbox, aka it was empty. And not as filter, but as filename in the openfile dialog!
This makes that you still see all the ini files, but that the default translation file is already selected (all you need to do is press enter in that case and not also find and select the default file).
- If a file was entered in the file textbox, the openfile dialog should automatically jump to that directory and select that file...
Also, the openfile dialog should automatically "jump" to the translation files directory (if no file was previously entered in the file textbox; otherwise it should jump to that file's directory of course as suggested above).
- Another small addition in this, but worthwhile and can save some time, is to automatically detect what the extension was of the file entered in the file textbox. If it was an ini file, set the filter index to *.INI, if it was not an ini file, set it to *.*. This mimics a semi-intelligent behaviour and can save some clicks for the user. (aka: if the user did not entered an ini file in the file textbox before, you can assume he also wants to view all files instead of only the ini files next time he presses the browse button)...
Example of all this can be seen in my adaptation of the
Background Changer Script which automatically selects the previously entered file and automatically "chooses" the filter index according to what extension the previously entered file has. This is also the same behaviour that some big programs have (eg: PaintShopPro, PSP, ..)
quote:
Originally posted by Mnjul
I know there is currently no implementation about this in the scripting interface...but I still want to ask 
Is it possible that when I navigate in the listbox (where the entries are in) with keyboard
Time for Patchou to fix the event handler (aka the OnClick event should also fire when enter is pressed (possible for other controls too, didn't check), and an OnEventSelectionChanged or something should be added)
-----
Other suggestions:
1- Make the window resizeable (and the translation text boxes and file textboxes should resize with it; the rest stays fixed)
2- Add another option to select if the Plus! interface windows automatically re-read the translation elements each time (
AlwaysReloadInterfaces).
This together with Mnjul's suggestion for automatically loading the used translation (given that the "automatically load used translation" option is set) makes it that you almost have a real "Live"/"On the fly" translator.
3- To make the above even more "on the fly", show the Translator's menu also in chat windows, so the user doesn't need to open the contact list each time he wants to translate when he sees some wrong stuff in chat windows.
4-
(already suggested in MSN) make the file textboxes editable so the user can easly type the filename if he wants to instead of opening the openfile dialog.
5-
(already suggested in MSN) when translated text is changed, ask user to update file or discard it (with an option selectable like in the standalone app) maybe even making it so that when you quick/close the window, Translator asks you to update the file or not (aka: making the changes in a temp file first and only updating the real one if the user agrees... this also makes it possible to "undo" so to speak) (<== already on the todo list IIRC)
6- In the mean time, until you changed it to a treeview with icons and stuff, you can add a 1 character indication before (or after) topics and keys to indicate if they are already translated, included in default file but not yet translated, not included in default file, etc...
7- Basic information of both the "default" file and translating file would be nice to see. eg: language name and translation level.
/ 
