Just got a knot in my stomach from seeing storyboard is going to be deprecated. Maybe I shouldn’t? Same stuff new name? Composer is a superset of storyboard with the original set of functions behaving identically?
Hi @henrik5,
It’s highly recommended that you migrate to Composer. I think you’ll find it fairly straightforward, as the overall concept works very similarly to Storyboard. Mostly what has been improved is the “phases” of the “show” and “hide” function handlers, as well as changes to some function names and properties. As a whole, I find Composer to be easier to understand and follow what’s going on.
I assume you’ve located the migration guide?
http://docs.coronalabs.com/api/library/composer/migration.html
Take care,
Brent
@henrck5, Composer is Storyboard 2.0. But to fix some of the things we needed, it required breaking changes and we didn’t want to hose apps built with Storyboard, so we gave it a new name so we could make the changes we needed to.
No need to get sick over it. Continue developing your existing apps with Storyboard. We’ve already made the library open source on our github account so you can have the code work as long as possible. Any new apps you start, or if you’re not too far into your app, then you should consider Composer.
Rob
Rob, good to hear. I’ll grab the old library and keep it for updating the published apps. We make money not from the apps but from the bespoke development of free apps for the clien’ts customers. If a client wants a small change he doesn’t expect to pay for app-wide library migration as well. Updates required by OS changes are a bit more negotiable.
Brent: No, I do get the newsletter but the online docs were the first I heard of it. Probably managed to miss it in the newsletters.
Hi @henrik5,
It’s highly recommended that you migrate to Composer. I think you’ll find it fairly straightforward, as the overall concept works very similarly to Storyboard. Mostly what has been improved is the “phases” of the “show” and “hide” function handlers, as well as changes to some function names and properties. As a whole, I find Composer to be easier to understand and follow what’s going on.
I assume you’ve located the migration guide?
http://docs.coronalabs.com/api/library/composer/migration.html
Take care,
Brent
@henrck5, Composer is Storyboard 2.0. But to fix some of the things we needed, it required breaking changes and we didn’t want to hose apps built with Storyboard, so we gave it a new name so we could make the changes we needed to.
No need to get sick over it. Continue developing your existing apps with Storyboard. We’ve already made the library open source on our github account so you can have the code work as long as possible. Any new apps you start, or if you’re not too far into your app, then you should consider Composer.
Rob
Rob, good to hear. I’ll grab the old library and keep it for updating the published apps. We make money not from the apps but from the bespoke development of free apps for the clien’ts customers. If a client wants a small change he doesn’t expect to pay for app-wide library migration as well. Updates required by OS changes are a bit more negotiable.
Brent: No, I do get the newsletter but the online docs were the first I heard of it. Probably managed to miss it in the newsletters.