OnDemand With 4OD Fix For PLi Based Images

Thanks digidude

opkg install python-beautifulsoup

with one l otherwise it won´t find it.

Quote from cazuela

Thanks digidude

Code

opkg install python-beautifulsoup

with one l otherwise it won´t find it.

added into the official OnDemand player 5 hrs ago.

https://github.com/oe-alliance/oe-alliance-plugins/commit/c6420c8449505288d390211fede872493f49f6f6

https://twitter.com/0penViX

Quote from pheonix

added into the official OnDemand player 5 hrs ago.

Code

https://github.com/oe-alliance/oe-alliance-plugins/commit/c6420c8449505288d390211fede872493f49f6f6

Code

https://twitter.com/0penViX

All credit to XBMC's Mossy again, and Mcquaim for incorporating it into OnDemand.

doesnt work on latest pli release

errors installing

no module named lxml

plus others

cannot install package beautiful soup
unknown package dnspython
unknown package python-lxml
unknown package python-simplejson
cannot install collected errors all the above

dreambox 800se openpli 4.0 gistrooms nightly build

will flash box & try again dont get it

Just downloaded all the needed files from the OE-A git and added the code to my original py files and I can confirm its working perfectly using OpenPli

It may work straight out of the box so to speak,although I didnt test that method,because past exprience has taught me that it usually doesnt.But when reading the new code,I cannot see anything that stands out,that will cause any GSOD's when using Pli

So well done ViX for adding the XBMC code for use in other Enigma2 images and not just solely for the ViX image.

Ian.

Will this get realised as a ipk file? Because I am well and truly lost lol

Quote from ian1095

Just downloaded all the needed files from the OE-A git and added the code to my original py files and I can confirm its working perfectly using OpenPli

It may work straight out of the box so to speak,although I didnt test that method,because past exprience has taught me that it usually doesnt.But when reading the new code,I cannot see anything that stands out,that will cause any GSOD's when using Pli

So well done ViX for adding the XBMC code for use in other Enigma2 images and not just solely for the ViX image.

Ian.

Display More

There never has been any code in this plugin to prevent it working on any image, that rumor was spread like all others by a few petty minded people who slate all things ViX yet use it to gain receiver sales for their own web based shop.

not strictly true buddy,after all your talking to the person who originally devixified the plugin so it ran on all other images.

agreed,there was never any code added to stop it running on other images,but the code was always written in such a way that only the vix images could utelise it.in other images it caused crashes.it was this code that had to be rewritten in a different manor,so as not to confuse none vix images and cause them to crash.

regardless of this,im applauding vix for not doing that this time and instead using standard code that all images understand.

Ian.

I dont wish to sound harsh here and I do fully understand that people have varying degrees of knowledge regarding their boxes and Enigma2,but how is anyone ever going to learn anything if they are always spoon fed ipk's that do everything for them ?

Enigma2 box owners should all at the very least, learn the basics such as manually installing a plugin and its dependencies.all the info and files are on this and other sites for you to read and learn to do these basic things yourself.

Ian.

Slight mod required to the original ViX code in the ui.py file to get the settings menu to display.More than likely just an oversight by the Vix coders.But its also possible that the Vix image doesnt need this ?

Navigate to line 126 and replace the existing line with this one.

self['actions']  = ActionMap(['MenuActions', 'SetupActions', 'TimerEditActions'], {

Ian.

Quote from ian1095

not strictly true buddy,after all your talking to the person who originally devixified the plugin so it ran on all other images.

agreed,there was never any code added to stop it running on other images,but the code was always written in such a way that only the vix images could utelise it.in other images it caused crashes.it was this code that had to be rewritten in a different manor,so as not to confuse none vix images and cause them to crash.

regardless of this,im applauding vix for not doing that this time and instead using standard code that all images understand.

Ian.

Display More

As i have said before the OE from which ViX is built is not the same as other images, and certainly not the same as Pli, Since ViX 3.0 we have been building and improving our own OE hence the creation of the OE-Alliance. we only work with our OE, so our plugins may not work with others.

Do you berate BH when a addition to their image does not work on others ?, no you dont so why constantly have a pop towards ViX ?. I dont want to rehash old arguments but i really do get tired of these silly rumors that ViX include code to prevent plugins from working on other images. after all the OE-Alliance it self consists of 16 member E2 dev team's and manufactures not just ViX.

Quote from ian1095

I dont wish to sound harsh here and I do fully understand that people have varying degrees of knowledge regarding their boxes and Enigma2,but how is anyone ever going to learn anything if they are always spoon fed ipk's that do everything for them ?

Enigma2 box owners should all at the very least, learn the basics such as manually installing a plugin and its dependencies.all the info and files are on this and other sites for you to read and learn to do these basic things yourself.

Ian.

Well at least that's one thing we agree on for a change.

Ok bud lets leave it at that as i too have no wish to get into another protracted argument over this again.the past is the past and lets keep it there.

Can you check your git and add the above code that ive added to it if its needed for the Vix image ?

if not,then its only other images that will require it.

Ian.

Quote from ian1095

agreed,there was never any code added to stop it running on other images,but the code was always written in such a way that only the vix images could utelise it.in other images it caused crashes.it was this code that had to be rewritten in a different manor,so as not to confuse none vix images and cause them to crash.

Ian.

That was never intentional but in a world where enigma2 it self has so many variations things like that were always going to happen and will always happen. no one coded is ever going to make a plugin that works with every single image under the sun, which is precisely why the code is in a public GIT environment so that people like you can adapt it and modify it for other images. I just take offence to the constant jibes insinuating we purposely made it to only work on our image.

I'm not saying you are the person who spreads such falsities but we both know the person(s) who do.