Feedback about the "TeamSpeak 3 Package Installer"

[PotaBlava]

Hello,

Mac: Seems I forgot the file associations for *.ts3_xxx on Mac. Will fix that.

Mac: Any alternative for using the *.ts3_xxx meanwhile? How can a Mac user "launch" the file?

Linux: Due to various window managers with their own handling of file associations this is difficult. However, Linux users can start the package_installer binary directly and give the *.ts3_xxx file as parameter.

Well, it seems that Linux users are "bound" to work in manual mode. ;-)

This has inspired me a suggestion: Why not having a subdirectory for *.ts3_xxx package files and then "select and launch them" from the TS3 client directly, instead of using external file association?.

Greetings.

[dante696]

Mac needs to be fixed and then it will be possible to use it.

[ScP]

An issue with the add-on website: not all the suffixes related with the Package files are identified. Some (.ts3_addon, .ts3_style) appear with a button that says "Install Now" and others, case of ".ts3_translation", the button shows "Download".

Fixed. Thank you for reporting this.

[PeterS]

Mac: Seems I forgot the file associations for *.ts3_xxx on Mac. Will fix that.

I admit I violated the "think first, post later" rule here. Those file associations do exist on Mac, they are included in the Info.plist file inside the package_installer app bundle (which is bundled inside the TeamSpeak 3 client app bundle).

Now file associations on Mac work a bit different than on Windows. You have to start the application once so Mac OS X can add the file associations read from the bundles Info.plist. On Windows one would just add them to the registry and Windows knows without starting package_installer.exe.

Now, although the file associations already exist, they are never registered because nobody starts package_installer manually, as it's hidden inside the TeamSpeak bundle. One could open the TeamSpeak 3 app bundle manually in Finder, navigate to the package_installer bundle and start this once. Then *.ts3_xxx files are properly clickable on Mac. But that is, well, not a great way. I need to think about something better...

Sorry for the confusion.

[Screech]

I thought would be:

In the Application area of Options window in TS3 add a "Set installer package file association" button. Have that call the installer and pass a "null action" parameter.

Could also add a screen for this to the Setup Wizard with a check box to set installer package file association. Wizard runs on first run so that should help.

[Jordi]

Linux: Due to various window managers with their own handling of file associations this is difficult. However, Linux users can start the package_installer binary directly and give the *.ts3_xxx file as parameter.

In Linux, it works as you say, but it really is much easier to use .zip

[PeterS]

I found a way to properly register the package installer file associations on Mac OS X for release 3.0.3.

Until then, there is a workaround: Just move the TeamSpeak 3 Client application to another folder and back to the original place. Actually my original theory, that the registration takes place when starting the package installer, was wrong. It takes place when installing the application or moving it. Now I suppose that the problem occured when someone installed a TeamSpeak client from before the package installer and then updated it, so installation or moving never took place. But that should be solved with 3.0.3.

Thanks for the feedback, I would not have noticed as the file associations were already in place on my dev box.

[dante696]

I moved all post's from sticky TeamSpeak-3-Package-Installer thread into this section.

[Bouma]

Hi all, nice explanation for this Package Installer.
I have created 2 skins, and uploaded as .ZIP, since I can't make the installer work. A friend of mine did the package.ini at his place, and zip it, change to .ts3_style send to me. The launcher works (Tho the name doesn't show, so it install nothing). But so far, he was able to launch the installer.

I tried to unzip his version. Open the package.ini, put underscore for the name, and save it again. once more, can't run the installer, it gives me error again.

Failed to extract Add-on :
Failed to extract:<name>/package.ini

If it is something related to UTF-8, I have tried from Notepad, and Notepad ++, and still the same.

Any help will be great.
Thanks

[Koladrink]

At the end it Alwaya says failed! What can i do?

[Jordi]

Tho the name doesn't show, so it install nothing

With Notepad ++ is required to encode: UTF-8 without BOM

[PeterS]

Regarding translations, which was discussed on the first page of this thread, I made the package installer, updater and error reporter dynamically translatable. This will be included in 3.0.6 beta, so once that's out, please contact us (dante or me) to get access to empty translation files.

The Windows NSIS installer can be translated, but only at build, so adding dynamic translations won't work. If anyone wants to translate the NSIS installer, please contact me (whenever, no 3.0.6 beta client required for this).

[Jordi]

Regarding translations, which was discussed on the first page of this thread, I made the package installer, updater and error reporter dynamically translatable. This will be included in 3.0.6 beta, so once that's out, please contact us (dante or me) to get access to empty translation files.

Ok, we'll do it

[dante696]

You can contact me, when 3.0.6 (beta or stable) has been released.

[Mr. S]

Well, looks like a nice feature. But I there is no way to upload an installer for Win32 and another one for Win64. I can only upload one file, so I have to distribute it within a zip file (source for linux included).