In this update
Welcome to the April 2024 edition of “What’s New in RokuCommunity.” Please consider subscribing to stay up to date with what’s happening in RokuCommunity.
This was a light month in terms of releases. We have a lot of behind-the-scenes work going on in the brighterscript project, more on that next month.
The RokuCommunity projects are maintained by a relatively small group of developers (mostly volunteers), and we have a growing list of unresolved issues. We need your help! There are many different ways you can contribute. Whether it’s addressing bugs, improving documentation, introducing new features, or simply helping us manage our expanding list of GitHub issues, your involvement would be greatly appreciated. We are more than happy to guide you in finding the most suitable contribution method that aligns with your interests. To learn more about how you can contribute, feel free to reach out to us on Slack, or explore the existing GitHub issues:
We added a new delete
button in the Roku File System view in vscode. This should make it much easier to delete files from the currently side-loaded dev app. One nice use case is when you want to delete cached files from cachefs:
.
We’ve finally added support for several common actions in the Roku development ecosystem: creating packages and rekeying devices. You can access these new commands through the command pallet. They will walk you through a series of questions (such as “what device”, “what’s your signing password”, etc). We understand that some of this information is highly sensitive in nature, so rest assured, we do not store or save any of this information, it’s kept in memory during the operation, and then promptly deleted as soon as the task is complete. You can audit our logic by reviewing this file.
Here’s an overview of the new commands:
BrightScript: Rekey Device
: Rekey the specified device based on the signing password ("brightscript.remoteControl.signingPassword"
) and package file ("brightscript.remoteControl.signedPackagePath"
) provided.
BrightScript: Create Package
: This will present user a list of available launch configs to choose from or manual entries. Once selected it will create a .zip file and .pkg file based on the config and will save them to the ${workspacefolder}/out
BrightScript: Rekey Device and Create Package
: This will first rekey device and then create package for the selected launch config
Here’s a quick demo of the Rekey Device
command in action:
The SceneGraph Inspector panel now supports showing details to the right of the tree when the panel is large enough. This is a nice improvement that results in a more familiar interface for those who were used to the RALE layout.
The SceneGraph Inspector can now be opened in a completely new tab! Also as of the April 2024 release of VSCode, you can also move that panel from the current window to a new window, but there’s no programmatic way to do this so you’ll need to move it there yourself. This should provide much greater flexibility when using this panel.
We’ve added a new “focus node” button in the SceneGraph Inspector which will pass focus to the selected node.
This month we started working on a v4 release of roku-deploy. This will bring a series of breaking changes that have been needed for a while now. Here are some of the highlights:
RokuDeployOptions
interface) (#126)retainStagingFolder
which was deprecated (#130)dest
is missing (#130)default
function exports. You should import { rokuDeploy } from 'roku-deploy';
now. (#144)npx roku-deploy sideload --host 192.168.1.123 --password aaaa --rootDir ./src
without needing a custom nodejs scriptcwd
option (158)We’ll be creating a migration guide in the roku-deploy v4 readme closer to the official release.
Last but certainly not least, a big Thank You to the following people who contributed this month:
Contributions to vscode-brightscript-language:
Contributions to roku-deploy:
Legal notice
The views and opinions expressed in this website and all of its pages are those from within our open source community and do not represent the views or positions of Roku, Inc. or any entities they represent.
Designed with @arturocuya, powered by Astro
by