Changes to Figma access tokens affecting Storyboard design import
A quick update on some recent changes within Figma that required us to update our Storyboard Figma design import wizard.
A quick update on some recent changes within Figma that required us to update our Storyboard Figma design import wizard.
Many Storyboard applications evolve and accumulate Lua functions as the application fills-out. These utility Lua functions are typically clustered in a few .lua files under the root of the scripts folder of the Storyboard project file structure which works fine whilst the number of screens is limited however as this grows or the project team increases then the task of collaborating and managing the functionality can start to become more challenging.
The Storyboard Designer install ships with several sample applications which make use of additional community sourced Lua modules to extend the capabilities of the standard runtime plug-ins. Two examples are the comms modules for the SocketJSON sample and the database functionality behind the LuaSqliteDatabase sample.
This document explores some examples of using the SDK API to send and receive Storyboard events and set application data variables in a Real-time Executable environment.
When displaying text that is written right-to-left, this will sometimes have the behaviour of being displayed with the characters in the reverse order. This is because text is interpreted/rendered from left-to-right. This means that the simple solution is to start off by reversing the character order before rendering. E.g. if you want your right-to-left text to be displayed as ‘ABC’ then write it as ‘CBA’.
If you are evaluating Storyboard or the Torizon platform you will likely have seen our pre-built container images configured to run on the Toradex Torizon platform. After you’ve played around with the image a bit, you will likely want to build your own container. Docker is a very flexible and configurable platform so I’m going to show you what we’ve done internally for our container and you can use that as inspiration or a base for your container going forward. To begin you will require the followirng pieces:
Because we will be interacting with Android, the first order of business is to get oriented with the LuaJava bridge. I highly recommend reading this write-up which goes over the process of exporting to Android as well as the luajava API with an example application:
Storyboard’s collaborative features help multiple users develop applications faster. You can merge multiple files (*.gde) together and produce a single output during runtime. This tutorial explains how to create a project with multiple application files.
This document serves as a quick reference which aims to answer questions regarding the various ways in which gstreamer can be set-up in your Storyboard application, and explain the building blocks along the way.
Learn how to render text along a path or curved line within Storyboard to support GUI application development destined for curved screens, such as those found on wearable devices