Player APIs (BrightScript & JavaScript)

brightscript vs javascript when developing for brightsign players, you must write in brightscript at some point (unless you are using brightauthor\ connected) though most users are not familiar with this language traditionally, every application, presentation, video, etc that ran on a player was driven by brightscript since most users today want to use javascript to develop applications and control the player, brightsign has been working to accommodate that nevertheless, brightscript remains integral because without an autorun brs file, written in brightscript, your player will not behave as intended the brightscript language https //marketplace visualstudio com/items?itemname=rokucommunity brightscript extension in visual studio code facilitates brightscript coding and is used by thousands of developers around the world why brightscript is required autorun brs is the generic name for a file the brightsign operating system (bos) searches for on the player’s configured storage device (see image 1, below) if an autorun brs is found, the player will execute it it is the entry point for any application developed on a brightsign player, and it can handle the entirety of an application (brightauthor\ connected), be a simple pointer to more complex programs (javascript applications), or any mix of the two the brightsign autorun brs also configures the player many player setup/configuration options must be set up immediately (such as ssh, logging level, some network interfaces, registry settings, video decoder routing, etc ) these settings are unique to media players, and because the autorun brs is the first thing the player executes, it is the best (and sometimes only) place to set them when creating a javascript application or presentation, the autorun brs will typically configure the player, instantiate an html widget, and give the html widget the correct html file or url the html widget will then take over and run your javascript files screenshot 2025 01 07 at 11 16 48 am png when to use brightscript brightscript required brightscript is required for these scenarios player setup/configuration that must be done before a javascript application or presentation is loaded setting up logging level instantiating the html widget setting up network interfaces (on certain ports) certain file system operations brightauthor\ connected plugins autorun logging level and bos logging (serial) any brightscript object that doesn’t have a javascript alternative a list of brightscript objects and their javascript alternatives is brightscript javascript migration guide docid 2kewwxlmpycwu8tffuf2z brightscript recommended though javascript can be used, brightscript is recommended in these scenarios player setup/configuration that is not time dependent, such as setting up ssh/telnet or setting up network interfaces on main ports player sync