Starling Builder migration guide

Starling Builder will support both Starling 1.x and 2.x for a long time. This guide will help you to migrate your project using Starling Builder from Starling 1.x to Starling 2.x without problems.


The engine is simple enough to support Starling 1.x and 2.x at the same time, so the latest engine master branch will always work for your project, no matter what version of Starling you are running.


The editor has to branch out to a different version for Starling 2.x. The layout data generated will be slightly different, due to API changes.

If you open a 1.x layout file using Starling Builder 2, the editor will prompt you to convert to 2.0 format. After your confirmation, the following conversion will occur

  • Scale3Image → Image with scale9Grid
  • Scale9Image → Image with scale9Gird
  • TiledImage → Image with tileGrid
  • Old Starling TextField → New Starling TextField
  • Old Starling Button → New Starling Button

If you open a 2.x layout file using Starling Builder, the editor will prompt a newer format is detected and no conversion can occur.


The extensions also have to branch out to the different version. Checkout the 2.0 branch to make your own extension for Starling 2.x.

  builder/migration.txt · Last modified: 2016/10/15 02:27 by johannh
Powered by DokuWiki