HI guys sometime this week i received a email about the new composer API and how clean the new api is from story board. i ran into a little problem i am trying to migrate from storyboard to composer now but i won’t pop up as a library in my corona sdk or my sublime corona editor is it steps that i have to take to install the Composer API
Thanks 
It’s only available in Daily Builds at the moment.
Rob
Okay when will it be available to all developers because I am about to start a new project and I am not sure weather to wait until it’s available or continue to use storyboard??? :]
It will be available when there is a new public build. We don’t have an ETA on when that will be. It could be a couple of months or more.
Rob
Thanks Rob I just use storyboard until it it’s officially available. I guess I have to write my code twice
Wait— so those of us that paid you $99 for Corona to make apps are forced to use the older Storyboard method (since we don’t have access to daily builds) even though, as you state in the Composer “we will no longer support Storyboard… It is going to be included in Corona SDK for 9 more months”…
…and there is no date for when we will get access to composer (may be “months or more”).
…meaning you might drop Storyboard support right before (or after?) we have access to the new Composer. (If it’s after, does that render our code useless while we have neither Storyboard NOR Composer available to us?)
Thanks a lot guys. Enjoy the $99 (third year in a row I’ve paid, too!)
Sheesh.
Hi @jwolverton.
I’m not sure what you are referring to about $99. The only $99 fee per year I’m aware of is the one you pay to Apple for your Apple IOS developer account. You are not paying Corona Labs. The forums indicate that you are a Starter account which means you are using our product for free. We do have paid subscription levels and one of the benefits for our Pro and Enterprise level accounts is access to new features and bug fixes before Starter and Basic accounts do.
Now while we will keep Storyboard in the core for at least 9 months, it’s already been put on our open source “Github” account so people who want to stay with Storyboard even after we remove it, will be able to continue using it.
Rob
“…forced to use the older Storyboard…”
There’s nothing wrong with Storyboard.
My apps that already use Storyboard will *stay* with Storyboard. The new ones I write will use Composer. There’s no good reason (for me) to retrofit any existing apps – and since CL has open sourced the Storyboard code nobody has to worry about it going away in the future.
The optional migration path is something CL did really right in this case.
Jay
I agree with that Jay
Sorry, my mistake! (I used to have a Basic membership back when it was $99).
I am still confused, though-- once Storyboard is no longer in the core, does that mean that those of us with apps using it that download the latest (now without Storyboard) SDK will suddenly see our apps not work? (Unless we also grab the open source version of storyboard and include it in our code.) And will Composer be in the public download by the time Storyboard is taken out?
Yes you have to get storyboard source code in order to make your apps work on the simulator
No, I don’t think Composer will be in the public domain, but it will be in the SDK public release (which is what I think you meant) before Storyboard is shown the door. That’s what CL has said recently.
Putting the Storyboard library in your code will look a lot like this:
Download the lib from Github.
Copy it into your project folder.
That’s it, there is no third step.
I’ve done this with widgets in the past (while transitioning from the old to new ones) and it’s really not the hassle you might think at first.
Jay
It’s only available in Daily Builds at the moment.
Rob
Okay when will it be available to all developers because I am about to start a new project and I am not sure weather to wait until it’s available or continue to use storyboard??? :]
It will be available when there is a new public build. We don’t have an ETA on when that will be. It could be a couple of months or more.
Rob
Thanks Rob I just use storyboard until it it’s officially available. I guess I have to write my code twice
Wait— so those of us that paid you $99 for Corona to make apps are forced to use the older Storyboard method (since we don’t have access to daily builds) even though, as you state in the Composer “we will no longer support Storyboard… It is going to be included in Corona SDK for 9 more months”…
…and there is no date for when we will get access to composer (may be “months or more”).
…meaning you might drop Storyboard support right before (or after?) we have access to the new Composer. (If it’s after, does that render our code useless while we have neither Storyboard NOR Composer available to us?)
Thanks a lot guys. Enjoy the $99 (third year in a row I’ve paid, too!)
Sheesh.
Hi @jwolverton.
I’m not sure what you are referring to about $99. The only $99 fee per year I’m aware of is the one you pay to Apple for your Apple IOS developer account. You are not paying Corona Labs. The forums indicate that you are a Starter account which means you are using our product for free. We do have paid subscription levels and one of the benefits for our Pro and Enterprise level accounts is access to new features and bug fixes before Starter and Basic accounts do.
Now while we will keep Storyboard in the core for at least 9 months, it’s already been put on our open source “Github” account so people who want to stay with Storyboard even after we remove it, will be able to continue using it.
Rob
“…forced to use the older Storyboard…”
There’s nothing wrong with Storyboard.
My apps that already use Storyboard will *stay* with Storyboard. The new ones I write will use Composer. There’s no good reason (for me) to retrofit any existing apps – and since CL has open sourced the Storyboard code nobody has to worry about it going away in the future.
The optional migration path is something CL did really right in this case.
Jay
I agree with that Jay