I am now up to the select channels page ;)
I keep saying miah, I am plodding along slowly. It is a mega complex plugin this.
If I was just doing xtream codes bouquets its dead easy, but I also allow any type of external playlists and local playlists. So the code has to be written 3 times for each with totally different code depending on the playlist type.
Which is a mega ball-ache.
depending on your box, your remote should have a radio button.
if not try pressing the tv button to toggle tv/radio
I was just intrigued by this plugin as someone had asked me to add it into my skins. Although my skins are not really designed to add in extra elements.
My reply was to do it themselves. But as I have never tried it myself, thought I would have a play and see what it was doing.
I just tweaked things as I was having a play around with it.
As you know biko I am a busy man, and I got my own plugins to tweak. Not enough minutes in the day for me to be spending much time on other projects.
Comparing openvix to openatv
openvix set all the values with self.guiObject.set...
def secondfont(self, value):
self.guiObject.setSecondFont(parseFont(value, self.scaleTuple))openatv have a right mixture going on, some use self.guiObject, everything marked as legacy doesn't have self.guiObject and lots of others don't use the guiObject at all?
def secondFont(self, value):
self.valueFont(value)
attribDeprecationWarning("secondFont", "valueFont")
def secondfont(self, value): # This legacy definition uses an inconsistent name, use 'secondFont' instead!
self.valueFont(value)
attribDeprecationWarning("secondfont", "valueFont")I have no idea what they are trying to do. But looking at skin.py it seems all over the place.
settings pages used to have 2 skin fonts.
font="Regular;32" secondfont="Regular;32"
Maybe they changed this now.
I will install latest tonight or tomorrow and see what exactly they doing
As digiteng has mentioned. His official release is on post 1.
See first post of how and where to use.
This is just my experiments with his code.
Fully linted the file.
Your code checked for internet connection, but didn't actually stop if no internet.
Your applyskin function is only reading data, so no need to apply attribs. Find source isn't the best way of finding the source component.
Like others have done I have used components.sources libraries to check.
I have wrote in a set of valid images sizes that will be used to download poster based on the user skin width size.
(185, 200, 300, 342, 500)
Size values in skin can now be anything if still 1:1.5 ratio and will pick nearest valid size image to download.
I only create the event name, and serviceref once, then these arguments are passed to all other functions. So no repeating code.
File names of posters are cleaned to prevent illegal characters
I have kept in your big regex replacer, but I don't think its need any more.
TV words are checked before movie words. I found this gave better results overall.
TMBD query string is now wrapped in quotes
If TV or Movie search fails, I try again with Multi search
I ignore any event that has the word "news" in it. Lots of incorrect results otherwise.
Lots of refs have a backdrop artwork and no main poster, I download the backdrop artwwork and squash it up. Better than nothing I suppose.
I have kept your skin sources the same (for backwards compatibility), but eventview and epgselection will only work if the poster is already downloaded as the change function doesn't start downloading for these screens. (That would require some more code). Using source="Event" makes things difficult. :/
There is no autobouquets mass download like other chaps have been doing.
Backup any original posterx.py files if you want to compare with my version
I presume this doesn't work on dreamboxes due to the use of threading.
You could get around that with twisted downloadpage. But as downloadpage is defunct in the latest version of twisted, we are all screwed on working out an alternative universal background downloader.
** I have updated the file as today it seems lots of channels titles are prefixed with "New: ". So fixed that **
xstreamity downloads the data, tries to work out the server offset if wrong, tries to cleans the data of any errors, converts it to json format to be quickly read,
while also having a secondary epg from epg importer that will try to fill in any gaps by reading epg custom sids (satellite refs) if the provider has used these rather than an ID in his epg data.
Jedi just downloads the data using epg importer. There will be no error checking. (bad data will just fail). I think epg importer reads custom sids. I can't remember.
But Jedi uses enigma2 bouquets code. So I have no control over the data in jedi.
thats a good question :)
but better to be safe than sorry
openatv 6.4
openatv 7.0
openpli
Is this plugin actively maintained anymore?
Which version is meant to be the working version? Which post?
I was just messing around with this today, and pretty much rewrote it all as personally I couldn't get any of them to work on openatv 6.4 python 2.7
Then looking at some of the other skin threads, I notice people like beber have been tweaking there own versions.
Now I am completely confused.
digiteng biko beber
And I don't want to upload my own amends, as thats going to confuse things even more.
And as they have currently broke the menu named pages
I wouldn't be surprised if they have also amended similar code for all the Settings/Setup pages. So they are probably not skinned as I designed them either.
i.e.
setup_subtitlesetup
setup_autolanguagesetup
setup_remotesetup
setup_specialfeatures
setup_time
As giopet has replied on the openatv thread.
They are experimental images, (as you are both fully aware), so any issues raise them on openatv github 7.0 branch.
The skinned menu not showing is probably an unnecessary name change or a broken bit of code with is preventing the screen name="menu_mainmenu" from being skinned.
(I am not changing anything in my skins for that - as it would break every other image other than that one)
name 'selection' is not defined, is something they have broke and not fixable by a skin author.
I know its only a language file, but I am ignoring all pull requests for jedi maker xtream at the moment.
It just causes problems merging in stuff when I am in the middle of changing every file.
Not at the moment. My offline code isn't uploadable to github as its all different.
post on github tbe
And by the looks of what you and urie have posted, they have broke every single skin out there by changing the menu screens / skin code.
And you wonder why I am still on openatv 6.4
done
I know people are waiting for an update, I keep promising the update. I actually don't mind people asking for an update. (It reminds me to finish it)
Most people on this forum know I have been quite seriously unwell since the start of the year and although better now, I am still not 100%. I am unable to be the same machine I was churning out work on a daily basis. I am tired a lot. So people just need to understand that my plugin work is slower nowadays.
Jedi Maker Xtream plugin was the first plugin I ever wrote, despite a few refreshes the code is old and over complicated.
Therefore the code needs rewriting from scratch. This takes time to make sure code is new and efficient and also all the same functionality remains.
We also have lots of versions of python on the go at the moment, which makes coding and testing more time consuming than it should be.
I know I update my other Xstreamity plugin a lot, but that is only due to the fact that code is new, clean and easy to edit.
At the moment Jedi works, with the exception of the modern panels breaking Series lists. So the priority is low.
I also rarely use this plugin myself as I mainly use my XStreamity plugin nowadays. So on a personal note the urgency isn't there.
I still mess around with the code a couple of times a week, it's not been shelved. It will get finished eventually.
As for the timescale. How long is a piece of string. It could take me a day, a week, a month. Who knows.
Go outside and enjoy the lovely weather instead of watching tv all the time 
Just a thought.... Any way of adding trailers directly in xstreamity?
Not up to me but just my opinion more things to slow x-streamity down and if vod movies are no correctly named by providers then even worst.
If I remember rightly, (I haven't recently checked), The provider API, or TMDB actually has a link for the trailers.
So it is doable, I think lululla does it in his XCplugin, but I got a million and one things on the go at the moment.
So it's probably not going to happen in the short term.
what exactly is the issue you are highlighting in the photo.
The over large LCD display?
The default scaling for graphics on enigma2 is pretty poor. It is very basic and that is why it ends up looking crap.
In xstreamity I have a custom written image resizer using the python piilow library.
That is why all my movie posters are nice and clear.
I have never even tried digiteng s poster plugin. I have never looked at his code.
But maybe my custom resizer can be used in his work using the PIL library.
I might have a play around with his posterx stuff later and see if we can get nice clean resized images.
Well as I have several skins I don't actually know which one you are talking about for adding movie posters.
Most of my skins are meant to be close clones of the originals, i.e sky hd, sky q, virgin etc.So there is no real room for all the movie poster stuff.
Most people are modding the the skins they use with the poster codes and rejigging things themselves.
I don't really have much spare time nowadays to amend all my skins.
And there might even be versions of my skins around that people have modded with the xposter code.
All the instructions are in digitends post
