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.
I believe this XML+JS thing was the only way to write apps for the old Apple TV. Various postings on the internet seem to suggest this from way back; the old SDK was probably only ever available to a select few handpicked appletv channel partners.<p>What's new in the new tvOS SDK is that you can also write native apps in Objective-C/Swift, with a main() function that starts up UIKit, and with access to most of the normal iOS APIs (like OpenGL, SceneKit, etc etc).
This should be theoretically compatible with React right? I wonder if Netflix are using this + React for their Apple TV app or if they're doing something entirely different... There is a <divTemplate> option so perhaps its through that?
This is what looks like a css: <a href="https://developer.apple.com/library/prerelease/tvos/documentation/LanguagesUtilities/Conceptual/ATV_Template_Guide/ITMLStyles.html" rel="nofollow">https://developer.apple.com/library/prerelease/tvos/document...</a>
Oh look, it's XAML for an Apple device.<p>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.<p>As others have commented, though, XML without namespaces is not a fun ride (in my humble experience).<p>[0] <a href="https://en.wikipedia.org/wiki/Extensible_Application_Markup_Language" rel="nofollow">https://en.wikipedia.org/wiki/Extensible_Application_Markup_...</a>
I'm a little surprised they're jumping into the literal "TV" namespace so wholeheartedly.<p>Is the future of this ecosystem really exclusively limited to the Television?<p>Gaming is already an explicit part of this, which undoubtedly will include VR, which is theoretically suited to Television-like content.<p>If they do this right, the source code running on your VR gogs will mention "TV" everywhere, much like the the current OS running their desktops and mobile devices references a defunct company.
The main problem is that we are still using XML to do component definition and composition.
We need to better language (no, json and yaml are not the answer).<p>I am working on a new language concept (still at early thinking) but the alert template document would be defined as:<p><pre><code> alert#update_available [ //Composition is separated from definition
btn#update,
btn#cancel
]
alert { //All alert elements are defined as alertTemplate
type: alertTemplate
}
btn { //All btn elements are define as button
type: button
}
alert#update_available { //Define the title and description for the alert with ID update_available
title: Get the latest tvOS version
description: Get the latest tvOS version
}
btn#update {
text: Update Now
}
btn#cancel {
text: Cancel
}
//We could override the settings like CSS
(@language = "pt_br") {
//If variable language is pt_br override the content with Brazilian Portuguese texts
btn#update {
text: Atualize Agora
}
btn#cancel {
text: Cancelar
}
}</code></pre>
The link should probably be the main TVML page rather than one of the template reference pages.<p><a href="https://developer.apple.com/library/prerelease/tvos/documentation/LanguagesUtilities/Conceptual/ATV_Template_Guide/index.html" rel="nofollow">https://developer.apple.com/library/prerelease/tvos/document...</a>
I think it's interesting that Apple is promoting making apps that are web based that you wouldn't have to get approval for to make updates. Maybe because it's limited on you can do with TVML but I think it's interesting.
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?