A correction: CFBundleName vs. FRApplianceName
So, I’ve mentioned on a number of occasions that the non-localized ‘CFBundleName’ showing up in the main menu can be alleviated through developers adding an FRApplianceName key to their Info.plist. I even explicitly pointed this out on the huge video tutorial — which is being downsized by my good friend (and also my hosting provider, at RGHosting) as I type this, ready to become the start of a proper podcast.
However, there needs to be a little change to this information. It’s technically true, except for a little bug in the implementation, due I would guess to the addition of some layers above the NSBundle API used to fetch the localized string value.
The code used by the BRApplianceManager looks something like this:
locName = [BRLocalizedStringManager localizedStringForKey: @"CFBundleName"
inFile: @"InfoPlist" fromBundle: bundle];
if ( locName != nil )
[dict setObject: locName forKey: @"FRApplianceName"];
The call into BRLocalizedStringManager on the first line can be effectively replaced with the following:
[NSBundle localizedStringForKey: @"CFBundleName"
inFile: @"InfoPlist"
fromBundle: bundle];
…which is in turn the API underlying the NSLocalizedString functions. And you know what those routines do when you haven’t created your localizations yet? That’s right, they return the key.
So, we end up with some code which contains a fallback, but that fallback will never actually be used, because the function called never returns nil.
Oops.
So, I have to apologize for giving out what essentially amounted to misinformation there. Hopefully when Apple delivers the YouTube plugin they can fix this bug too, so we can have a working locale-independent fallback for the plugin name.
While we’re at it, why not make it fall back on the plain ‘CFBundleName’ property?
shrug
June 1st, 2007 |
Ok Alan. Now it`s done.
Thanks for your support to me.
best regards
Michael
May 31st, 2007 |
ah ok, do this:
May 31st, 2007 |
Oh i think i give it up…this is what i get…
-bash-2.05b$ sudo mv CustomPlugin.frappliance CustomPlugin.deleteme
mv: rename CustomPlugin.frappliance to CustomPlugin.deleteme: Read-only file system
-bash-2.05b$
Michael
May 31st, 2007 |
Use sudo, like this:
When prompted for your password, give the frontrow user’s password.
May 31st, 2007 |
Sorry Alan…i cant rename this.
I am loged in at User Frontrow.
Any suggestion ?
May 31st, 2007 |
Hello again
Many Thanks to you. You are very fast to answer me.
Nice Weekend.
Michael
May 31st, 2007 |
The plugins are installed inside the Finder application on your Apple TV. The full path to the folder containing them is:
/System/Library/CoreServices/Finder.app/Contents/PlugIns
You can remove items from there manually, although I would suggest that to remove them you simply change the extensions from
.frapplianceto.deletemeand restart your Apple TV. That way the Loader will remove them after the reboot, and no errors are likely to occur due to files being deleted that are actually in use.Also, version 1.1 of Loader will have uninstallation/enable/disable support built-in, so you might choose to wait for that. It will probably be a couple of weeks away though.
May 31st, 2007 |
Hello Alan
Thanks. Your ATV Loader 1.06 looks Ok here.
Do you have any Tip to remove the other plugins ? Were can i find they ?
Michael
May 31st, 2007 |
There isn’t a simple way to handle it, I’m afraid. It requires creating the appropriate localization for the plugin in question. If that plugin is ATV Loader, then I’m happy to say that there is a German localization available in version 1.0.6, downloadable here or from your Apple TV if you already have version 1.0.5 installed. For other plugins, you’d need to contact the plugin developers directly to enquire about this.
May 31st, 2007 |
Hello
I am German and this is exact what i have on my Screen.
Is it possible to remove this from the Menue ? Uninstall this ?
Sorry for my bad enlisch..its only from school 35 years ago..
I hope you can help.
best regards
Michael