Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Mathias (Author)

Pages: 1 ... 5 6 7 8 [9]
201
Beta Releases / Beta Build 814
« on: August 14, 2011, 12:03:27 »
Only minor fixes and additions has been added since last beta.
  • Full path will now be shown as a tooltip when hovering over a tab
  • Starting MultiCommander.exe -F=startup.ini, you can now defined multiple paths to be shown at startup.
  • File editor now support ${mcinstallpath} tag. So relative paths for the editor can now be entered.
  • 5 new MultiTags.
  • Fixed crash that happen if file search tab was closed shortly after a search was finished.
  • Device dropdown list lost some items if a USB device was removed.
  • User Commands how support single quote around commands. (See doc on Multi-Tags)
  • Fixed problem that quotes around filename when edit a file was lost in some situation.
  • 45+ Internal changes and fixes since v1.1.1 build 800.

202
Beta Releases / Beta Build 808
« on: August 03, 2011, 13:49:27 »
Mostly stability fixes for rare problem that have been reported from crash reports.

Also some minor new improvments
  • Menu bar can now be hidden. And then shown when user presses Alt key. (Like in IE9)
  • Device toolbar now also shows USB/Removable devices.
  • Multi Commander no longer locks the folder it is showing. So it is now possible to delete the folder you are currently showing from another program.
  • 11 new MultiScript function for getting selected/focus items from target/source view
  • 4 new MultiTags that will expand to the item in focus for source/target item. with fullpath or just name.
  • When creating checksums MD5/CRC32/SHA1. It is now possible to copy the calculated checksum to the clipboard using context menu on the item.
  • 30+ Internal changes and fixes since v1.1.1 build 800.

205
If you want to create translations of texts used Multi Commander you can do that in 2 ways. Using the built in language editor or by editing the language files manually using your favorite text editor.

Getting Started
All language files are stored as language packs. If you want to submit the changes you should not unpack them and edit them.
What you do is to start the built in language editor. This in Unpack all language files into the userdata location.
(C:\Users\<username>\AppData\Roaming\MultiCommander\UserData\Languages\)
After that you can edit the unpacked files. When done select Export/Send from the language editor to generate a new language pack.
The Generated language that is sent to be included/update in MC has a different structure then the file layout you see and the layout of the Language Pack.
So thats why you should use the built in Export/Send function. even if you edit the files externally.

Add Support for New Language
Open the Language Editor and in the language list select "Add New Language"
A dialog will be shown where you specify the name and properties of the language.
(Make sure that culture name code is provided, Without it the language will not work)

Add Support for New Language - Manually
Open the Language Editor so that the language files are unpack.
Then go to C:\Users\<username>\AppData\Roaming\MultiCommander\UserData\Languages\ and add en entry in the SupportedLanguages.xml file

Translate - Built in editor
Start the language editor by starting "Menu->Extensions->Language Editor"

You will see 3 dropdown lists. The first is Plugin type, second is Plugin/Extension, third is Language.
When you select a language other then English you will see the English text in italic and red color.
and when you writing a translation an item will turn black and bold. Bold indicate items that are changed but not saved.

The category name is just placeholders and do not need to be translated.

If an text item is not translated Multi Commander will fall back to the English file for that text item.

The language file will be save as "<AppOrPluginName>_lang_<culture code>.xml" ( eg. MultiCommander_lang_de.xml )

Not all text must be translated for it to work. When running Multi Commander with none-English language set. If it does not find a text string in the set language it will fall back and use the English for that string.

Translate - Alternative way
If you want to edit the files using an external editor. You first need to duplicate the english files.

When opening the language editor it will unpack the language file into C:\Users\<username>\AppData\Roaming\MultiCommander\UserData\Languages\
(or type ":gouserdata" in the command line field)

Then search the for all "*_lang.en.xml" file and then copy them.
Then rename them with the correct "culture name" code  (For example for german that would be *_lang_de.xml, for swedish it is *_lang_se.xml )
Then after that you can edit them using any text/xml editor.
Just make sure the file are save using UTF-8 is there are any special characters.

If you do not translate one text item. Then remove that item from your translated language files. Do not keep it in english in your translated file. Because MC will automatically pick up the english text if a translated item does not exists. Also you will easily find what text are missing translation later on if you open the built in language editor. Since all text that are missing translation is shown in red.

Generate Language Pack
To generate a language pack file that contains all the language files for a specific language, Press the "Export" button in the language editor. It will generate a language pack zip file with all the language file for the selected language. The files in the zip file are organized in a way to fit the build process of Multi Commander. So when sending in a Language pack to be included into the release. This format is preferred.

Submit Language Changes
If you create a new translation for Multi Commander we would be happy to included that into the installation of Multi Commander.
Even if the translation is not 100% complete we will accept it into the release.

First make sure the language you want to export/send is the selected one. Then press the Export/Send button.
You will now see an export dialog that allows for a couple of options on language pack format and how to submit it.
When submitting a language pack to be included into Multi Commander you must select one of the "Internal format ..." options.

Submit - Using File
If you want to the language pack in a file that you can send your self, Then select "Internal Format (Submit to developer using E-mail)"
You then send that file to me using email

Submit - Using HTTP
You can also have Multi Commander submit the language directly to the server. Then select "Internal Format (Submit to developer using HTTP)"
When submitting using HTTP you will also have to enter an Submit Key on the submit page that is shown when you press OK.

If you do not have an Submit key, Send me an e-mail and I will give you an personal submit key to use.

206
Beta Releases / Beta - Movie Information in Columns
« on: June 25, 2011, 14:15:38 »
I have gotten a lot request about adding a way to show movie information in columns for movie files.

Well. It is now possible. You can now show IMDB and/or RottenTomato movie information as column information.

Read more about it on the blog

You need at least build 770 to test this out.

Post all Questions and Issues about this feature here until it is available in the regular version.

207
Feature Requests and Suggestions / Read Before Posting
« on: May 01, 2011, 13:49:02 »
Use this forum for posting suggestions and feature requests that you would like to see in future version of Multi Commander.

If you have idea of feature please provide as much information as possible on how you think it should work.
The more information you provide the bigger chance it is that it can be added. Lots of the time it takes to create a new feature is to figure out how it should work.
And the more information you can provide the easier it will be to create.

208
Script / Read Before Posting
« on: May 01, 2011, 13:37:15 »
Use this forum for question about scripting in Mulit Commander or to share scripts that you have made.


209
Beta Releases / How to get beta releases
« on: April 24, 2011, 12:38:07 »
To make Multi Commander check for beta release at startup you need to activate that in its configuration

In the configuration for "Core Configuration" (located under the "Configuration" menu) there is a check box.
"Check for and download and update of beta version of available"

If this is checked Multi Commander will look for a new Beta Version at startup.

If you do not what to always check for beta version at startup you can also update to the latest beta version by running the MultiUpdate program separately. And in the settings for MultiUpdate there is a checkbox for "Download unstable beta if exists".


BUT.....

Beta release are to be considered unsafe. They contain feature and fixes that are not yet fully tested. So test them at your own risk


Pages: 1 ... 5 6 7 8 [9]