Hey all.
I could use a bit of clarification about the requirements to use Roku Scene Graph. All of the components that are going to be deprecated are here: https://blog.roku.com/developer/2017/02/01/legacy-sdk/ … but then in the documentation it shows more functions/components that cannot be used here: https://sdkdocs.roku.com/display/sdkdoc … pt+Support
So my question is, what is the most efficient way to go about this “conversion” of my app that uses the older SDK? For example, I understand that to replace roGridScreen I can use a rowList node class, but how do I implement the XML/BRS files to work together using an API’s JSON data? Since I can’t use methods like SetContentList(), setupLists(), setListNames(), I’m unable to see through the examples how to set content with JSON instead of XML data.
I’ve tried replacing the createObject(“roGridScreen”) with something like this:
m.screen = CreateObject("roSGScreen")
m.port = CreateObject("roMessagePort")
m.screen.setMessagePort(m.port)
scene = m.screen.CreateScene("HomeGrid")
m.screen.show()
and then I made a test .xml file called “HomeGrid.xml” where I set it up like so, just to see if it’ll link together:
<?xml version="1.0" encoding="utf-8" ?>
<component name="HomeGrid" extends="Scene" >
' stuff goes here
</component>
but I got an error saying “BRIGHTSCRIPT: ERROR: roSGScreen.CreateScene: No such node HomeGrid.”
Beyond that, I’m just not sure how I change my files/structure so that all of the 40 or so files I have can work with the Roku Scene graph. What goes inside the .xml file?
The documentation and examples are somewhat helpful, but I can’t figure out how to tie it in with what I already have without essentially re-doing my whole application from scratch. I have tons of functions that make requests, responses, general functions. Any help would be appreciated. 
I’m in the same boat, and I suggest you redo all the UI from scratch. I decided that’s the path of least resistance.
For content, the trick is to extend the ContentNode to include all your custom fields, then apply your array of content nodes to a List. You will probably be able to re-use the bulk of your JSON data parser. I found the requirements a little bit confusing, because the List elements require a structure of ContentNodes that is very specific, and it doesn’t work right until you hit the right construct. You don’t just simply load an array of elements like you did with a PosterScreen.
This may not be the info you are looking for, I’m not sure I read your question right. For your content feed, it looks like the parseLeaf() function (in UriHandler.brs) in that demo is what you need to modify
https://github.com/rokudev/videoplayer-channel/blob/master/components/UriHandler.brs
instead of contentNode= CreateObject(“roSGNode”,“ContentNode”), you would use a custom component that extends ContentNode, like contentNode= CreateObject(“roSGNode”,“MyExtendedContentNode”)
and define the custom node like this, in an XML file called MyExtendedContentNode.xml
<?xml version="1.0" encoding="utf-8" ?>
<component name="MyExtendedContentNode" extends="ContentNode">
<interface>
<field id="thumbnail" type="string" />
<field id="contentType" type="string" />
<field id="title" type="string" />
<field id="entitlement" type="string" />
<field id="externalAdvertiserId" type="string" />
<field id="mediaGuid" type="string" />
<field id="accountId" type="string" />
<field id="duration" type="float" />
<field id="trackingData" type="assocarray" />
<field id="category" type="string" />
</interface>
</component>
Then as you parse your JSON you can assign all the custom fields you require and the List component in SG will still honor the fundamental fields of a ContentNode.
The size font color junk in the message is automatically entered when you copy and paste sometimes into the message box on the forum - you can ignore all that.
You’d need to add those fields to your extended content node if you want to have specific fonts, sizes, or placement associated with your content. Or you could put those values into a separate array. It’s an open system so you can organize your data any way you like, but the existing components are easier to use if you comply with the supported content metadata and content nodes or extended content nodes.
https://sdkdocs.roku.com/display/sdkdoc/Font
If your current app is convoluted, then now is a good time to rewrite and streamline it. I printed out the code for all of the last channel upgrade I did and went through with a sharpie crossing out code that wasn’t used. It saved a lot of headache. Basically, any UI screens need to be recreated - if you used roScreen/roImageCanvas then that’s a lot of work - if you used the default posterscreen or gridscreen then it’s easier. Also the video component changed so that will need to be recreated, and the springboard screen needs to be recreated, and the linking/billing routines might need to be recreated. Take it screen by screen, take your time, get one part working and test it, and then move on to the next display.
dang sorry about that formatting stuff, posting to this forum is beyond my capabilities.
For JSON parsing, here’s some code I threw on GitHub. It’s not a complete application, don’t have time right now for that, but hopefully this helps.
https://gist.github.com/timbeynart-nbcu … 8c104f82af
