8 posts tagged with "workflow"

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.

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:

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.

As your embedded application grows sometimes all those screens make it difficult to focus on a certain aspect of the GUI application. With Storyboard, you can customize the screens being shown and the actual layout of screens being developed to align to match how the screens are transitioned to within the final GUI application for a more intuitive development workflow.

Your custom-built components can now be modified after-the-fact improving their reusability across different GUI applications and helping speed up the GUI development process.

Learn how the workflow for exporting Storyboard-built GUI applications to MCU hardware has been simplified by combining what used to be separate steps into a more unified experience for exporting to MCU-based hardware.

Before we are able to start using the demos from the public Crank code repository we will first need to install a SVN client. To do so in Storyboard Designer we go to Help > Install New Software.

Translations are typically implemented towards the end of a project. In this scenario, you have been developing the app and filling in default text in a single language to be translated at a future time. Now that time has arrived and the translator is standing by to fill in alternative values for whatever languages will be supported. The following tutorial will walk you through the recommended workflow for exporting a translation database file for the translator to fill in and re-importing it into the project to view the translations in the app.