I heard that there is no more storyboard after graphics 2.0
is that true?
In particle candy they told me about something call “Composer”
what is that?
Yes. But it’s important to know the whole story.
Composer is what would have been Storyboard 2.0. There are enough changes with Composer that it would break Storyboard without you making changes. When the next public build comes out (should be fairly soon) then Composer will be the officially supported version. That means that new features and bug fixes will happen in the Composer version and the older Storyboard code will no longer be maintained.
Now for your use, Storyboard will stay around for a while (at least until September), so you can continue to use Storyboard. We have already made Storyboard open source and you can download it from our github repository so you can use storyboard forever if you want.
Please read the introduction and tutorial on it for the details…
http://coronalabs.com/blog/2014/01/21/introducing-the-composer-api-plus-tutorial/
Rob
Thank you Rob…
Which one is better?
if composer == isBetter then
is it worth it to learn how to use it?
and, is not too difficult?
else
if comoser < isAboutTheSame then
should I just keep working with storyboard?
now that finally I got the idea how to use it…
end
Return What do I do…
Well, until the next public build comes out there isn’t much of a reason to spend energy on it. But given that’s going to be sooner than later, it wouldn’t hurt to start reading up on it.
Composer is better than Storyboard for the following reasons:
1. Any new features and bug fixes will only go into Composer.
2. After it releases to the public, any future tutorials, guides and documentation will be using Composer.
3. If fixes many of the outstanding issues with Storyboard, such as not being able to transition when hiding an overlay.
4. It should be simpler to implement (by just a little bit).
- Overlays have a better way to communicate with their parent scene.
So: return true
Also, if you already have the idea on how to use Storyboard, then switching to Composer will be very easy for you. Same idea, just a little different syntax for some things.
Jay
Okay…
Thanks I will be ready for that…
are there any new tutorials on how to use now that the new (2189) public build is out?
Is it faster than storyboard? (Performance)
Well we refactored the code to try and streamline it, so it should in theory be more efficient, but probably only in a minimal way. Creating objects will take the same amount of time. Transitions are done on a timer, so they shouldn’t be any different.
Rob
Possibly a terrible question - but existing compiled apps will still continue to function correct? Just that we need to update them to composer going forward in any new releases? (Not using source code to continue using storyboard etc.)
Just making sure 
Thanks!
Edit:
Guess I should read first eh? …
" Please note: Although we will no longer support Storyboard, you can keep on using it. It is going to be included in Corona SDK for 9 more months and it is available as open source code, so you will be able to keep on using it for as long as you like. Of course, we recommend moving to the Composer API for all new apps and eventually migrating existing apps."
Once your apps are compiled and online, what we do with Corona doesn’t matter. The one exception would be if you’re using some online service and that service changes how it works or goes away. But for things like storyboard, it won’t effect your existing live apps.
Rob
Great thank you Rob!
Yes. But it’s important to know the whole story.
Composer is what would have been Storyboard 2.0. There are enough changes with Composer that it would break Storyboard without you making changes. When the next public build comes out (should be fairly soon) then Composer will be the officially supported version. That means that new features and bug fixes will happen in the Composer version and the older Storyboard code will no longer be maintained.
Now for your use, Storyboard will stay around for a while (at least until September), so you can continue to use Storyboard. We have already made Storyboard open source and you can download it from our github repository so you can use storyboard forever if you want.
Please read the introduction and tutorial on it for the details…
http://coronalabs.com/blog/2014/01/21/introducing-the-composer-api-plus-tutorial/
Rob
Thank you Rob…
Which one is better?
if composer == isBetter then
is it worth it to learn how to use it?
and, is not too difficult?
else
if comoser < isAboutTheSame then
should I just keep working with storyboard?
now that finally I got the idea how to use it…
end
Return What do I do…
Well, until the next public build comes out there isn’t much of a reason to spend energy on it. But given that’s going to be sooner than later, it wouldn’t hurt to start reading up on it.
Composer is better than Storyboard for the following reasons:
1. Any new features and bug fixes will only go into Composer.
2. After it releases to the public, any future tutorials, guides and documentation will be using Composer.
3. If fixes many of the outstanding issues with Storyboard, such as not being able to transition when hiding an overlay.
4. It should be simpler to implement (by just a little bit).
- Overlays have a better way to communicate with their parent scene.
So: return true
Also, if you already have the idea on how to use Storyboard, then switching to Composer will be very easy for you. Same idea, just a little different syntax for some things.
Jay
Okay…
Thanks I will be ready for that…
are there any new tutorials on how to use now that the new (2189) public build is out?