Sharing this announcement here since I nearly missed the blog update myself and feel this is a big deal for developers.
https://blog.roku.com/developer/2017/02/01/legacy-sdk/
Effective immediately: No new features will be added to our legacy SDK visual screens
July 1, 2017: All new channels must use RSG or Direct Publisher
January 1, 2018: All channel updates must use RSG or Direct Publisher
January 1, 2019: Legacy visual screen components will be removed from Roku OS
It is a BFD indeed!
The Co want to deprecate the “old look&feel” components apparently.
On a side note, one could see the new posts from the dev.blog pop (rss feed) in the http://chat.stackoverflow.com/rooms/125654/roku if one were to join that room. The question of course is, how would one remember to check on said chat room? 
Sadly, the @RokuDev twitter is a useless robot right now, that keeps repeating messages pre-recorded many months ago and because of that any real news would be lost in the repetitive torrent
Will this affect the Sample Brightscript SDK that Belltown created : https://github.com/belltown/Roku-NewVideoPlayer? Does it include any of the Legacy SDK Components?
I was going to try converting a channel to Roku Direct Publisher but it is not available on Private channels, I don’t see the “Convert to Direct Publisher” option. Not really sure what would happen if I try it on a Public channel.
I tried to do the SceneGraph guide but there are errors in it so was unable to test : https://developer.roku.com/en-ca/develo … uide-index
I’m just trying to figure out if I need to do anything in preparation of the change
“matrixebiz” wrote:
Will this affect the Sample Brightscript SDK that Belltown created : https://github.com/belltown/Roku-NewVideoPlayer? Does it include any of the Legacy SDK Components?
Yes, it (d)effects the above NewVideoPlayer - i just had a quick look and it uses e.g. roPosterScreen which will be deprecated. Note the timeline - it does not mean you cannot submit new channels with “old” APIs outright - but plan accordingly for the long term.
Okay, I’ll try and create a working Direct Publisher version of my channel.
What time line does the above SDK channel fall under before it dies?;
July 1, 2017 or January 1, 2018 or January 1, 2019
Will my channel just not work anymore or does that timeline just mean that if I have to submit an update then it has to be in Direct Publisher format but the old channel itself will continue to work properly?
“matrixebiz” wrote:
What time line does the above SDK channel fall under before it dies?
It doesn’t fall anywhere, since it is not published as an app in the Store.
The above deadlines apply to submissions
Sorry, I meant my published channel that is based off that SDK 
Okay, thanks for the info, so I have 2 years to figure out how to program the channel in SceneGraph or Direct Publisher instead
“matrixebiz” wrote:
Sorry, I meant my published channel that is based off that SDK
Okay, thanks for the info, so I have 2 years to figure out how to program the channel in SceneGraph or Direct Publisher instead
Or 2D API. It’s not going away.
Which type is easier to convert the NewVideoPlayer channel too?
“matrixebiz” wrote:
Which type is easier to convert the NewVideoPlayer channel too?
Id go with RSG its the newest and has a lot of customization. Just start building some samples and tweaking and studying its a lot harder than brightscript but not too hard, if you are fluid in brightscript you will figure it out in a couple days/weeks..
So if i read correctly if i have a private channel i have until 2019.
I can keep publishing new channels with old sdk and updating them right? privately i mean
“adrianc1982” wrote:
“matrixebiz” wrote:
Which type is easier to convert the NewVideoPlayer channel too?
Id go with RSG its the newest and has a lot of customization. Just start building some samples and tweaking and studying its a lot harder than brightscript but not too hard, if you are fluid in brightscript you will figure it out in a couple days/weeks..
I would not advise that, it would be violation of the Geneva Convention: @matrixebiz is smart but beginner at programming.
“adrianc1982” wrote:
So if i read correctly if i have a private channel i have until 2019. I can keep publishing new channels with old sdk and updating them right? privately i mean
Yes, that is my understanding too. They will work till they yank the deprecated components, scheduled > 12/31/2018. On a side note, it’s fair to assume the old components will remain “forever” on boxes that are discontinued from maintenance (firmware updates) by that time.
Will there be a replacement for roCodeRegistrationScreen?
EDIT: auth-linking-channel.zip in roku’s sample github did what I needed: https://github.com/rokudev/sample-channels
