If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Jivelite seems to be stuck at version 0.1.0. This fails installation of some applets which require something like "7.*". See eg. http://forums.slimdevices.com/showthread.php?t=110089. Could that version be bumped to something a bit more current?
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
Triode hard coded the JIVE_VERSION to 0.1.0 in jivelite during development because he used lua-jit which is not 100% syntax compatible with the lua 5.1 used in the jive based players.
Most of the 3rd party applets I've tried don't work with a lua-jit based jivelite.
It's the main reason I changed jivelite for picoreplayer to use the same lua 5.1 version as the squeezeplay players.
For picoreplayer I will change the version with an update to the extension, but that's going take a bit as I don't have my pcp build environments online.
In the meantime, here's how to temporarily override the version in pcp.
# Using vi add the line _G["jive"].JIVE_VERSION = "8.0.0" above the comment line before local io as shown in the patch below.
# Don't include the leading + sign(s).
sudo vi /home/tc/.jivelite/userpath/jive/JiveMain.lua
> Triode hard coded the JIVE_VERSION to 0.1.0 in jivelite during
> development because he used lua-jit which is not 100% syntax compatible
> with the lua 5.1 used in the jive based players.
Ah, I see. I wonder why he didn't opt for a custom target. That would
have given applet developers more flexibility.
Is the difference in Lua runtime worth the hassle?
Thanks for this insight!
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
> [22-11-07 07:24:24.1760] Slim::Plugin::Extensions::Plugin::_parseXML
> (501) searching http://ralph.irving.sdf.org/extensions/sigen.xml for
> type: applet target: jivelite version: 8.0.0
>
> Where would I see this? In the regular LMS logs? Somewhere else?
Enable logging for plugin.extensions.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
Thanks, just verified the work around you provided.
Applets now show and can be installed!
It is working but had a question
You wrote:
[22-11-07 07:24:24.1760] Slim::Plugin::Extensions::Plugin::_parseXML (501) searching http://ralph.irving.sdf.org/extensions/sigen.xml for type: applet target: jivelite version: 8.0.0
Where would I see this? In the regular LMS logs? Somewhere else?
I was just highlighting the fact that the jivelite version 8.0.0 is now reported. You won't see this exact log entry unless you have the above url setup in LMS.
Ah, I see. I wonder why he didn't opt for a custom target. That would
have given applet developers more flexibility.
Is the difference in Lua runtime worth the hassle?
Thanks for this insight!
lua-jit is "suppose" to be faster than standard lua, but I've never seen any significant speed improvements between lua-jit jivelite and lua 5.1 based jivelite.
The big hassle now would be replacing the default lua-jit interpreter for all jivelite builds with the lua 5.1.5 sources from squeezeplay.
The jivelite extension has been upgraded for picoreplayer 8.x, it now reports 8.0.0 as the version to LMS.
To update, navigate to the Tweaks page in the pcp webadmin and click the Update button in the Jivelite Setup section.
If you've installed the work around from post #2 you should delete the file /home/tc/.jivelite/userpath/jive/JiveMain.lua and backup the configuration to remove it before installed the new build.
Using the work around jivelite still reports the version as 0.1.0 in /var/log/jivelite.log
Code:
cat /var/log/jivelite.log
Using /dev/fb0 as frame buffer device.
Frame rate set to 22 frames per second.
Frame buffer color bit depth set to 32.
JiveLite 0.1.0
The updated extension reports the modified version and revision.
Code:
cat /var/log/jivelite.log
Using /dev/fb0 as frame buffer device.
Frame rate set to 22 frames per second.
Frame buffer color bit depth set to 32.
JiveLite 8.0.0-r208
Deleted the directory
/home/tc/.jivelite/userpath/jive
Rebooted
Ran the tweaks update
after another reboot,
plugins that should be showing as "available to be installed" are still there.
All that is left is to fix installing custom clock. Custom Clock was always instalable, but would try to install the one NOT meant for picoreplayer and fails, needs to be manually installed.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment