
A bit of history for those in the tank. In recent years, the flash is in a permanently dying state, and flashers are constantly looking for ways to dump on other platforms. So it was back in 2009, when the flasher Daniel Sperl decided to take up games for iOS. Not finding Cocos2D convenient, Daniele writes his bike, based on the familiar api flash, and in early 2010 Sparrow Framework comes out . The framework is gaining popularity among renegade flashers. Meanwhile, Adobe is launching support for GPU in flash. New low-level api is too tough for ordinary flashers, and Adobe is thinking about a lib, which would hide it behind a beautiful facade, reminiscent of classic api. Starling , Adobe-sponsored reverse Sparrow port to flash, becomes such a livelihood . Adobe money does the trick, and Starling becomes quite popular, killing its main competitors . But the people continue to blame the ever-dying flash, and Adobe decides to get the flash off with the people. Six months ago , the announcement of StarlingJS , a port of Starling on JS using TypeScript, and a completely working demo appeared . Nevertheless, for some reason, the release of the public version of StarlingJS is constantly being postponed, Adobe even instructs Renown Erickson to study the question of directly compiling Starling into javascript using randori .myStarling.addEventListener("complete",handleManifestLoad); myStarling.load([ { src: "assets/spritesheet.png" }, { src: "assets/spritesheet.xml" } ]); Source: https://habr.com/ru/post/203340/
All Articles