Segger embOS Support

Crank Software will be introducing support in Storyboard Suite 3.0 for non MMU targets by offering a runtime for Segger’s embOS. New and existing Crank customers will now be able to use Storyboard Suite 3.0 as a single solution to support traditional 32 bit family processors and lower level non MMU platforms.

Storyboard Suite enables customers to begin prototyping and development before a final hardware platform has been chosen. Developers can use the included simulator within Storyboard Designer to test the graphical user interface to verify touch or press events are working as defined in the product specification.

Adding support for non MMU platforms opens up additional hardware opportunities for Storyboard applications. Giving customers more choice on what platforms they can deploy their Storyboard Application on is an incredible value add.

Stay tuned for more information on our non MMU support as we get closer to the Storyboard Suite 3.0 release.

Upcoming Storyboard Suite 3.0 Release

Crank Storyboard™ Suite enables UI Designers and Embedded Developers with the ability to quickly prototype, develop and deploy rich animated user interfaces for embedded devices. The upcoming Storyboard™ Suite 3.0 release has a number of new and improved features including animation timeline, iOS support, custom shaders, internationalization, and image optimization just to name a few.

Click on the video to see a sneak peak of what to expect with the new animation timeline!

Android Support

The upcoming Storyboard Suite 2.0 brings with it the ability to export a Storyboard Project as a native Android Application. Here are a couple of easy steps showing you how to do that.

When your Storyboard Project is complete and you are ready to export to Android, right click on the application .gde file and select Export as Native Android Application.

Next you will be presented with the Export Selection dialogue. Here you will be able to change the application name, specify which directory you want the package to be exported to, and how your application will be orientated and scaled. You will also have the option to select how your application with be signed … either by your existing keystore or one created by Storyboard.

Next you will see the Export Manifest dialogue box. Here you can personalize your application by specifying the icons to be used with the Android application. By default Storyboard includes it’s own icons.

There you have it. After clicking Finish the Android package (.apk) will be in the directory you specified earlier on. I used the default setting and that places it in the current project directory.

The next step is to copy that apk file over to your Android phone or tablet and install.

Android on Roids

You may have heard of this Android platform.  It seems to be all the rage.  Well we here at Crank Software didn’t want to be outdone, so we have come up with a Storyboard Embedded Engine implementation  that will run on the Android platform.  Here are some screen shots of it running in the emulator.

The next phase is to get this running on actual hardware rather than just the emulator.  After that the plan is to integrate this support in to our Storyboard Designer tool.

You may be thinking to yourself “This is great and all, but what does this do for me?”  Well it will help speed along the development of your android app.  You no longer have to worry about the low level pieces of your UI.  A graphics designer will be able to design and prototype an Android applciation in fairly short order, and from there moving it to production quality is an easy step.  So think of it as a performance enhancement for Android app development.