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!
I have developed a left and right page flip for corona for my interactive ebooks and added the functionality to the open source storyboard. Given there is composer my question is; Is there anyway to extend composer with additional effects if so are there any examples (The API does not appear to support extensions but perhaps i am missing something) if not i am safe staying with storyboard for the next few years? (i understand that this will not be maintained but the code appears relatively clear so i am confident to be able to maintain for my apps going forward but is there likely to be major changes effecting this so i can understand the potential risks)?
Thanks!
Steve
Hi Steve,
At some point, Storyboard will likely be open sourced and support will discontinue for it. Its code should continue working, so if you want to keep using it after that point, it should be possible. We just recommend that developers migrate to Composer for new projects, since that will be supported going forward.
Brent
Actually you can already download the storyboard.lua file:
https://github.com/coronalabs/framework-storyboard-legacy
We will not be updating Storyboard going forward. While storyboard is still in the core, you can continue to use it. Once we remove it, just drop the storyboard.lua from the above link into the folder with your main.lua.
Rob
Thats what i have done is take the github code and merge my code in, i am just testing it to be sure all the events work as expected as the page flick does not follow the same approach as the other effects although that will be transparent to any user. It appears from what you say that the risk of issues going forward is relatively small would that be fair to say?
One other thing, what are the issues with overlays and storyboard that composer addresses?
BTW - I have ported all my work from HTML5/JS to corona due to server performance issues on devices with animation and drawing so far Corona has worked exceptionally well on the same hardware and i will certainly be going pro and sticking with this for the foreseeable future if the prototype works as expected and its certainly looking good so far.
There is a known bug when showing overlays that .isModal doesn’t block all touch and tap events from making it through to the parent scene.
Rob
Brent, Rob
Thanks for the answers much appreciated!
I have developed a left and right page flip for corona for my interactive ebooks and added the functionality to the open source storyboard. Given there is composer my question is; Is there anyway to extend composer with additional effects if so are there any examples (The API does not appear to support extensions but perhaps i am missing something) if not i am safe staying with storyboard for the next few years? (i understand that this will not be maintained but the code appears relatively clear so i am confident to be able to maintain for my apps going forward but is there likely to be major changes effecting this so i can understand the potential risks)?
Thanks!
Steve
Hi Steve,
At some point, Storyboard will likely be open sourced and support will discontinue for it. Its code should continue working, so if you want to keep using it after that point, it should be possible. We just recommend that developers migrate to Composer for new projects, since that will be supported going forward.
Brent
Actually you can already download the storyboard.lua file:
https://github.com/coronalabs/framework-storyboard-legacy
We will not be updating Storyboard going forward. While storyboard is still in the core, you can continue to use it. Once we remove it, just drop the storyboard.lua from the above link into the folder with your main.lua.
Rob
Thats what i have done is take the github code and merge my code in, i am just testing it to be sure all the events work as expected as the page flick does not follow the same approach as the other effects although that will be transparent to any user. It appears from what you say that the risk of issues going forward is relatively small would that be fair to say?
One other thing, what are the issues with overlays and storyboard that composer addresses?
BTW - I have ported all my work from HTML5/JS to corona due to server performance issues on devices with animation and drawing so far Corona has worked exceptionally well on the same hardware and i will certainly be going pro and sticking with this for the foreseeable future if the prototype works as expected and its certainly looking good so far.
There is a known bug when showing overlays that .isModal doesn’t block all touch and tap events from making it through to the parent scene.
Rob
Brent, Rob
Thanks for the answers much appreciated!