Roidy, awesome progress. I'm wondering, now that essentially all data is here, when are we planning on rolling this into the main plexconnect version?
Roidy, awesome progress. I'm wondering, now that essentially all data is here, when are we planning on rolling this into the main plexconnect version?
the problem is that its only working with ios 6 .. so all thats not updated will ger error code.. need to find a way round that first i guess
Ah, makes sense. Can we do an iOS version detect like we do for determing whether or not plexconnect is compatible, and then use that information to determine which template to use?
thats actually exactly what i was thinking about aswell.. if it checks while entering plexconnect and then forward u either to the standard xml files or to the alternative ios6 ones.. if that was implemented the "progress bar" discussed here https://forums.plexapp.com/index.php/topic/88102-episode-play-progress/ would also work depending on version used...
Ah, makes sense. Can we do an iOS version detect like we do for determing whether or not plexconnect is compatible, and then use that information to determine which template to use?
thats actually exactly what i was thinking about aswell.. if it checks while entering plexconnect and then forward u either to the standard xml files or to the alternative ios6 ones.. if that was implemented the "progress bar" discussed here https://forums.plexapp.com/index.php/topic/88102-episode-play-progress/ would also work depending on version used...
In the progress bar discussion I ended up modifying the XML in place based on the iOS version, but that probably wouldn't work as well here since the XML element being changed has a lot of children.
Either serving up a different template in XMLConverter.py or maybe using ADDXML to fill the itemDetail/itemDetailWithImageHeader element would make sense here.
{{ADDXML}} will pull in a new PMS XML, not another aTV template.
{{CUT}} on the other side will happily cut out even bigger branches - that is XML nodes with multiple children, deeply nested.
{{ADDXML}} will pull in a new PMS XML, not another aTV template.
{{CUT}} on the other side will happily cut out even bigger branches - that is XML nodes with multiple children, deeply nested.
Ahh, I didn't understand what ADDXML did.
My concern with CUT was mostly just the amount of duplicated XML that would be required I guess, but I supposed it won't really have a big impact.
A little suggestion guys:
AWESOME features people are suggesting here. This one and the progress bar of episodes .. I don't think that the users who uses the new version should be harm because of the users of 5.2-
Maybe we can make PlexConnect in 2 Github. 6+ and 5.2- or something like that, i really don't know. Or if it's possible, in the settings there will be an option to choose the version so 5.2- users will choose they are on 5.2- so these features will be off .. But we can't stop :)
We have to add features :)
Just saying what i think.
Thanks for everyone for suggesting and to the developers too of course :)
A little suggestion guys:
AWESOME features people are suggesting here. This one and the progress bar of episodes .. I don't think that the users who uses the new version should be harm because of the users of 5.2-
Maybe we can make PlexConnect in 2 Github. 6+ and 5.2- or something like that, i really don't know. Or if it's possible, in the settings there will be an option to choose the version so 5.2- users will choose they are on 5.2- so these features will be off .. But we can't stop :)
We have to add features :)
Just saying what i think.
Thanks for everyone for suggesting and to the developers too of course :)
The XML will adapt to which OS the user is running. So on 6.0- it shows the dots and on 6.0+ it's the progress bars.
Will it still work with multiply atvs in the same house on diffrent ios?
Yes, should.
It decides on the aTV that is calling.
The XML will adapt to which OS the user is running. So on 6.0- it shows the dots and on 6.0+ it's the progress bars.
Ok , great, when in the closest PlexConnect Github's to my house? :)
awesome.. is this fanart fuction going to be implemented in the main version or is it still to instable?
Yes, should.
It decides on the aTV that is calling.
When will it be in the original code?
I am so waiting for this, to my taste the PrePlay screen now looks like IOS 4.X :)
Yeah I'm curious as to when it will be implemented as well.
Just wondering if there was any progress on this, would love to see it as part of PlexConnect!
Awesome! What is set status button?
Watched/Unwatched
Watched/unwatched is something I miss. Would be good to see it in the base code for TV and movies as a minimum
