Correct. You could actually modify the HTTP proxy settings and trusted certificates on the device and run your own applications using a man in the middle attack. Plex had a version that supported this: https://github.com/iBaa/PlexConnect
For anyone wondering about this, I've been using it for a while and it works great - the Trailers app now loads the Plex UI for me. I've barely had to touch it since the initial setup.
I've had worse results -- after a few days, I need to restart the python process as it'll start to block outbound requests.
Why would anyone add complexity to the syntax when you can make it simpler by removing the XML namespace? If you need to add namespaces, then you have already failed.
It's if you want to have backwards compatible syntax supported by later devices. This will naturally happen as you add features and modify old ones. It's even more important in hardware devices that might might not be able to be updated later. EDIT: I think someone is probably down-voting me for a technical reason. Would you please explain it?
As I understand it, you don't need to worry about backwards compatibility. You submit these pseudo-XML views along with your app when you publish it but what they do from there on out is up to them - they could "recompile" them to newer versions, they could compile them to some binary representation, whatever. But anyway, it's not your problem. Your responsibility is getting the app to the app store, their problem is getting the app from the app store to the devices, in whatever format they see fit. Despite the technological similarities, this isn't publishing to the web where you have to handle everything by yourself.
It's if you want to have backwards compatible syntax supported by later devices. This will naturally happen as you add features and modify old ones. It's even more important in hardware devices that might might not be able to be updated later. EDIT: I think someone is probably down-voting me for a technical reason. Would you please explain it?
If Apple wants to break BC they just do it. They control the entire ecosystem and has been known to break stuff pretty frequently and force everyone to keep up
> been known to break stuff pretty frequently
Apple is really good about giving developers a heads up before deprecating anything.
So if you're building a simple media app, can you just use the templates and JavaScript without much or any Swift/ObjectiveC? Sort of like Roku and Sonos?
I'm a little surprised they're jumping into the literal "TV" namespace so wholeheartedly. Is the future of this ecosystem really exclusively limited to the Television? Gaming is already an explicit part of this, which undoubtedly will include VR, which is theoretically suited to Television-like content. If they do this right, the source code running on your VR gogs will mention "TV" everywhere, much like the the curr…
I think TV is an ok reference to "a large screen with a remote control".
That's only half-sarcastic; it does seem to be a similar but much-simplified markup language that learned a lot from HTML5. Will be interesting to watch it develop.
As others have commented, though, XML without namespaces is not a fun ride (in my humble experience).
If any of the authors are reading, you really ought to consider putting this into an XML namespace. It can just be a mysterious invocation to most users today, but if you need to extend this in the future (inline SVG? inline XHTML?), it'll save your bacon to have done it in the first version.
Can't you add support for SVG and XHTML without this? Unless I'm missing something, you just need to put the appropriate `xmlns="..."` attribute on the root element of the SVG/XHTML embed.
The link should probably be the main TVML page rather than one of the template reference pages. https://developer.apple.com/library/prerelease/tvos/document...
OP here - You're exactly right, I looked at that front page and almost bailed. I thought this was much more interesting since it shows a simple example with code and matching output screens.