director - storyboard - now composer?

Getting Started Newbie Questions
#1

I am not a full time corona programmer - I have a ‘daytime job’ to pay bills.  I spent a good part of a year creating a new point-and-click game which is finished and I am ready to publish on my vacation.  Now I see composer?  So here are my questions:

QUESTION 1) I am using build v2014.2179 for my current game which I hope to publish this week.  The game was done in storyboard.  The game works fine on devices.  TODAY: Am I good to go to publish with storyboard using build version v2014.2179?

QUESTION 2) For my new game, I plan to take my point-and-click template done using director and use if for my next game.  This should save me time.  Will storyboard be supported in the future?  Or will I have to redo everything again from scratch using ‘composer’ (this will require a learning curve again) ?    

Thank you, Jan

#2

Hi Jan,

I can answer these questions:

  1. Your current game using Storyboard should be fine to go. There’s no need to re-configure it with Composer. We suggest that developers begin new projects using Composer, but existing projects can remain in the Storyboard framework.

  2. I don’t think Director is supported any longer by the original author, so I highly recommend that you convert your new template to Composer. Storyboard will eventually be deprecated, but most likely it will be open-sourced at that point for those who wish to remain using it (but it won’t receive any further support or modifications after that time). As for the “learning curve”, Composer is not vastly different than Storyboard… it’s actually more simple/understandable in my opinion, and the functions/properties are more logically named. If you follow the migration guide (link on the page below), I think you’ll be up-and-running pretty quick under Composer.

http://docs.coronalabs.com/api/library/composer/index.html

Take care,

Brent

#3

Thanks Brent!   After viewing the Composer docs I think the learning curve will be much less compared to going from Director to Storyboard.  It will be much easier.  I have months of graphics work to do for my next game and time to create a new template for the game.  I will use definatly use Composer.   Thanks, Jan

#4

Hi Jan,

I can answer these questions:

  1. Your current game using Storyboard should be fine to go. There’s no need to re-configure it with Composer. We suggest that developers begin new projects using Composer, but existing projects can remain in the Storyboard framework.

  2. I don’t think Director is supported any longer by the original author, so I highly recommend that you convert your new template to Composer. Storyboard will eventually be deprecated, but most likely it will be open-sourced at that point for those who wish to remain using it (but it won’t receive any further support or modifications after that time). As for the “learning curve”, Composer is not vastly different than Storyboard… it’s actually more simple/understandable in my opinion, and the functions/properties are more logically named. If you follow the migration guide (link on the page below), I think you’ll be up-and-running pretty quick under Composer.

http://docs.coronalabs.com/api/library/composer/index.html

Take care,

Brent

#5

Thanks Brent!   After viewing the Composer docs I think the learning curve will be much less compared to going from Director to Storyboard.  It will be much easier.  I have months of graphics work to do for my next game and time to create a new template for the game.  I will use definatly use Composer.   Thanks, Jan