Bugzilla – Bug 13909
Installing third party applet on Baby and Touch
Last modified: 2011-11-06 23:22:13 UTC
Created attachment 5799 [details] Applet We have an applet from FrameChannel that seems to work ok on the Jive controller. We want to role that applet to Baby and Touch, but we are having some issue. After adding the XML link to Squeezebox server Plugins, from the controller going to Setting->Advanced->Applet Installer we can see the FrameChannel applet and we are able to install it. Connecting Baby and Touch to the same Squeezebox server and going to Setting->Advanced->Applet the applet is not available on those two devices. We thought Baby and Touch are build using the Jive software as their base OS. The XML link for adding the applet to SC is http://download.framechannel.com/Downloads/squeezebox/repo.xml Also attached are the meta file and applet file for a quick reference, there is a file to generate an ID (like our player pin) but no need for it because the ID can be generated from Framehannel’s website also. The applet attached using Squeezebox server 7.4 r28449 on Fedora 11.
Created attachment 5800 [details] Meta file
Created attachment 5801 [details] ID file
In the repo xml, try removing the the target clause or change it to be "jive|fab4|baby" The code is doing what was intended which is restricting the applet to the target device called "jive". It uses the device name for this, so these are the device names which the code uses for devices. Not sure if these are intended to change Richard? Simplest is probably to remove the target definition if you want it to work on all squeezeplay devices. You can see this filtering on the server using plugin.extensions logging: [09-09-08 21:09:32.3941] Slim::Plugin::Extensions::Plugin::_parseXML (396) entry FrameChannelPl does not match, wrong target [squeezeplay != jive]
Can I modify the XML file and try to access it locally? Would that work
Thanks, Adrian. Osama I tried this on my jive last night, and didn't seem to find anywhere to enter a player pin. How is that meant to work (or is the applet as yet unfinished?). Let me know if Adrian's suggestion works. I think you should be able to copy the xml and host it on a webserver locally to try the change.
Hi Richard, Step # 1 The below are the instructions as provided by Frame Channel, To access the new version, bring up the "squeezebox server". On the "Web control page" at the bottom right hand corner select "Settings". On the "Settings" panel, go to the "Plugins" tab. On the "Plugins" page, navigate to the bottom of the page and enter: http://download.framechannel.com/Downloads/squeezebox/repo.xml in the input boxes provided. Then make sure to hit the "Apply" button On the Duet controller ( or Squeeze play ) navigate to "settings->advanced->Applet Installer". Here you will see our application "FrameChannelPl[1.0->1.0]" press the center button on the controller ( or return key on the keboard if using "Squeeze play"), then hit the "install" menu entry. Step # 2 Once you are done with step # 1, wait for the Screensaver to kick-in. After that wait for about a minute or so the controller will give you an alphanumeric number, similar to our player pin for SN. To speed things up change your screen saver from the default setting to appear after 10 seconds. Step # 3 You need to go to http://www.framechannel.com/ and create an account. Once the account is created, on the top of the page click on "My Account". Click on "Frame Activation", enter the alphanumeric number you got on Step # 2 and click on "Save". As far as Adrian suggestion, I tried to fool the process by changing the XML file on my apache server as a local file after modifying target option that did not work. I guess the easiest thing to do is to contact Framechannel and ask them if they can modify the XML file for testing. I will look into that with Dan.
Richard is no longer available to us.
Hi, Is this FrameChannel project dead? I think with the launch of the Touch a FrameChannel screensaver (especially on that can work with the server off) would be popular. :)
Unassigned bugs cannot have a priority.